Please Help. This is driving me crazy.

[jadab]

Have NT 4.0 PDC SP6a and 100 clients running Win98, NT 4.0 and W2K. Have Cisco switches between floors. They are fine. Having a sudden problem with various clients getting the No domain controller error (logging in with Cache). Also some of my servers are disappearing from Network Neighborhood suddenly. WINS and DHCP look fine. If I reboot my PDC all is well for a couple of hours. NIC looks fine and can be ping'd. Error 5719 Netlogon in Event Viewer. I have combed through the Knowledge base at Microsoft site and tried everything. I have event removed some of the Computers in Server manager, resynched, and readded to domain. Also tried having a client join a workstation reboot and then rejoin domain. This works for a little while then clients complain they cannot hit shares on a server and the server disappears from Netowork neighborhood. Any help would be appreciated.

 

[Guest_imported]

Conffigure All PDCs & BDCs Cisco ports to "Port Fast"

Gil Dori
Israel

 

[Guest_imported]

On the switch in question, do the following.

conf t
int fastether 0/xx duplex full speed 100 spanning-tree portfast

where xx = the port where your sever is logged into, and thats it. Depending on the size of your site you might also review PRIORITY levels on the switch, see the cisco web site for more info on that.

 

[Jhall0326]

I had a similar problem with the 98 machines forcing browse master elections. Had to disable master browser within the properties of File and Printer sharing on all boxes that were not to be a browse master for the subnet. If you have a BDC in each subnet, you can let it be your subnet master browser and disable the feature in all other boxes so that no elections are being forces.

Since the PDC is the Domain Master Browser, that may explain why rebooting tends to fix it.

This may be in left field but I hope it helps.

Jhall

 

[gjw12]

Sounds like a browsing problem. From the looks of it you use DHCP to assign Wins info. Try static assign of wins server Ip address to client PC. I have had a few client Pc's that like to do the same thing so I did this fix and they hit the network everytime.

 

[gjw12]

Forgive my inappropriate use of the word browsing - I should of said "browser" problem.