Discussion Locked

No Domain Controller

0 helpful
16 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Occasionally, some of my workstations are unable to communicate with my NT server using TCP/IP. If I ping a troubled workstation from the server, then the workstation can reach the server. This has happened 2 or 3 times in the past year. Rebooting the server seems to clear it up. This usually affects several clients at a time.

16 replies

by randelman

Do you normally reboot the server as pasrt of normal maintaince? This should be done at least once a month. Try that and it might solve the problem that you are having.

by cavedweller

Try installing the latest drivers for your network interfaces or re-installing your current service pack.

by tareed

If you are using cisco switches on your network you might want to configure the ports with portfast. For help on this depending on the model of switch visit cisco's web site. This might clear the problem up.

by jmpmcse2k

I've seen this on Windows 2000 machines as well. The workstation would be able to log onto the network fine one day and not be able to log on at all the next day. I think this problem is more evident in Win2K than any other O/S I've seen.

What I do is this -- dump TCP/IP from the workstation and then reinstall it. This sounds lame, but it works.

by estebandelatorre

Servers MUST be rebooted depending on how heavy is the load. For a PDC & BDC, once a month, for a file system, onece a week, a web server two or 3 days, no more, or it will hang in the worst moment.

Also check the traffic in that moment, the server may be slow if a big copy across the lan is taking place.

by jayen

Dearest friend,

I would like to suggest you two things.

1) Apply DHCP server.
2) Check your I/O block or UTP cabling for those nodes. Strongly i recommed that u re-punch the pair of cable on I/O Block side, and re-crimp your utp cable's. (RJ45)

Jayen

This discussion is closed to new replies.