Hello guys, I upgraded the long over due ScreenOS 3.0 to ScreenOS 4.0. Has anything changed in regards to how configs work because after the upgrade my DMZ isn't working. I am using the DMZ to run our Citrix Secure Gateway so right now no one can access their citrix application from the outside. Here's how I have it set up
eth1 = trust 10.10.0.3/23
eth2 = DMZ 192.168.100.1/24
eth3 = untrust (public)
Alright, please keep in mind that everything worked fine and dandy in screenOS 3.0...now upgrading has made this stop.
I have the following policies in place;
from untrust to DMZ -> map external IP to 192.168.100.11 (our citrix secure gateway)
from untrust to DMZ -> Any to Any (just for testing)
from DMZ to untrust -> Any to Any (again just to test)
It doesn't work. I go to the Citrix server and I can access the internet just fine, I go to whatismyip.com and it tells me my external IP (that I mapped). However, I try to ping and I get no response...none at all, I try to access the IIS server on citrix and I can't externally. Anyone have any ideas? Does ScreenOS 4.0 set something up by default for protection that I need to look at? Please help!! Thank you!
eth1 = trust 10.10.0.3/23
eth2 = DMZ 192.168.100.1/24
eth3 = untrust (public)
Alright, please keep in mind that everything worked fine and dandy in screenOS 3.0...now upgrading has made this stop.
I have the following policies in place;
from untrust to DMZ -> map external IP to 192.168.100.11 (our citrix secure gateway)
from untrust to DMZ -> Any to Any (just for testing)
from DMZ to untrust -> Any to Any (again just to test)
It doesn't work. I go to the Citrix server and I can access the internet just fine, I go to whatismyip.com and it tells me my external IP (that I mapped). However, I try to ping and I get no response...none at all, I try to access the IIS server on citrix and I can't externally. Anyone have any ideas? Does ScreenOS 4.0 set something up by default for protection that I need to look at? Please help!! Thank you!