Hi all,
I've gotten myself into a mess by simply "playing around"! My goal was to test one of the many administrator password reset tools so I could put one on a floppy and keep it in my arsenal for when a user at a client would foolishly unjoin their domain and not know the local passwords. I've succeeded in royally screwing up my daughter's computer, which was joined to the domain in our home network. I initially couldn't get the password utility to work at all. I could use my domain logins, but whatever I set the local Administrator password towouldn't work until I logged into the domain and then reset it back using the function in Control Panel.
Anyway, at some point it all got messed up because now I can't do anything with the domain and I can only log into the computer locally as the Administrator.
Here's what's happening and what I've done:
1. If I simply try to log into the domain using the Administrator account (the option is still there on the login screen, I get the following errror: "The system cannot log you onto this domain because the system's primary domain password is missing".
2. If I try to unjoin from the domain and go into a local workgroup, I get the following error: The following error occurred attmpting to unjoin the domain xxxxx.com: The revision level is unknown."
3. I thought I'd try to add domain users back using the Control Panel/Users function, but when I click OK to Finish, I get the following error: "The trust relationship between this workstation and the primary domain failed".
4. If I try to browse to the PC from the server, I get an error saying that there is no trust relationship between the 2 computers.
5. I have successfully renamed the computer, thinking that this might have changed these symptoms, but it didn't. Everything is the same as before doing that.
Help! I really don't want to wipe out the computer and start over again, but I have a feeling that's where I'm going.
Thanks for any suggestions.
Tom
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Sorry, I'd done that already as well (at least if I'm doing it correctly). In Active Directory I just deleted the Computer account. Other than that, I can't join the domain because the client PC still thinks it is joined! That's why I tried to unjoin the domain and move to a workgroup -- but unsuccessfully.
Thanks for the suggestion, though.
Under the connection properties (where you'd go to change the TCP/IP settings. Under this connection uses the following items, click on Client for Microsoft Networks, click on Uninstall. This will remove the Client for MS networks, which should clear all joins to domains. After the uninstall completes, go back into the same page and click on Install, choose client and install the client for MS networks.
That should solve the problem.
Collinglover, I thought that seemed like a good idea, but I seem to have dug myself in a little deeper instead. I was able to uninstall the Client for MS Networks, but now when I try to reinstall it, I get the following error:
"Could not add the requested component. The error is: The account name is invalid or does not exist, or the password is invalid for the account name specified".
I think this relates back to the fact that the password utility I mentioned in my initial description probably wiped out all logins/passwords.
Any other ideas? Or just reload?
Thanks,
Tom
Craylord, I would if I could! Right now the options to join or unjoin a domain or workgroup are grayed out with a line of text that says networking is not installed.
Per the previous message, I had uninstalled Client for MS Networks and now can't get that installed again.
Thanks for the suggestion,
Tom
Business Accounts
Answer for Membership
by: MrArubaPosted on 2005-09-14 at 14:37:55ID: 14885208
try removing the workstation on your domain controller.
then try to join the domain from the workstation