Now i can’t resolve any hostnames. My email doesn’t work unless i use the IP for the servers and i have to run through the proxy for http to work. Also - i cannot ping anything unless its an IP.
Windows 2K service pack 3 in case you were wondering.
Seriously, though, with a little more information we might be able to help. How are you’re DNS configuration settings set? Automatic? Or do you have a DNS entry entered? Whats the result of typing ‘ipconfig /all’ at the command line? Have you tried ‘ipconfig /flushdns’ to clear the DNS cache?
micilin, who’s tried SP3 without any obvious problems. (Well apart from the EULA! :))
A) Can you ping it? If you can’t, then you’ve a problem other than DNS.
B) If you can, run ‘nslookup’. It should tell you then name and IP of your default DNS server. If it can’t talk to the DNS server you’ll get an error.
C) If you can, then type a couple of host names into nslookup, eg. ‘boards.straightdope.com’*, ‘www.microsoft.com’. What are the results?
*By the way how are you posting if your computer’s knackered?
As ToF said. What error do you get, and whats the IP of the DNS server? My immediate reaction without any further detail (well second to immediate, see below) is that the IP address is wrong, or the DNS server has decided not to serve you for some reason.
I work in IT BTW, and when someone says ‘I get an error when i run X’ the temptation is to suggest to them that they need a psychic, as I can’t divine what the problem is without knowing what the error is. No offence meant.
And MarkyDeSade, SP3 is released, but there hasn’t been the usual sh*tstorm that surrounds a particularly crappy SP relaese, so I wouldn’t worry too much about it.
If you post the IP of the DNS server then we can try and run an NSLOOKUP against the server to see if it fails for us as well.
Of course, There also is not telling how much of “Bill & Ted’s Excellent Shareware” is installed on your system which can cause problems. I have been running SP3 since early MS internal Beta copies on both my workstations and my servers (test servers only) and have never had a problem with my name resolution being hosed.
I am alomost 100% sure that this is not the issue, but check your system for a HOSTS file. If you find on, then rename it.
if you installed the support tools off of the Windows 2000 CD then try running NETDIAG /test:dns
If you can get there then the full details of NETDIAG can be found at this address:
Sorry for my trite response above. I was just leaving work and wanted to sum up several points in a single sentence.
I do sympathize with your plight. What I meant by my post was that unless you have a great need for some fix from a service pack from M$, don’t install it until a month or two later after several companies/individuals/SP testers have tried it out and reported any bugs. These people are usually prepared to deal with situations like yours and do not install a SP on a critical production machine.
On to your OP. It sounds like your ISP’s DHCP server has stopped handing out the correct DNS servers or for some reason their DNS servers don’t want to handle your requests. The first thing I would do is uninstall the SP if you went with that option. Just to get yourself back on track.
Second thing I would do is call your ISP and ask for some troubleshooting tips. I haven’t read up on SP3 but does it replace the TCP/IP stack? If it does perhaps your ISP’s routers can’t deal with the new stack for some reason. Have you tried “ipconfig /release” and “ipconfig /renew”? Usually if my ISP is acting up I won’t get an IP address with the renew and I’ll have to call them. Or if I do get an address the DNS or subnet mask will be wrong.
It could be that SP3 replaced a critical .sys driver file for your ethernet card. If you’ve got a different brand laying around try it out.
All in all, beware SPs from M$. Sometimes they’ll break more things than they fix.
Upon reading the list of fixes for SP3, specifically the [networking fixes](http://support.microsoft.com/common/canned.aspx?R=d&H=List of Networking Fixes in Microsoft Windows 2000 SP3&LL=support&Sz=kbWin2000sp3fix AND kbNetworking&Fr=&DU=&SD=GN&LN=EN-US&CND=1&VR=&CAT=&VRL=&SG=&MaxResults=200), I see that they did indeed “improve” the TCP/IP stack software.
Looks like SP3 is not meant for Windows 2000 Home edition. What service pack were you at prior to SP3 installation?
If you don’t have the option to uninstall SP3, try reapplying it. Hopefully things won’t get worse.
Here’s one more tip: Put your TCP/IP settings back to automatic if they aren’t already. Do an “ipconfig /release” and “ipconfig /renew” to get whatever settings your ISP’s DHCP server will give you. Then do a “tracert boards.straightdope.com” and see if you can determine where your packets are dying. It sounds like your gateway is working for you since you aren’t getting “Destination net unreachable”. That’s all I’ve got for now.
SenorBeef - you’re right. In a dropdown list for Windows 2000 resources at microsoft.com I saw “Windows 2000 Home” and thought it meant a Home Edition, rather than what it actually was, the Windows 2000 home page. I figured maybe they had done up a Home version like they had for XP.