On a single 2K machine in our AD call center we have a machine that no one can log on to, upon investigation we found that it was no pulling policy. Although it shows to be part of the Domain, both in AD users and computers and in the Computer properties applet, when trying to remote to it, we get the message a trust relationship could not be established. We also get that trying to rejoin the machine to the domain. We have reimaged it several times to no avail. Any ideas would be appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Windows 2k Client problem
- Thread starter cldboone
- Start date
terrywilson
MIS
When you say reimaged, are you updating the sid for the system? I've never done it but I imagine it wouldn't be very happy if you tried to present it with the same sid as another pc under a different name.
To this end, you could use the tools with ghost to change it or try a fresh install - non imaged, a good old fashioned install.
In addition you may have an orphaned entry that you need to manually edit with command line tools to get rid off; I had this problem with a failed domain controller and had to resort to using command line tools to clean it up out of the tree. So if a fresh install itself fails, have a look at giving the PC a slightly different name (I am assuming you deleted the account from AD if it was still there once you disjoined the domain?).
To this end, you could use the tools with ghost to change it or try a fresh install - non imaged, a good old fashioned install.
In addition you may have an orphaned entry that you need to manually edit with command line tools to get rid off; I had this problem with a failed domain controller and had to resort to using command line tools to clean it up out of the tree. So if a fresh install itself fails, have a look at giving the PC a slightly different name (I am assuming you deleted the account from AD if it was still there once you disjoined the domain?).
- Thread starter
- #3
I ran into this a while ago. My solution was to run the network ID wizard and have the pc drop down into workgroup mode.
Then go to AD and remove the old computers account. Do not create a new one.
After the PC reboots, re-run the network ID wizard and re-join the domain. The wizard will prompt you to create a new computer account when it does not find the one you deleted.
Then go to AD and remove the old computers account. Do not create a new one.
After the PC reboots, re-run the network ID wizard and re-join the domain. The wizard will prompt you to create a new computer account when it does not find the one you deleted.
- Thread starter
- #5
- Status
Similar threads
- Locked
- Question
- Locked
- Question