Ben Bridgwater wrote: > I complained to my ISP about the sites I couldn't access and got a > similar answer, that traceroute and even ping (depending on firewall > setup) don't necessarily determine whether you can actually access the > site. In the case of www.nvidia.com I was unable to access the site for > a couple of days, but I'm now able to access it although I *still* get > the 10.0.0.2 address and subsequent "* * *"'s in the traceroute! In many cases, ISPs and/or systems will set things up not to return anything for traceroutes and pings. It's entirely possible NVidia did this with their own system. What's fun is that different route-check utilities sometimes use different packet types, so one will work where another won't. I know for sure that the 'traceroute' that comes with Slackware differs from the 'mtr' utility that way, because often one works where the other doesn't. Some day I'll dig for the details. -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Cliff Sharp | "Speech isn't free when it comes postage-due." | | WA9PDM | -- Jim Nitchals, founder, FREE | +-+-+-+-+-+-+-+-+-+- http://www.spamfree.org/ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
