Win2k can't get on the internet *fixed*

[Hamman999]

Ok, Win2k is still without a internet connection. I made those services which you listed manual and tried runinng the machine on both static and DHCP-retrieved IPs. Nothing. I have an idea as a sort of last resort. On my junk storage partition I have a complete Hard Drive backup of my last Win2k paartition (the last time before I reformatted). What I am going to do is save a copy of my current junked-up Win2k, reformat the drive, and then copy the old backup onto the clean drive. I am not usre if this will work, but I'm kinda desperate. This weekend I might try the trick one of my classmates told me to try out (the physical remove and replace on the NIC). But I have a few more questions, that I'm not sure you've quite fully answered for me:

• What does that constantly recurring error message mean? If this error was @HOME's fault (which for once I think it isn't), wouldn't Windows just tell me that the DHCP server was unreachable?
• How am I going to make any of these solutions work if I can't release or renew my IP address?
• Why can i ping all these IPs and servers but not be able to use them through IE, Outlook, etc.?
• And the most obvious question, what next?

I know this must be frustrating to you (more so to me), but you really have tried to at least make a valiant attempt to solve this stupid problem. Till next time.

David

 

[Slikkster]

Unfortunately, there's no documentation from Microsoft about this problem. If it makes you feel any better, you're not alone (well, not quite, anyway). Take a look at this guy's problem and see how similar it is to yours. It, too, involves dual-booting, by the way.

Same thing for this poor dude

Notice he got no replies, however, his email address is there in case you want to email him as to his resolution. However, we may be able to learn from this.

Have you tried releasing the IP address from Win98 and not renewing it there?. I mean release, log off/restart into Win2k and then release/renew.

Another suggestion: Create another user (with adminstrative rights) on your Win2K machine and try logging on as this new user and see if you can get online.

The error you're talking about is a general "Winsock" error; in other words a TCP/IP error. However, you said you removed the protocol stack and then reinstalled it to no avail, true?

Can you uninstall EVERY networking component you see listed (client for MS Networks, File/Print Sharing, TCP/IP and the reinstall Client for MS Networking and TCP/IP?

I need you to do one other thing which could be a little tedious...that is to go to the following registry key (in Win2K) and give me a readout of every entry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

There's entries in the Parameters main key, then there's some sub-keys, too, like Adapters, etc.
I need all the info. If there's some you don't want to make public, send me a private message here with the info.

You don't need all the "000000x0" type crap...most are DWORD values..just give me the decimal value in parentheses. Note, you can right-click on any keyname and choose "copy key name" to paste into a message to save time.

Also (heheh...always something new to try...), try this:

If you do an "ipconfig /?" you'll see other options. I'd like to see you try:

ipconfig /flushdns

AND

ipconfig /registerdns

You'll see what these things do by doing the "ipconfig /?" at the command prompt.

 

[Hamman999]

Well, this probably not gonna surprise you, Slikk, but by using that old install backup of Win2k, my internet connection is now operational again. Problem is it's pointed to the wrong drive--after the first 'net fiasco I repatitioned my 2nd drive (which Win2k is on) and moved some things around. So I can't keep this 3GB install (w/ some extra programs) on my downloads drive (not enough room). So come this weekend I'm gonna reformat and install. But this time I'm gonna make sure to make a CD backup. So thanks for all your help and don't worry after i finish this message I'm gonna make a printout of my current TCP/IP settings (just in case I ever need them). Till we meet again.

David

 

[Slikkster]

Glad it's working again. I'm still intrigued, of course, as to what exactly was different, but that will remain a mystery. But it appears since that other guy had the issue that MS will have to identify and deal with it at some point!

Later man...