Recently had these W2K SP4 machines' user data cleaned (no re-format) to be used as training pcs in the company. These machines are part of a domain. I noticed something on one of them. First noticed the problem when I was trying to run Liveupdate, failed message appeared. Then Spybot failed to even connect to the remote site for downloading. I tried to access normal websites (such as Windows Update, Microsoft, Google, Yahoo, cnn, etc.). I'd get the HTTP 403 (Forbidden) message, indicating I may not have the credentials to view the page or directory. I had checked a number of places, TCP/IP settings (which matched a DHCP enabled PC right next to it), cleared temp internet files, etc. Re-installed SP4, re-installed IE6 SP1 (the default browser used). Local intranet within our company still works as I could perform installs of programs from the server, and I could ping loopback, another pc on the domain, DNS, Gateway with no problems. Trying tracert to yahoo and it timed out once a response from the gateway was received. Hence timed out if trying to reach out of the gateway. It gets frustrating as this was the last PC I need to perform updates on and all the 6 or 7 others with the same set up seem to connect just fine. I am guessing there is something extremely obvious that I am missing here? Please help. Thank you.

It sounds like a local policy or permissions problem. Open admin tools in the control panel and go to local security policy. Also, look at users and passwd in the control panel.

Ah, that's one place I haven't looked into. Which particular item or items under Local Security Policy should I be looking into?

Update: Well, I compared Local Security Policies side-by-side with the PC that works with the one that doesn't. On the quick run through, it seems they are identical. I also made sure the hosts file is identical in contents. But, no cigar, that one still gives me the HTTP 403 (Forbidden) as it tries to connect to the remote sites. Any other suggestions? Thanks

Sounds like your company has a firewall and/or proxy server that is doing the blocking.

Lets drop down to basics. Does it have a correct ip address? Can it ping itself? Can you ping the gateway? Can it access the local network? Can you ping the wan interface on the gateway device? Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

Well, as I've indicated above. This one shares an almost identical configuration as a working one (same system). I made sure no duplicated IPs, I was able to do loopback ping, ping dns, ping gateway, access local network. Only thing that was not working is anything beyond our company network. After doing more research, someone mentioned a certificate in place may have prevented the access, so I went ahead and found one in the Public Key Policies, disabled it and just like that, I was able to connect to websites, and start downloading updates. I thank all that have chipped in to help with all the suggestions, if it weren't for you guys, I'd never have narrowed the search down to looking at Administrative Tools and Local Policies. Hazzah!