I have a home network consisting of one W2KSP4 server, two W2K workstations (SP3 and SP4) and an old W98 notebook. The server has three NICs: one connected to the internet via DSL, the second connected to the W98 machine and the W2KSP4 workstation, and then third NIC to the W2KSP3 machine, via coaxial because of distance. I have "Routing and Remote Access" on the server configured so all machines have access to the internet and to each other. The W2KSP3 machine (the one on coax) has had web access problems for several months: it can browse normally for about ten minutes after booting and then no more web (although programs like MSMessenger or Media Player continue to have access just fine). This didn't matter much since that computer doesn't get much use. A week ago the other W2K machine developed a similar problem, except it can't surf from the moment it boots. I can ping any website or local machine by name and by IP, and access shared folders but not browse web. Stranger still: it can access cnn.com and google fine, and connect the browser to port 14 on NIST servers; but nothing else. The only thing that has changed on that machine is the network card, and the new one conplained that the fixed IP was being used by the old (uninstalled) one. I tried changing every machine to DHCP and reserving different IPs but still got no http access. Tried deleteing the Hosts file too, with no change. Internet Explorer, Opera, Netscape and OffByOne browsers all have the same problem. I also have the firewalls (Sygate) configured properly (tried uninstalling them, just in case; but no luck) The old W98 notebook surfs Ok. Any ideas, short of reformatting and reinstalling? thanks!

Try downloading a utility called Dr TCP/IP and lowering the MTU on the ISP connection to 1400 mtu.

Thanks for your suggestion. I got DrT and did what you suggested but got no results. I noticed something strange in DrT, there are four adapters listed in the dropdown: A "Microsoft TV/Video Connection" (what??); the original (uninstalled) network adapter, "Realtek blah blah"; a previous name of the existing adapter, "CNetPro200"; and the present name of the same adapter, "CNetPro200 #2". I think this is because I uninstalled and reinstalled this adapter while trying to solve the problem, and the second time it took the "#2" name (apparently uninstalling doesn't free the name). I don't know if this hav something to do with the problem. I also noticed that Opera browser says on its status bar "Request queued for sending to www.whatever", and IE says "Website found, waiting for reply"; I think this mean that the browsers DO connect to the sites.

New development: I connected the DSL modem cable directly to the W2KSP4 machine (leaving it isolated from the home network and the network without internet access), ipconfig /released and /renewed, and YES; web browsing and email are back on this machine. I took the opportunity to get my emails and check some pages, but of course the DSL cable had to go back to the server. Naturally I'm web less again. The problem is not in the workstation because it can surf while connected directly to the modem, but neither it is on the server doing the routing because the old notebook surfs ok. More ideas?

You may also want to try lowering the mtu on the machine that can browse cnn.com but no others. the default packet size for a dsl packet 1500 bytes. Unforetuneatly when browsing via nat to certain sites it adds a 8 bit packet header onto that making your total size 1508. Since ethernet only allows 1500 as well it creates a bottleneck. Usually i adjust the router accordingly but not entirely sure how to do it on a w2k box. Try dropping it on the local client.

I had dropped the MTU before (of all adapters, the real one and the 'ghosts', just in case) to 1400 as recommended on another reply; but there was no change in behaviour. Now I tried it again, but lowering the MTU down to 512, and YES: the web is back, THANKS!. I changed the same settings on the other W2K machine, and that got the web back ... but only after a reboot, and as before the web access failed after about 1o minutes. Mystery pending solution. Now, lowering the MTU does not impose a performance penalty (compared to when it worked at the default 1500)? I have the TCP receive Window at 64240. What could have happened to make it NOT work with the default? I have always connected via the server, and don't remember changing anything. Thanks again