Cannot login to domain

[jeeji]

Hi

I administer some lab machines on which I run daily tests of our
software.
The machines are part of the same domain.
The machines are reimaged daily because we run tests on them, and want
to ensure a certain initial state before we run the tests.
The funny thing now is that suddenly out of the blue, I cannot log into
the machines on the domain anymore.
I get the following error: "WINDOWS CANNOT CONNECT TO THE DOMAIN,
EITHER BECAUSE DOMAIN CONTROLLER IS DOWN, OR BECAUSE YOUR COMPUTER
ACCOUNT WAS NOT FOUND. PLEASE TRY AGAIN LATER. IF THIS MESSEGE
CONTINUES TO APPEAR, CONTACT YOUR SYSTEM ADMINISTRATOR"

The thing is that I can still see the machines being part of the domain
using the active directory MMC snap-in. Another funny thing is that
this system has worked for a long time without having any error of this
sort.


I can add the following information:
- This happened after a reimage, and not after one of the numerous
reboots the tests we run on the machines do.
- The machines have Win2003 Server installed
- The images created were create from the machines after they were
joined to the domain. So the SID registered in teh Active Directory
matches the key in the image/machine.
- The same issue happened 2 months ago too, and now I am seeing it
again.

Now I know how to solve this problem, and unfortunately solving it
requires me to create new images, so that the new AD SID matches the
image. So all I am asking for is, does anyone have any idea why this
could have happened, and why it happened to all the machines at the
same time.

Thank you very much in advance
Jeeji

 

[Pegasus \(MVP\)]

Multiposted.

 

[Richard G. Harper]

Multishame, because I might have had a multianswer ... but if someone else
has already done the homework ...

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Pegasus \(MVP\)]

So far the OP has not received a final reply to his second
post in "windows.server.general".

 

[jeeji]

Do I get the feeling that someone is insulted because I posted the same
question on different news groups. I am sorry for that, but I lack some
best practice knowledge and ticket here, and this is a clear sign of
it. I am sorry. I have not written that many posts to newsgroups, and
some posts I have written to newsgroups that are not monitored by
anyone. And I did not know the status of the newsgroups I posted to.

Could you please give me some response on the above.

Jeeji

Multishame, because I might have had a multianswer ... but if someone else
has already done the homework ...

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Multiposted.

 

[Pegasus \(MVP\)]

Nobody feels insulted but you're being informed about
newsgroup etiquette. By posting your question independently
in serveral newsgroups you cause a great waste of time: None
of the respondents can see any of the other replies, hence
there is lots of re-invention of the wheel. Respondents do not
like this one bit. Richard Harper is a top-notch expert in his
field but he backed right off when he saw the multi-post flag.

The answer is: Use cross-posting (in moderation) if you wish
to reach a larger audience. In this case every respondent can
see the replies posted in ***every*** newsgroup. You do
this by placing several newsgroup namesinto your address field,
separated by semi-colons.

A quick search on Google would have revealed much the
same thing.

Do I get the feeling that someone is insulted because I posted the same
question on different news groups. I am sorry for that, but I lack some
best practice knowledge and ticket here, and this is a clear sign of
it. I am sorry. I have not written that many posts to newsgroups, and
some posts I have written to newsgroups that are not monitored by
anyone. And I did not know the status of the newsgroups I posted to.

Could you please give me some response on the above.

Jeeji

Multishame, because I might have had a multianswer ... but if someone else
has already done the homework ...

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Multiposted.


Hi

I administer some lab machines on which I run daily tests of our
software.
The machines are part of the same domain.
The machines are reimaged daily because we run tests on them, and want
to ensure a certain initial state before we run the tests.
The funny thing now is that suddenly out of the blue, I cannot log into
the machines on the domain anymore.
I get the following error: "WINDOWS CANNOT CONNECT TO THE DOMAIN,
EITHER BECAUSE DOMAIN CONTROLLER IS DOWN, OR BECAUSE YOUR COMPUTER
ACCOUNT WAS NOT FOUND. PLEASE TRY AGAIN LATER. IF THIS MESSEGE
CONTINUES TO APPEAR, CONTACT YOUR SYSTEM ADMINISTRATOR"

The thing is that I can still see the machines being part of the domain
using the active directory MMC snap-in. Another funny thing is that
this system has worked for a long time without having any error of this
sort.


I can add the following information:
- This happened after a reimage, and not after one of the numerous
reboots the tests we run on the machines do.
- The machines have Win2003 Server installed
- The images created were create from the machines after they were
joined to the domain. So the SID registered in teh Active Directory
matches the key in the image/machine.
- The same issue happened 2 months ago too, and now I am seeing it
again.

Now I know how to solve this problem, and unfortunately solving it
requires me to create new images, so that the new AD SID matches the
image. So all I am asking for is, does anyone have any idea why this
could have happened, and why it happened to all the machines at the
same time.

Thank you very much in advance
Jeeji