Removed from domain and unable to logon

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a Windows XP Professional workstation that was removed from a Win2003
SMS domain. It was assigned to a workgroup named MSHOME. Rebooted as
requested. At the logon window there is only the logon and password option.
None of the account logon ID's or passwords, including what was the domain
admin will allow us to get logged back on to rejoin the domain. Am I hosed?
 
I have a Windows XP Professional workstation that was removed from a Win2003
SMS domain. It was assigned to a workgroup named MSHOME. Rebooted as
requested. At the logon window there is only the logon and password option.
None of the account logon ID's or passwords, including what was the domain
admin will allow us to get logged back on to rejoin the domain. Am I hosed?
Click to expand...

It sounds like you just need to login with the local administrator
account which every computer has by default. If you can't figure out
that password what you will need is something like the UBCD at
http://www.ubcd4win.com which will allow you to boot up a gui
environment and reset the local admin password to something that you
know and then you should have no more problems.
 
For XP Home users:
Boot the computer into Safe Mode
Do this by pressing the F8 key after the Power On Self Test is finished,
until the Start menu appears.
This will get you to the correct menu window.
Once in Safe Mode, you will see the normally hidden Administrator account
and any other accounts.
(Note: Accounts are displayed alphabetically).
Use the Up/down arrow keys to highlight the 'Adminstrator' account;
Remember as mentioned above: The default password is a blank (no password
required).

For XP Pro users:
You do not need to go into Safe Mode.
At the Welcome Screen, do/press the Ctrl-Alt-Del keys twice to display the
Windows logon box.
Type in "Administrator" (without the quotes) and 'if' you assigned a
password when you set up Windows, then enter it. (Note: by default the
password is blank, no password need be entered)

Once your in, then:
Click Start/Run/and type in: Control Userpasswords2 and then press OK
Next click on the Advanced tab and then click Manage Passwords.

You may want to also create a new account while your at it.

JS
 
Hi JS,

Thanks for the response. One more piece of info. I tried the safe mode,
but the administrator account has, at some point, had a password attached.
No one knows what it was. I'm going to look into Pauls suggestion and see if
I can find something to let me back in.

JayHawk
 
JayHawk said:
I have a Windows XP Professional workstation that was removed from a Win2003
SMS domain. It was assigned to a workgroup named MSHOME. Rebooted as
requested. At the logon window there is only the logon and password option.
None of the account logon ID's or passwords, including what was the domain
admin will allow us to get logged back on to rejoin the domain. Am I hosed?
Click to expand...


By changing the computer from the domain to a workgroup, you
destroyed the trust between the domain and the machine. In doing so,
you've also rendered your domain login credentials as invalid. You'll
need to be physically connected to the domain network, you'll need to
have administrative privileges to the workstation, and you'll need to
have sufficient privileges on the domain. Then you can add the machine
back on to the domain, after having first deleted the computer's old
domain account (unless you've also renamed the computer).

Take the computer to your company's IT department for repairs.


--

Bruce Chambers

Help us help you:



They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell
 
I have a similar problem. For some reason, at some time, 2 of my computers
(both XP Pro, both wireless) failed trusting my domain (NT 4.0 sp6) which
they had been on for years. I had recently installed McAfee VirusScan Plus
2007 on one of them (which also housed my web server which stopped serving
right about then).

A few days ago, I tried to set up a share on the webserver. I was asked for
domain admin credentials, which I gave. I was told the password was wrong. It
wasn't. I tried several, all domain admins, all of which can log into other
computers.

Yesterday, I tried to get to an existing share on that server and was told I
didn't have permissions. I checked the share and noted that all my domain
accounts were not in it anymore. My share permissions had actually been
changed.

Today, I went to compare that to what was going on on my XP laptop, which
has had McAfee for a year now. And voila, the same problem. Domain
permissions were gone from the shares and I couldn't add them.

So I go to my NT server box and check Server Manager. I'm told for both of
those computers that "The trust relationship between this workstation and the
primary domain has failed."

I uninstalled McAfee. After much finagling (removing it from the domain,
adding it to a workgroup, and adding it back to the domain, rebooting between
each), I finally got the webserver back on. I had actually tried changing
its name, to which it replied that it was it's original name and put it back
on the domain.

I tried the same with the laptop. To no avail. I've removed it from Server
Manager. (It never actually leaves the list.) I've set it to workgroup.
I've readded it to the domain, both via Network Identification on the laptop
and Server Manager on NT. Repeatedly. I've changed it's name. Same thing:
trust relationship failed. I've tried restoring from a restore point. The
only one I had was from 4:15 this morning. I tried it. It still won't trust
the domain to which it belongs.

Any help? (I studied MCSE courses under NT 4 but 1) it's been a long time,
and 2) I only took half the tests before deciding I didn't want to be a
network admin. I am, however, an MCDST. I've been working in tech support
for 8 years. I'm at a loss at the moment.)

--Gabrielle
 
My guess is (having been an Admin for NT 4) is that McAfee is the problem,
which you probably already know by now. I say this because a number of
software packages which ran fine on a local desktop did not run or were not
supported on NT.

You may also want to check the firewall settings in this product as they may
be getting in the way.

JS
 
Thanks. I already tried uninstalling McAfee on the laptop. It didn't help.
The only active firewall is my router. Windows Firewall and McAfees are both
disabled.

Tried using it on an ethernet cord instead of just wireless but still no luck.

--Gabrielle
 
Back
Top