Windows Forum

Ask something
Discussion Locked

Second DNS entry causes logon to fail

0 helpful
2 replies

by basswr

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have several PC's with Win95B. They logon to an NT 4.0 server across a wide area network. The server location is specified in the LMHOSTS file. When one DNS entry is placed in the TCP/IP properties, the logon works reliably. When a second DNS entry is added to the TCP/IP properties the logon fails. The only way to cause the logon to be successful is to remove the 2nd DNS entry. Other identical PC's that are completely current with critical updates and recommended updates will perform properly with both DNS entries in the network settings. Can anyone provide the solution to this problem or provide the patch or update to allow the 2nd entry to work.

2 replies

by d_v ant

My question is, why do you need two entries in the LMHOSTS file for the server? There should only be one entry for the server with the correct name and ip address. If you are placing a second entry with different information, then the pc is trying to connect with the wrong information and cannot find the server. The PC will look in the LMHOSTS table until it finds the first entry for the computer it is trying to connect to. If there is a second entry farther down in the table, it will never seeit. That may be why the other PCs can still connect. Verify the settings for the server and edit the LMHOSTS table to the valid settings only. Delete any other references to the server in the table and everything should be good.

This discussion is closed to new replies.