I don't really know what this tells me. It seems as though it works up to the 12th entry and dies? I am a little confused that I can resolve the IP, but the page will not load. Thanks for all the help so far, you guys are great.
It says that packets (traceroute) are getting out from the SuSE box up to a point. At this point, either the routers are dropping the traceroute packets (possible and likely probable) or the route has problems (can't hop to the next router). But it does show that packets are indeed routing out from you to the internet, so not a routing problem from your network, maybe after. Now do the other SuSE boxes and the Windows PCs follow the same/similar route? If so, do those have problems getting to the site? If they do, then the routes may have problems. You could try using ethereal to capture the raw packets that come to and leave the SuSE box and see if something is wrong. When I try the ping I get the ip 64.56.191.114, but when captured with ethereal I get the ip you get with ping (64.41.140.167). BTW, have you tried typing in the ip in your browser on SuSE to see if this works? I know that dns works for you, but it does eliminate the need to resolve, and based on what you've provided it should fail as well. You resolve the name to the ip, but can't get there. I'm gonna venture a guess that the problem has to do with routers outside of your network. Based on dns working and the fact that you can route out of your network up to a certain point. Ethereal should reveal more about what's happeining. John