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 2 of 3)   Prev   01 | 02 | 03   Next
Thread display: Collapse - | Expand +

All Comments

Collapse -

by Roger In reply to

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

Collapse -

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

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.

Collapse -

by Roger In reply to

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.

Collapse -

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

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

Collapse -

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

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 <domainserver_ipaddress> -p both -r 135:139 -sl -l portqry.txt

Local computer name:

<Localcomputer>

Querying target system called:

<domainserver_ipaddress>

Attempting to resolve IP address to a name...


IP address resolved to <Domainserver_name>

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

Collapse -

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

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.

Collapse -

by Roger In reply to

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.

Collapse -

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

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.

Collapse -

by Roger In reply to

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

Collapse -

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

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

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

Related Discussions

Related Forums