General discussion

Locked

I can not log into a domain

By Roger ·
I have a problem logging into a domain. I receive the message "The system cannot log you on now because the domain <domainname> 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?

This conversation is currently closed to new comments.

23 total posts (Page 1 of 3)   01 | 02 | 03   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by ewgny In reply to I can not log into a doma ...
Collapse -

by ewgny In reply to

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

Collapse -

by ewgny In reply to

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

Collapse -

by Roger In reply to

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

Collapse -

by Roger In reply to I can not log into a doma ...

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 I 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 I 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 ^..?

Collapse -

by Roger In reply to I can not log into a doma ...

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

Collapse -

by Cactus Pete In reply to I can not log into a doma ...

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.

Collapse -

by Cactus Pete In reply to

MS has a utility called portqry, sounds like what you want.

http://support.microsoft.com/default.aspx?scid=kb;en-us;310099&Product=win2000

Remove any spaces in the above link. Else:

http://tinyurl.com/2ltps

Collapse -

by Roger In reply to

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.

Collapse -

by Teamadmin In reply to I can not log into a doma ...

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.

Back to Windows Forum
23 total posts (Page 1 of 3)   01 | 02 | 03   Next

Related Discussions

Related Forums