No Domain

  • Thread starter Thread starter Jamie
  • Start date Start date
J

Jamie

After changing network setting from domain to workgroup,
system restarted and will not accept Admin or user
password. Unable to logon to workstation. Any suggestions
will be greatly appreciated!
 
You'll have to return the machine to the network where it belongs and ask
the system administror to rejoin it for you.
Unless you know the local administrators password, you won't be able to log
in.
 
Problem is I was "wiredd" into the network, attempting to
log on as a user with local admin privledges, tried
logging on as network admin; when the domain dialog box
did not appear and did not accept either logon(s). Any
ideas?
 
Marina,
I have the same poblem. What to you mean with "return"?
Is it to connect it to my corporate LAN and boot it again
and have the sysadm do some magic remotely?

When solved, how do I avoid it happening again?
Many thanks,
Johan
 
Yep, connect the machine to the corporate LAN and ask the system
administrator to rejoin it for you.
You should never change the networksettings on a corporate machine using at
home.
 
If the local administrator account is not known then there is not much that
can be done short of rebuilding the machine. Hopefully the someone who
administers the domain will now the local administators password.



This posting is provided "AS IS" with no warranties, and confers no rights.
 
-----Original Message-----

If the local administrator account is not known then there is not much that
can be done short of rebuilding the machine. Hopefully the someone who
administers the domain will now the local administators password.



This posting is provided "AS IS" with no warranties, and confers no rights.

.
As it turns out, .... I tried recovery console (which
requested a password [no go]), I tried "correcting
install -correcting errors in setup, found errors;
corrected and rebooted; blue screen of death; powered off.
same blue screen error; I then ran setup (reinstall to the
same local drive); [WINNTNEW}; wasble to create new admin;
logtged on and had to reinstall all drivers and apps;
copied user info -(documents and settings to new user);
imported mail msgs., etc etc. Long Day! All except NAV OK.
 
As it turns out, .... I tried recovery console (which
requested a password [no go]), I tried "correcting
install -correcting errors in setup, found errors;
corrected and rebooted; blue screen of death; powered off.
same blue screen error; I then ran setup (reinstall to the
same local drive); [WINNTNEW}; wasble to create new admin;
logtged on and had to reinstall all drivers and apps;
copied user info -(documents and settings to new user);
imported mail msgs., etc etc. Long Day! All except NAV OK.
Jamie
 
The changes were made while connected (wired) but without
being able to a logon into the network either as a
computer [whilst making the appropriate changes to the
server nor as a user, - NO DOMAIN!] to the "corporate LAN"
 
Actually ended up creating a new setup dirrectory
(winntnew) and was able to copy most all of the original
(administrators') account accross. Quite a bit of
importing and copying/reinstalling.
-----Original Message-----
-----Original Message-----

If the local administrator account is not known then there is not much that
can be done short of rebuilding the machine. Hopefully the someone who
administers the domain will now the local administators password.



This posting is provided "AS IS" with no warranties, and confers no rights.

.
As it turns out, .... I tried recovery console (which
requested a password [no go]), I tried "correcting
install -correcting errors in setup, found errors;
corrected and rebooted; blue screen of death; powered off.
same blue screen error; I then ran setup (reinstall to the
same local drive); [WINNTNEW}; wasble to create new admin;
logtged on and had to reinstall all drivers and apps;
copied user info -(documents and settings to new user);
imported mail msgs., etc etc. Long Day! All except NAV OK.
.
 
Back
Top