Log on when the domain is not present

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

Guest

A user has changed his domain to a workgroup on his own machine (this
workgroup would have been a part of the network running on the vmware on the
Windows XP host). The host is Windows XP with service pack 2.

Now he can't log on to his machine. At the log on screen he gets a message:

"The system could not log you on. Make sure your user name and domain are
correct, then type the password again."

Why can he not log into the machine without the network access? Is there any
way around this?

Thanks a million.
 
If he has removed the computer from the domain, then he'll have to log
in with a local account on the workstation to which he is attempting to
log in.
 
Thank you Kerry,

Unfortunately, that does not work either. We tried logging on in safe mode
but that didn't work either. We are really stuck here :(
 
00sqroot(49) said:
Thank you Kerry,

Unfortunately, that does not work either. We tried logging on in safe
mode but that didn't work either. We are really stuck here :(
Click to expand...

You can find a utility to remove the administrator password here:

http://home.eunet.no/pnordahl/ntpasswd/

You will need another computer that has a CD writer to create a bootable CD
with the utlity on it.
 
00sqroot(49) said:
A user has changed his domain to a workgroup on his own machine (this
workgroup would have been a part of the network running on the vmware on the
Windows XP host). The host is Windows XP with service pack 2.

Now he can't log on to his machine. At the log on screen he gets a message:

"The system could not log you on. Make sure your user name and domain are
correct, then type the password again."

Why can he not log into the machine without the network access? Is there any
way around this?

Thanks a million.
Click to expand...


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

Have "the user" take the computer to your company's IT department
for repairs. I do hope that your employer is of the understanding and
forgiving variety. In many companies, the user's employment would be
summarily terminated for altering, and thereby rendering useless,
company property.

This isn't entirely "the user's" fault, though. A lot of
responsibility rests squarely upon the shoulders of the network
administrator. You see, if the computer had been properly configured,
"the user's" account would not have had sufficient privileges to remove
the computer from the domain in the first place. Clearly, "the user"
lacks the requisite knowledge to be properly entitled to full
administrative privileges on the computer, or he would have known better
than to attempt what he did.


--

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
 
Back
Top