C:\>tracert google.com Tracing route to google.com [216.239.37.100] over a maximum of 30 hops:
1 * * * Request timed out. 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. what the H#$## does this mean...I put in the proxy... -----Original Message----- From: Scott.Wiseman [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 19, 2002 10:08 AM To: NT 2000 Discussions Subject: RE: why can't I ping or telnet from behind a proxy? Not far at all.... I must need to put in the gateway? Microsoft(R) Windows NT(TM) (C) Copyright 1985-1996 Microsoft Corp. C:\>tracert google.com Tracing route to google.com [216.239.37.100] over a maximum of 30 hops: 1 Destination host unreachable. Trace complete. C:\> -----Original Message----- From: Adam Smith [mailto:[EMAIL PROTECTED]] Sent: Monday, February 18, 2002 6:38 PM To: NT 2000 Discussions Subject: RE: why can't I ping or telnet from behind a proxy? > Subject: why can't I ping or telnet from behind a proxy? > confused and sort of dazed Pings are not proxied. Proxying is a way of caching information so that it can be re-retrieved more quickly (and cheaply). What you mean instead of a "proxy" is a firewall. A firewall is in place to protect a local network from inbound packets, by restricting the type of data that comes through, and through which methods it is allowed to come through. The firewall can also be configured to stop certain types of packets from going out from the local network to the internet, for example pings and traceroutes. For example, at my work, the firewall (which is a router) is configured to allow packets to be transferred outward only by a single server on the network. It is also configured to block a large amount of data that's coming into our network. The server that's allowed out is doubling as a proxy server, so it is caching HTTP and FTP requests so that if the same file is requested twice from the Internet, it's looked up locally instead. In my case, pings go out via this server, through our firewall/router, and out to the net. It would seem that in your case, your firewall is blocking ping requests. Try doing a traceroute and seeing how far you get -- that way you'll know at which point your pings are being blocked. For example: tracert google.com Adam ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED] ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED] ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
