Windows cannot connect to the domain either ....


I have installed Windows 2003 R2 with all updates.  The details is given below:

Host name :  corporate
Domain name :
FQDN             :

The DNS is installed in the same server.  I can resolve corporate, and through this DNS.

The problem that I am facing is given below:

All my Windows XP workstation is joined to the above mentioned domain.  Some of the machine, daily I am getting the following messges:

"Windows cannot connect to the domain either because the domain controller is down or other wise unavailable, or becuase your computer account was not found"

Please help

Who is Participating?
PAQed with points refunded (500)

Community Support Moderator
Hi liji77,

make sure dns only pointing to the server and check your servers logs
Irwin SantosComputer Integration SpecialistCommented:
outside of jay_jay70's would seem like a connectivity problem
- check your cabling
- change the port on the switch that the server is attached
- replace you network interface card
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

liji77Author Commented:
hi ,

Yes...DNS is pointing to the Server only.  I am sure becasuse I have alloted the IP, gateway and DNS through DHCP only.

If I again re-join the XP workstation to the start working properly.  so it the problem of connectivity issue?
My Switches are Brand New Link-Sys Layer 2 switch.
so after your second join all goes fine?
liji77Author Commented:
These are the following logs from the server:

The session setup from computer 'GP-104' failed because the security database does not contain a trust account 'GP-104$' referenced by the specified computer.  

If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. Otherwise, the following steps may be taken to resolve this problem:  

If 'GP-104$' is a legitimate machine account for the computer 'GP-104', then 'GP-104' should be rejoined to the domain.  

If 'GP-104$' is a legitimate interdomain trust account, then the trust should be recreated.  

Otherwise, assuming that 'GP-104$' is not a legitimate account, the following action should be taken on 'GP-104':  

If 'GP-104' is a Domain Controller, then the trust associated with 'GP-104$' should be deleted.  

If 'GP-104' is not a Domain Controller, it should be disjoined from the domain.

For more information, see Help and Support Center at
i have never seen anything like it, yet joining it back to the domain fixes it so there is your solution - very very strange though
liji77Author Commented:
after second join...all goes fine....
would love to know where that is coming from!

will research some more tomorrow as its late here

you can safely assume your fix is a rejoin, maybe try a few of the clients using the network IS wizard - its a better way of doing things
mcsweenSr. Network AdministratorCommented:
I have seen this issue in a couple of instances.  Not sure if they apply to you.

1. If you image the workstations but do not run sysprep on them they end up all having the same SID.  When you disjoin/rejoin a new SID gets created and allow the workstation SID in the domain to be unique.

2. If 2 or more computers have the same netbios name and are joined to the same domain only the last one will work since the new computers keep replacing the previous computer's domain account.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.