ascoredhat
New Member
Hello
After moving a couple computers in my office's network due to problems with crashed hard drives, switching with working computers while getting things fixed, etc., there seems to be a message that comes up after logging off and then trying to log back in:
Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable or because your computer account was not found. Please try again later.
I know this is related to switching around computers, adding new hard drives and all the other Frankenstein fixes, and from what I gather from googling the problem it has to do with duplicate accounts or IP address change thingies or what not, and I "think" I've read about removing the computer from the domain, putting it in workgroup, rebooting, putting it back in the domain, or also rebuilding the TCP/IP stack, or messing with the domain controller.
Here's the thing... I am not real computer savvy and I have no idea at all how to do any of those things. For every tip of "remove the computer from the domain and..." I answer "HOW do I remove it?" or "add it back to the domain..." again I say "HOW? Where on the computer do I do this?" Or "open the domain controller and then..." "WHERE is the domain controller?"
In other words, assume I'm a complete idiot (you're not too far off the mark) and could someone please give me advice on how to fix my network so I straighten out the confusion the domain seems to now have with allowing the "fixed" computers access, and in a "step by step" manner explaining where to find things like controllers and DNS's and IP's and what have you? Believe me, I would be extremely grateful.
Oh, I have a network with one server with Windows Server 2000 and six workstations with XP Pro. And before the moving of a couple computers, things were fine in regards to logging in.
Thank you very much for any help that can be offered.
After moving a couple computers in my office's network due to problems with crashed hard drives, switching with working computers while getting things fixed, etc., there seems to be a message that comes up after logging off and then trying to log back in:
Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable or because your computer account was not found. Please try again later.
I know this is related to switching around computers, adding new hard drives and all the other Frankenstein fixes, and from what I gather from googling the problem it has to do with duplicate accounts or IP address change thingies or what not, and I "think" I've read about removing the computer from the domain, putting it in workgroup, rebooting, putting it back in the domain, or also rebuilding the TCP/IP stack, or messing with the domain controller.
Here's the thing... I am not real computer savvy and I have no idea at all how to do any of those things. For every tip of "remove the computer from the domain and..." I answer "HOW do I remove it?" or "add it back to the domain..." again I say "HOW? Where on the computer do I do this?" Or "open the domain controller and then..." "WHERE is the domain controller?"
In other words, assume I'm a complete idiot (you're not too far off the mark) and could someone please give me advice on how to fix my network so I straighten out the confusion the domain seems to now have with allowing the "fixed" computers access, and in a "step by step" manner explaining where to find things like controllers and DNS's and IP's and what have you? Believe me, I would be extremely grateful.
Oh, I have a network with one server with Windows Server 2000 and six workstations with XP Pro. And before the moving of a couple computers, things were fine in regards to logging in.
Thank you very much for any help that can be offered.