Domain / Workgroup Logon 1

[DukeSSD]

Hi, Help !
My girlfriends work laptop (w2k pro) had a harddrive problem and wouldn't boot.
I booted a w2k CD and recovered it with chkdsk -R c:
Then in an attempt to save the data before if fails I tried to connect is to the home network.
Her company uses a domain logon, so it couldn't see my home network.
I changed the network identification from domain to workgroup and rebooted.
Now I can see it in my home workgroup but I presume as there is nothing shared on it I can't connect to it and when I try to logon to it, it won't let me logon, it says please correct your domain and try again.
How can I reset it to the domain if I can't even logon ?
... and she needs it for work in the morning.....

 

[bcastner]

She will have to take it to work in the morning and ask her IT staff to sort the issue. Only a Domain Administrator a member of the Domain Adminitrators group can rejoin the machine to the Domain.

 

[DukeSSD]

Thanks for the quick reply.
Will they sign on as administrator, or do something from the network side to allow the signon ?
She has admin rights but signs on as her name (a user).
Even as a standalone her signon does not work.
Even in safe mode with no networking the signon gives the same message and refuses signon....

 

[bcastner]

She will sign on as herself, but be prompted to enter a Domain Administrator username and password.

 

[DukeSSD]

Nope, when she signs on there is a message saying please check / correct your username / password / domain and try again, but since win2k is now set to be part of a workgroup rather than a domain, the little domain box no longer appears and the signon box returns.

 

[DukeSSD]

We know what the domain should be but don't get the option to input it !

 

[bcastner]

The only possible signon is the local adminstrator account created at installation.

You need to connect to the Domain, logon locally as the local Administrator, change from Workgroup to Domain, and have a valid Domain Administrator account and password to authorize the rejoin.

 

[thefourthwall]

in my experience, removing a laptop from the domain to which its joined never helps re: connectivity on my home network. bcastner, have you found that to be the case as well?

 

[bcastner]

I see absolutely no reason to remove a Domain workstation to access a Home network.

One of the "myths" of Windows networking is that for a Workgroup workstation member the computer must be set to match the Workgroup name. Windows networking happily supports multiple workgroups. It happily supports Workgroups under domains. The workgroup name is an organizing convenience and not a connectivity requirement.

 

[LloydSev]

bcastner is correct, that this issue would require a Domain Administrator to correct the problem.

In fact, I don't understand how you "removed" the machine from the domain without a domain administrator account as well.

Computer/Network Technician
CCNA

 

[thefourthwall]

LloydSev,

I have seen this scenario played out so many times at work -- someone thinks they will be able to (somehow) connect to their work laptop via their home lan if he/she just disjoins the machine from its domain. Here at least, there are not restrictions on a user removing his/her machine from the domain -- only restrictions on who can rejoin said machine.