Cannot Logon to Windows 2000 Server

[BattleDroid42]

Windows 2000 Server refuses all logon attempts with proper credentials. Prior to this the only change made was the speed of the NIC. Have tried Recovery Manager, Safe Mode boot and even removal of the NIC. The server is a Compaq ML350 and Recovery Manager cannot see the disk array so is of no help either. Help?

 

[challiday]

Is the server a member server or Active Directory domain controller...?????

 

[ChicagoTechNet]

can you the DNS server? quoted from

http://www25.brinkster.com/chicagotech/

How to troubleshoot DNS problems

To correct DNS settings and troubleshoot DNS problems, you can 1) run nslookup from a command line is the default dns server the one you expect.
2) use ipconfig /all on client to make sure the client point to correct DNS server and the the DC server points to only itself for DNS by its actual tcp/ip address, and make sure no any ISP DNS listed in tcp/ip properties of any W2K/XP.
3) When the machine loads it should register itself with the DNS. If not, use ipconfig /regiesterdns command.
4) Check Event Viewer to see whether the event logs contain any error information. On both the client and the server, check the System log for failures during the logon process. Also, check the Directory Service logs on the server and the DNS logs on the DNS server.
5) Use the nltest /dsgetdc:domainname command to verify that a domain controller can be located for a specific domain. The NLTest tool is installed with the Windows XP support tools.
6) If you suspect that a particular domain controller has problems, turn on the Netlogon debug logging. Use the NLTest utility by typing nltest /dbflag:0x2000ffff at a command prompt. The information is logged in the Debug folder in the Netlogon.log file.
7) Use DC Diagnosis tool, dcdiag /v to diagnose any errors. If you still have not isolated the problem, use Network Monitor to monitor network traffic between the client and the domain controller.

Robert, MS-MVP & MCSE

http://www25.brinkster.com/chicagotech/

 

[AndyHo]

Had a similar problem when going from 10Mbs to 100Mbs. Turned out to be a bad patch cable. Caused all sorts of garbage to fly around the system and generally prevented any attempts to do anything beyond basic logons. Can you slow the system back down to 10Mbs?

Andy Holden

 

[BattleDroid42]

Server is not a domain controller and is not running active directory. The NIC speed was turned from 100Mbs to 10Mbs in error by a coworker. Can't change the speed back because we can't login.

 

[BattleDroid42]

Problem solved. The switch is hardwired for 100 Mbs so I swapped lines with a 10 Mbs connection (the APC) and was able to login. Thanks all!