I think that happens only if you reset the account in AD and there is nothing attached to the name. In this case it does not seem to be a bad idea unless the machine is having hardware issues then they would need addressing first.
Jon On Mon, Mar 23, 2009 at 11:53 AM, Winters, Rick < [email protected]> wrote: > If you do that won’t the SID still be the same, shouldn’t this person > also delete the name from the AD or change the name of the pc in question?? > > > > *Rick Winters* > > Network System Support Analyst > > Merced County Human Services Agency > > Merced County MEDS Security Enforcer > > Merced County CWS/CMS Security Cop > > Ph: (209) 385-3000 *5308 > > [email protected] > > > > > ------------------------------ > > *From:* Terry Jezewski [mailto:[email protected]] > *Sent:* Monday, March 23, 2009 8:48 AM > *To:* Active Directory Admin Issues > *Subject:* Re: Computer Account Problem - AD > > > > I agree with this suggestion. *Try removing the machine from the domain > (from the problem machine), then reset the account and then readd the > machine.* > If you have more than one DC, either wait for replication or force > replication before adding back to domain after you reset the computer > account. > > Terry > > > [image: Inactive hide details for Jon Harris ---03/23/2009 11:45:25 > AM---Try removing the machine from the domain (from the problem mac]Jon > Harris ---03/23/2009 11:45:25 AM---Try removing the machine from the domain > (from the problem machine), then reset the account and then readd the > machine. If the > > > From: > > > Jon Harris <[email protected]> > > > To: > > > "Active Directory Admin Issues" <[email protected]> > > > Date: > > > 03/23/2009 11:45 AM > > > Subject: > > > Re: Computer Account Problem - AD > ------------------------------ > > > > > Try removing the machine from the domain (from the problem machine), then > reset the account and then readd the machine. If the machine is really > having issues then wipe and rebuild. Sorry this is the best I can come up > with. You might also look to make sure the NIC is functional, but in my > environment that has been rarely the problem. > > Jon > > On Mon, Mar 23, 2009 at 11:37 AM, <[email protected]> wrote: > > > I have a domained computer (on a Win3k domain) that all of a sudden when > the user tries to log on they get the message..."Windows cannot connect to > the domain, either because the domain controller is unavailable, or because > your computer account was not found." > > If I unplug the computer from the network, log the user on, then connect > back to the network, I have all domain capabilities. > > Tried resetting the computer account in AD, but to not avail. > > Troy Adkins > Network Administrator > Virginia House of Delegates > General Assembly Bldg. Room 815 > 804.698.1567 (O) > 804.771.7917 (F)* > *[email protected] > > ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ > ~ ~ > > > ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ > ~ ~ > > ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ > > ~ ~ > > > ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ > ~ ~ > > ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ ~ <http://www.sunbelt-software.com/product.cfm?id=400> ~
<<image003.gif>>
<<image002.gif>>
<<image001.gif>>
