Windows Forum

Ask something
Discussion Locked

I can not log into a domain

0 helpful
23 replies

by roger 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a problem logging into a domain. I receive the message "The system cannot log you on now because the domain is not available." I have 4 computers attached to a 56K frame relay which then connects to the remainder of our network. All the pc systems are running Windows 2000 SP2. I have 1 machine which will not log on. I upgraded it to Windows 2000 SP4 but still cannot log on. Any suggestions?

23 replies

by ewgny

Post any associated event logs
ipconfig /all to check that the workstation has it's proper DNS
Last I would rejoin it to the Domain

by ewgny

The E100B event is usually associated with the NIC card, indicating a hardware failure or failure of the NIC to negotiate with a switch.

With that failure, the PC is off the network, and thus can't locate a DC for a logon

Check that the NIC is seated properly, and the driver is correct. also try setting the card to Auto Detect for link speed and Duplex in the NICs
properties in Device manager.

try pinging 127.0.0.1
try pinging the Domain Controller
at the command prompt run
ipconfig /all
Post your results

by roger

This one left me where I already was... I had already done these steps and went nowhere.

by roger

I have 2 entries in the event log that might be related to the problem:

Entry #1
Event Type: Information
Event Source: E100B
Event Category: None
Event ID: 8
Date: 4/14/2004
Time: 1:19:23 PM
User: N/A
Computer: SVH02486
Description:
Adapter Intel(R) PRO/100 VE Network Connection: Did not receive auto-negotiation advertisement from link partner. A full duplex connection may be available
Data:
0000: 00 00 04 00 02 00 58 00 ......X.
0008: 00 00 00 00 08 00 04 40 .......@
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 08 00 04 40 ...@

Entry #2

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 4/14/2004
Time: 1:19:56 PM
User: N/A
Computer: SVH02486
Description:
No Windows NT or Windows 2000 Domain Controller is available for domain SEBAST. The following error occurred:
There are currently no logon servers available to service the logon request.
Data:
0000: 5e 00 00 c0 ^..?

by roger

Attempting to add the pc to the domain again fails with a message stating that the domain cannot be located.

by cactus pete

You likely need to look at the router(s) between you and the domain server. Either it isn't allowing traffic through the interface [both ways] or you are not passing port 135-139.

by roger

This helped me to confirm that the connectivity between the PC and the Domain Controller should exist. The PC appeared to be timing out on an attempt to locate the domain controller.

by teamadmin

it is conectivity problem it doesn't mater SP2 or SP4 try ping 127.0.0.1 and domain controller
try changing the network card pci slot. change your card properties of "link speed/duplexmode " to Auto negotiation. if it is old card change the network card.

by roger

The card is an internal part of the motherboard. I needed a solution that would not involve installing another NIC.

by djrampant

I would suggest you find out exactly what speed the hub/switch your pc is connected to and fix the speed of the nic accordingly. eg. 100MB Full Duplex.

Then check you have the correct ip address allocated to your machine, and that you can ping other 3 machines on your subnet. If you can, reboot and retry joining the domain. If you cant, then address this before even considering logging on to the dmain.

Good luck.

by roger

Since I already stated that I could ping any machine on the subnet the PC is on, and could also ping the Domain Controller, this advice did not help.

by roger

Thanks for the suggestions so far... I have successfully pinged 127.0.0.1 (localhost), the Domain controller, and other pc's on the network. I can go through the gateway and open Internet web pages with no problems. Do you know how I can test to see if the ports are being blocked?root

by roger

I ran a portscan using Microsoft's portqry.exe version 2. Here's the results of the query-- Does it indicate a problem?

PortQry Version 2.0 Log File

System Date: Fri Apr 16 11:31:49 2004

Command run:
portqry -n -p both -r 135:139 -sl -l portqry.txt

Local computer name:

Querying target system called:

Attempting to resolve IP address to a name...

IP address resolved to

querying...

TCP port 135 (epmap service): LISTENING

UDP port 135 (epmap service): LISTENING or FILTERED

TCP port 136 (unknown service): NOT LISTENING

UDP port 136 (unknown service): NOT LISTENING

TCP port 137 (netbios-ns service): NOT LISTENING

UDP port 137 (netbios-ns service): LISTENING or FILTERED

Using ephemeral source port
Attempting NETBIOS adapter status query to UDP port 137...

Server's response: MAC address 0010b541e9eb
UDP port: LISTENING

TCP port 138 (unknown service): NOT LISTENING

UDP port 138 (netbios-dgm service): LISTENING or FILTERED

TCP port 139 (netbios-ssn service): LISTENING

UDP port 139 (unknown service): NOT LISTENING

========= end of log file =========

PortQry developed by Tim Rains

by yntbom

Did you try going into the my network places to see if the connection is there? Check your tcpip settings if it is not connecting automatically. Also you should try to disjoin from the domain and try to rejoin after you take out your nic card and replace it.

by roger

I already stated that I could see the machine on the network, simply couldn't log into it. Also I have an internal NIC on the motherboard and didn't want to replace it.

by emiaj

I once had a similar issue and after several attempts (checking connection, nic cards, etc.), I disjoined from the domain by adding it to a WORKGROUP and then re add it to the domain. At least it worked for me.

by roger

Couldn't reconnect to the domain as the computer wouldn't communicate with the domain controller.

by chris

This might sound silly, but it is worth a try - it has always worked for me.

If network connectivity is working (you mentioned you have 4 machines there, and only 1 is not working) - everything appears to be setup correctly from a network standpoint. I would ensure the machine is first taken out of the domain (if it was in it originally). If the NIC card is set to AUTO/AUTO, I would change it to 10 half duplex (this speed always works). I would then modify the LMHOST file to include the name and IP address of the Domain controller.

A sample LMHOST file is included in all windows systems. Check your Windows\system32\drivers\etc directory for LMHOST.SAM.

Copy that file to your LMHOST. (no extension) file, and modify it to include you DC information. Also ensure that LMHOST is being used (check IP settings).

This has worked for every remote system I ever installed (a lot) and had problems with.

Let me know if it helped any.

Chris

by chris

Sorry, I forgot (wife was yelling at me ;-)

After modifying the LMHOST file - try to re-add the machine to the domain.

Chris

by roger

LMHOST Solved the problem: IPADDRESS machinename DOM:domainname PRE:

PC needed a full reboot after this change - restart did not see the change.

Thanks ALL for your assistance!

This discussion is closed to new replies.