Dial-up fails to allow DNS

[Matt Silberstein]

My dial-up suddenly stopped working. I connect, but can't resolve any
names. I tried ipconfig /registerdns and got this response:

Windows 2000 IP Configuration

Error: The system cannot find the file specified.
: Refreshing DNS names


If I do a ipconfig /displaydns I get

Windows 2000 IP Configuration

------------------------------------------------------------------
Record data for type could not be displayed

localhost.
-----------------------------------------------
Record Name ....

Then it gives some valid records.

I have a valid DNS and I can ping my DNS.

Any clues?

 

[Michael Johnston [MSFT]]

Is this a Windows 2000 Server or Windows 2000 pro box? At the command prompt type "ipconfig /flushdns" and test name resolution. If it still fails, at a
command prompt type "nslookup" and press enter. This should default you to the prefered DNS server. At the ">" prompt type "www.yahoo.com" and press
enter. Does this resolve? Is it the correct IP address? If it still doesn't resolve, verify that you don't have any firewall software blocking DNS queries.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[Matt Silberstein]

Is this a Windows 2000 Server or Windows 2000 pro box? At the command prompt type "ipconfig /flushdns" and test name resolution. If it still fails, at a
command prompt type "nslookup" and press enter. This should default you to the prefered DNS server. At the ">" prompt type "www.yahoo.com" and press
enter. Does this resolve? Is it the correct IP address? If it still doesn't resolve, verify that you don't have any firewall software blocking DNS queries.

All the network stuff, nslookup, etc. seemed fine. Actually it turned
out to be something different. For some reason my DHCP client was not
running. It was set to automatic, so it should have been running. And
I had an IP address and all, so that was not the problem. I went to
services and saw that the DHCP client was not started so I started it.
Then the system worked fine. And worked when I re-booted. Now I had
rebooted several times in trying to fix things so that was not it.
And, as I said, the service was set to automatic, so it was not that
setting that was the problem. I guess there was something that was
preventing it from starting automatically and that once I manually
started it it cleared up. Odd though.