Change Member of from Workgroup to Domain

  • Thread starter Thread starter Stuart
  • Start date Start date
S

Stuart

Hi All,
I don't understand this one, so it must be simple !!

I changed a W2K machine from Domain to Workgroup to test a
cross cable connection to another PC. All good.
Reconnected back to the network, when changing from
Workgroup back to Domain, I get the message "The specified
domain either does not exist or could not be connected."

What am I forgetting ? I thought changing the
simple "Member of" option from Domain>Wrkg to Wrkg>Domain
would be simple ??

Thanks for any help.
 
First... you don't need to have two machines in a workgroup in order to test
whether a cable is a good cross cable... just connect 'em, set their TCP/IP
(or other NW protocol) properties, and test....

When changing back to domain, have you set the TCP/IP (or other NW protocol)
back to what they were before? Can you ping, or otherwise, test to ensure
that you have a connection to the domain controller? When changing back to
domain, you will have to reauthenticate to the DC, you will receive a new
SID for the machine.

L8r,
MS
 
Hi,

Yeah, problem was, the PC needing testing was in a
workgroup and we couldn't get it to join the domain. We
had to ship the PC today, so the best we could do to
confirm the NIC was working, was to use a c-cable.

We're using TCP so nothing changed in any other setting
other than the "Member of:" and a reboot.

Tried pinging DC and it failed.

thanks
 
Hi,

Yeah, this system has been working on the network for at
least a year. All I did was change it from logging on to
the domain, to workgroup, and then back to domain, but
when I change it back to the former domain name, I get an
error.

Nothing else was changed.
 
Try to rename the workgroup to something completely different, reboot and
then join it to your domain.

Marina
 
Hi Marina,

We only use domain login. The creation of a workgroup was
just to test two stand alone PC's.

I think the problem lies in going from workgroup login to
domain login. I suspect it has something to do with
process/security. Since doing this in NT,98,ME is simple,
I guessed that 2000 would be too, based on the join domain
dialog box.

I can't beleive the only fix for this is reformatting the
drive and reloading 2000 !

thanks
 
You may want to try setting your primary DNS server on the client
machine to point to the W2K Domain Controller. Then make sure you can
ping the DC by name.
 
Back
Top