No Domain Controller Available

[Guest]

I am running active directory on a 2003 network. I have one machine that was
joined to the domain just fine. When I reboot the machine it tells me no
domain controller is available. I log on locally and run an ipconfig /all
and everything is fine. I can ping my servers by name. I know DNS is working
fine. I thought there was a netsh command to fix this but can't find the
article that addressed this issue. Any help would be greatly appreciated.

 

[Chuck]

I am running active directory on a 2003 network. I have one machine that was
joined to the domain just fine. When I reboot the machine it tells me no
domain controller is available. I log on locally and run an ipconfig /all
and everything is fine. I can ping my servers by name. I know DNS is working
fine. I thought there was a netsh command to fix this but can't find the
article that addressed this issue. Any help would be greatly appreciated.

If you don't setup the domain itself, and the client computers, just right, it
will not work reliably. Is your domain setup precisely as instructed:
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html

 

[Guest]

We have the domain setup properly and 300 pc's working just fine. I am only
having an issue with one PC. I have seen this in the past and ran a netsh
command to fix it but can't find my notes on the exact command.

 

[Chuck]

We have the domain setup properly and 300 pc's working just fine. I am only
having an issue with one PC. I have seen this in the past and ran a netsh
command to fix it but can't find my notes on the exact command.

Well, maybe there is a netsh command that's applicable. But you haven't
provided any details yet, so anybody can get a clue what command you need.
What's different between the problem computer and the others?
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html
<http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html

 

[Guest]

What more do you want? I told you have a 2003 active directory network. I
have an XP machine that was joined to the domain with no problem. When I try
to log in it gets no domain controller is available. I have 300 machines
that are setup the same way working fine. What other information do you need
to get a clue?

 

[Chuck]

What more do you want? I told you have a 2003 active directory network. I
have an XP machine that was joined to the domain with no problem. When I try
to log in it gets no domain controller is available. I have 300 machines
that are setup the same way working fine. What other information do you need
to get a clue?

I'm trying to help you here. I'm not in front of your computers - you are.

You've setup 300 computers, and you don't have enough experience with them to
get an idea how one computer could decide "no domain controller is available".

What are the differences between the working 300 and the problem 1 computer? I
can think of at least 3 - maybe you can think of some more. Maybe the problem 1
is not connected to the network. Maybe it is connected, but the domain is
ignoring it. Maybe it got dropped from the domain.

Maybe the first article has some ideas for you. Did you read it?

But work with me here. Nobody here can read your mind. And nobody here can see
your network.

 

[GTS]

Possibly the command was this one to rebuild the TCP stack?
netsh winsock reset catalog