Discussion Locked

Can't log into Domain with Tcpip

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
My users are suddenly having to wait 20 seconds or so to log in to my nt4 server. Initially this was nearly immediate. In troubleshooting this I decided to remove Ipx from one workstation and after I rebooted I was given the No Domain to log into error. I checked a few more clients and it was the same for all. I can ping the server from anywhere but I can't log in (no domain found) When Ipx is loaded again the logins work but work slowly. The server's ip, netmask, gateway, etc etc are all correct and the machine uses the internet without a problem. Any solutions?

13 replies

by andrewf1

have you checked the "client for microsoft networks" properties, and made sure it s set to logon to windows nt domain and it has the right domain listed

by andrewf1

Okay scratch what I wrote earlier I was actualy reading a question from a friend and gave you the answer, my bad sorry

by andrewf1

To your question,
#1 20 seconds, well I guess 20 seconds is a lot to you???
#2Determin workstation as either 95/95/ workstation or 2000 nt?
#3 what additions to the network have been made or to the server possible to the workstation.
#4 have you done youe server and system performance checks.."asstandard" mcse adive or what...hehehe

by cricket_moon

Sounds to me like you are not using TCP/IP to connect. Remove IPX if you are not using it for Novell. If you are, make sure that it is forced to 802.3.

by gentryc

Check these things first.
What protocols are on the server? TCP/IP? IPX?
What Protocols are on the workstations? TCP/IP? IPX?
Check the workstations to see what the default login method is.
Check to see if tcp/ip is bound to the adapter andwhat services the protocol are bound to. If both, move tcp/ip to the top for the default protocol to be used.
Last remove all protocols, reboot server, reinstall tcp/ip,reboot,service pack it,reboot, then check the bindings again to make sure it is correct.

Check ping to several workstations to make sure connection is there.

by dgnall

It sounds like a NetBIOS problem to me. With IPX enabled, you may have NetBIOS over IPX enabled, but no NetBIOS over TCP/IP. (This is a checkbox in the TCP/IP properties on the client). Either way, the latency you are experiencing is because the NetBIOS name resolution for the domain is being done over IPX, and your binding order is slowing this process (I am assuming your PDC and BDCs are also running IPX).

If NetBIOS is enabled over TCP/IP, then you have a NetBIOS name resolution issue. This is probably a WINS problem (if its running).

You can try verifying this by adding a line to the client's lmhosts file in the following format:

10.0.0.1 servername #PRE #DOM:domain

Be sure that you rename the lmhosts file from its default of lmhosts.sam to just lmhosts (found in %systemroot%\system32\drivers\etc).

If you are using a Win2k client, then type nbtstat -RR at a command prompt. This will flush and reload the NetBIOS name cache. Then try logging on to your domain again.

Good luck...

This discussion is closed to new replies.