NT 4 Wkstn not using DNS

I think I've seen this previously. My fix was to delete TCPIP, then delete the follow (if existing) registry keys:

HKLM\Software\Microsoft\NetBT
HKLM\Software\Microsoft\Tcpip
HKLM\Software\Microsoft\TcpipCU
HKLM\SYSTEM\CCS\Services\DHCP
HKLM\SYSTEM\CCS\Services\LMHosts
HKLM\SYSTEM\CCS\Services\'NetDriver'\Parameters\Tcpip
HKLM\SYSTEM\CCS\Services\NetBT
HKLM\Software\Microsoft\RFC1156Agent
HKLM\Software\Microsoft\Snmp
HKLM\System\CCS\Services\Snmp
HKLM\Software\Microsoft\Lpdsvc
HKLM\Software\Microsoft\TcpPrint
HKLM\SYSTEM\CCS\Services\LpdsvcSimple TCP\IP Services
HKLM\Software\Microsoft\SimpTcp
HKLM\SYSTEM\CCS\Services\SimpTcp
HKLM\Software\Microsoft\DhcpMibAgent
HKLM\Software\Microsoft\DhcpServer
HKLM\SYSTEM\CCS\Services\DhcpServer
HKLM\Software\Microsoft\Wins
HKLM\Software\Microsoft\WinsMibAgent
HKLM\SYSTEM\CCS\Services\Wins
HKLM\SYSTEM\CCS\Services\TCPIP

Then re-install TCP/IP as you have done. In my case, removiong IP from network did not remove all theregistry settings -

I dunno....I would look ata possible hardware failure. Did you try a different NIC?

I seems like that is the easiest fix up front, so I would start there are work towards the more difficult ones.

Bill Seay
Advanced Micro Solutions

Try pinging the fully qualified hostname. I.e., 'JOE' is considered to be NETBIOS name resolved via WINS and LMHOSTS, while 'joe.company.com' is considered to be a host name, resolved via DNS and hosts file. Also (not trying to insult your intelligence - but just in case:) where have you put the hosts file? In NT it goes under C:\winnt\system32\drivers\etc\hosts.

Ping this workstation from another box - see if it responds. Next use 'nslookup' to verify which server it uses for the look ups. You can use 'nslookup ' for a single lookup. Or you can type just nslookup without a server name to go into interactive mode. At the > prompt type the name to look up. If this does not work, at the > prompt type 'server ' using the IP address of your DNS server. See if you can connect that way.

Finally: IS your DNS server on the same subnet as your NT worksation? It might be a bad route. Use 'netstat -r' to display the routing table, and the 'route' command
to modify your ro

Ask the user what changes were made in Germany (Longshot!)
Check out the TCP/IP properties Tab, has anyone added new rogue WINS or DNS addresses, including Domain names.
Check out the Hosts and LMHosts files for new settings (or missing old settings.)
Try and get a similar laptop, or Workstation, and compare commands, what works, what fails.
Finally does ping ip address, or ping localhost work, if so then its a configuration problem, if not, then its a hardware or reinstall problem.

To tfazer,

Just a little humor, probably the laptop forgot something in Germany. hehehe

First, you may wish to check that the time zone in the laptop had not been changed since it went to a diiferent time zone and back, but only if it had beenchanged.

Secondly, in the DHCP Server, verify that the IP address that you gave to the laptop is in the DHCP's scope, if it has a static address, re-verify that you are using the IP address that correspond to the network.

Third, in the WINS (I assume that your network has one), re-verify that the laptop's computer name is entered correctly (it probably had changed to a German name). (Hey thats only a joke OK, don't get excited), but I still would check it anyway.

Fourth, in the RAS Server, See if the laptop computer name and its correcsponding IP address is still enabled in the RAS Servers clients. If you are using VPN, I suggets that you re-check your protocols.

Fifth, had you tried pinging the laptop IP address from any workstation in the networ