Well, you sorted it already, good stuff.....
some (late) notes
I suspect the "set zone Untrust block" in the config is what caused the issue.
If you do a "get zone untrust" you should be able to see if it is still enabled or not.
The untrust zone has the 'block' option on by default, and since he's going from trust to untrust, it's irrelevant (or should be
)
The dip id used in the policy ID 1 cannot be correct since the egress interface for that policy is the untrust one, and the dip is on the trust interface. -> remove that dip from the policy, replace with "none, use interface ip" (or s'thing that sounds simmilar.
Also, your guarenteed and max bandwidth are equal, i'd start of by removing those settings too.
Let's get internet working first, you can always brake it by adding fancy stuff later
============
you cant ping a hostname from the NS.
(hostname = fqdn in this case (
www.google.com)).
?
Sure you can......
www-> ping
www.google.com count 20 from eth2
Type escape sequence to abort
Sending 20, 100-byte ICMP Echos to
www.google.com [66.102.13.99], timeout is 1 seconds from ethernet2
!!!!!!!!!!!!!!!!!!!!
However, timeshadowrider was pinging from a cmd box, not from a telnet session to the netscreen
