DNS Not Working

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

One of my Windows 2000 workstations can no longer find our domain. All
previous users of this system can logon since the system is using cached
information but when a new user tries to logon we get the "no DNS server was
available" error. I have ran the Windows 2000 repair process twice,
uninstalled and reinstalled TCP/IP twice, and have removed the NIC from the
device manager twice. If I logon as the local administrator and do an
ipconfig I'm getting a 169 IP address, which is not my network. The subnet
mask is also incorrect even though I have the system set for DHCP. If I
assign the system a static IP address, I still cannot logon to the network.
I have tried moving the system to 3 different ports with the same results,
can't find the domain. Finally, I removed the system from the domain and
tried to re-add it bit I get an error stating "...This condition may be
caused by a DNS lookup problem..." and to got to a MS link to troubleshoot.
I have checked all of the services and they are in fact running.
 
Crockett said:
One of my Windows 2000 workstations can no longer find our domain. All
previous users of this system can logon since the system is using cached
information but when a new user tries to logon we get the "no DNS server
was
available" error. I have ran the Windows 2000 repair process twice,
uninstalled and reinstalled TCP/IP twice, and have removed the NIC from
the
device manager twice. If I logon as the local administrator and do an
ipconfig I'm getting a 169 IP address, which is not my network. The
subnet
mask is also incorrect even though I have the system set for DHCP. If I
assign the system a static IP address, I still cannot logon to the
network.
I have tried moving the system to 3 different ports with the same results,
can't find the domain. Finally, I removed the system from the domain and
tried to re-add it bit I get an error stating "...This condition may be
caused by a DNS lookup problem..." and to got to a MS link to
troubleshoot.
I have checked all of the services and they are in fact running.
Click to expand...

If you give this machine a fixed IP which is valid. and a DNS that is valid,
can you ping around the network using IP and/or hostname.
If yes, you have eliminated a NIC/cabling issue.
If not, can you ping the IP you just set, ie yourself? if yes the TCP/IP
stack is OK(Software), problem lies with the NIC, either hardware of
configuration (Firmware)
 
The 169.x.x.x address means that the computer is not seeing your network or
your DHCP server. Check the obvious - cables, bad network card, etc.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
 
Using a static IP address allows me to ping devices on my network via IP
address or NetBIOS name.
 
Crockett said:
Using a static IP address allows me to ping devices on my network via IP
address or NetBIOS name.
Click to expand...

Ok as suggested already, the nacvhine is not seeing the DHCP server, either
the DHCP server is not running, or the machine cant see the network. The 2nd
has been illiminated. So the problem lies with the DHCP server.

Check the service is actually running. Ensure its configured correctly, and
if in a domain environemt ensure its authorised to service clients.

 
This is interesting. I did a parallel install of Windows and everything
works just fine.
 
Back
Top