Windows

One thought: look at the Coonection tab under Tools, Internet Options in IE for anything untoward.

Since you are able to ping your tcp setting should be correct. And since you can ping by name your wins and dns should be ok. Since they look ok why don't you try the IE settings. Check the internet options Connections tab. The lan settings may havebeen changed or if they are correct check to see if you have the MS proxy client enabled. Are you able to do anything else like telnet, ftp etc. If so you may have to check to make sure nothing is blocked. Hope this helps.

The only thing I can think of is that you don't have clear access to TCP port 80 for http. Your excellent description rules out the common problems (routing issues and DNS issues).

Short of doing a packet trace and/or getting with your net adminfolks, the only thing I can think of would be to try some other TCP protocol (FTP or Telnet, perhaps) and see if you can reach the outside world with those.

Also, you might see if other machines on your subnet can browse the Web.

paul

When TCP/IP works perfectly at the command line but fails on all gui applications the problem is usually a broken winsock2 function. (sna/ip terminal emulation is a frequent culprit breaking winsock2.) The only consistent fix I've found is to: 1.remove the app that broke it; 2.remove the tcp/ip protocol completely and reboot; 3.add tcp/ip back in, but whenever a "newer version" is on the hard drive be sure to overwrite it with the older original version, reboot; 4.re-apply the current service pack, reboot; 5.Install (or reinstall) IE5.01. These steps should restore the winsock components to all compatible and working versions.

Okay no one mentioned this so I have to I guess.. Are the networks seetings set up okay on the box?.. i.e. not only is the DNS server ip address noted but it the "Gateway" address in there. Do a ipconfig /all on a command line is all okay? If I'm wrong then I am wrong but I like to cover the basics sometime just to make sure.