Windows NT Logon Problem

[microsoftmis]

There are currently no logon servers available to service the logon request.<br>
<br>
I get this message on most of the Windows NT Workstation. I am running 1 PDC with 4 BDC's. I am using WINS for Internal clients, and DNS for the Internet. I have Proxy Server 2.0 on all the machines. We are a strict tcp/ip based system with no multi-homes servers. Any suggestions

 

[Zelandakh]

Obvious one - check the connection. Is the cable attached and so on...<br>
<br>
Choose OK and get to the desktop using a cached profile if you can. Ping the server by IP address. Check your ipconfig.<br>
<br>

 

[microsoftmis]

The cabling is just fine. Once you logon you have total network connectivity. It is a problem with the domain controller. I think. I have tried adjusting the time it takes for the server to respond with an acknowledgement and that doesn't work either. I have tried all the basics, and a smany advanced things as I can think of.

 

[Guest_imported]

In your TCP/IP properties, check your WINS server addresses. If the fields are empty try specifying them. If the fields are populated, even if you're sure they're right, try blanking them so the workstation has to broadcast a request for a WINS server.

 

[Zelandakh]

Alternatively, specify a specific IP address on the workstation that is in the same range as the server/s. That will rule out problems with the DHCP server.

 

[Guest_imported]

Go to a dos window and type in IPCONFIG. Then see what is going on! One thing you can try doing is going to your host file (WINNT/system32/drivers/etc/hosts) and seeing if there is a problem there. The host file contains the mappings of IP addresses to host names. If there is a mapping to the host with an incorrect IP address, I believe you might get this message. Also, if there is no mapping at all, try to set up the servers address here. For instance if your servers name is NT_SERVER and the ip address is 123.456.789.10 then you would add this line to the hosts file:<br>
<br>
123.456.789.10 NT_SERVER<br>
<br>
Gods Love,<br>
<p>John Vogel<br><a href=mailto:john@computerwiz.net>john@computerwiz.net</a><br><a href=

http://computerwiz.net>ComputerWiz</a><br>

 

[microsoftmis]

There is no DHCP problem, and it gets in WINS properties from the DHCP Server. The host file on both the client and server is empty. If it was a WINS problem I would not be able to resolve netbios names to TCI/IP addresses. Like I said once the client logs on there is total network functionality. Internet e-mail, network printers, the whole ball of wax. Any other ideas.

 

[Zelandakh]

If it works fine once it gets on but has trouble actually logging on and everything else in the world is fine, I would suggest it is not WS or server related. Have you checked whether your switches are running spanning tree or if they are using portfast? If the DHCP server comes back to the workstation before the switch enables bi directional comms then it will fail to see the server.

 

[Guest_imported]

I'll assume that you've checked your event log for obvious<br>
<br>
Check your DNS settings. You said that you had Proxy server 2.0 installed on all the clients, which I actually take to mean that you've installed the Proxy Winsock Client on all the PCs. <br>
<br>
If you have a DNS server specified in the IP Settings, that can and will redirect certain request to the external DNS server, which of course, knows nothing of your intranet. the Proxy should take care of resolving DNS.<br>
<br>