"No Domain Controller Found"

[seanc]

I didn't notice there was a network forum before, so I'd posted this in the OS forum before... Oops. Sorry. But anyway, here's the problem...

At my work I'm the sole network admin / IT guy... Right now a problem has cropped up recently that I'm at a loss to solve. Hopefully you guys can help.
On some of the old PC's here whenever the user reboots their PC (which happens a lot, they're all developers) and try to login they get an error message something like:

"no domain controller can be found, you will be logged on using cached account information"

All the systems that have the problem are about the same config as below:

Celeron 333mhz
128MB RAM
3Com 10/100 Etherlink 3C905B ethernet card
Windows NT Workstation SP6

The domain controller is a WinNT Server 4 with SP6.

I'm at a total loss and now the problem is starting to plague my boss as well!!!

Please help.

Thanks

Sean

[Mntsnow]

Has your network config changed any? Are the effected computers actually about to "see" the domain controller? Sounds like to me that something has happened to maybe the subnet (routing?) and the effected machines are now unable to locate/communicate with the domain controller.


In short....double check your network setup (routing tables and or network connections to the domain controller)

[tantone]

Follow the link to the knowledgebase on MS's website. Once there, search for the following article numbers:
Q185081
Q150963 *
Q202840
Q163204

I marked the second one because it may prove to be more pertinent that the others.

http://search.support.microsoft.com/kb/c.asp?fr=0&SD=GN&LN=EN-US

Good luck! I know how hard it can be to be the only person to handle these problems.


[This message has been edited by tantone (edited 06-04-2001).]

[muno]

If the computers cannot access network at all (no web, no local) then your cabling is screwed. Check that they're all connected.
I had that problem when I forgot to plug the cord in my stack to the right port.
-M

[seanc]

Hi guys,

Thanks for all your help and suggestions. The MS knowledge base articles were ones I couldn't find and the one Q163204 (setting a domain logon timeout delay) worked.

Thanks again guys.
Sean