[windows2000] Re: Correcting a PC which was improperly configured with our network
- From: "Sullivan, Glenn" <GSullivan@xxxxxxxxxxxxxx>
- To: "'windows2000@xxxxxxxxxxxxx'" <windows2000@xxxxxxxxxxxxx>
- Date: Fri, 10 Jan 2003 06:52:11 -0500
Do you have a WINS server?
If so, delete references to that workgroup name, but only those that have
the same IP as the workstation in question was assigned.
If you don't have Wins, change the name of the workgroup and wait.
Supposedly all browse lists should be updated within 36 minutes, but
experience has proven that sometimes it takes as long as overnight. But
leave the machine on and connected to the network while waiting.
Also, verify that there is no object in your AD that has the same name.
Maybe he did attempt to join the domain, but it failed part way through, and
there is an orphaned account laying around. Not likely, but worth a look.
HTH,
Glenn Sullivan, MCSE+I MCDBA
David Clark Company Inc.
-----Original Message-----
From: Rod Falanga [mailto:rjfalanga@xxxxxxxxxxxxxx]
Sent: Thursday, January 09, 2003 8:15 PM
To: rjfalanga@xxxxxxxxxxxxxx
Subject: [windows2000] Correcting a PC which was improperly configured
with our network
We are expanding into another building. We=92ve pull RJ-45 cable and =
are all
ready to go. So far, I=92ve set up something like 4 PCs, two of which =
were
brand new Dells with Windows XP Pro preinstalled. I know, from =
experience,
that it takes a little bit of drilling to find where to make the PC join =
a
domain, but it is possible and works fine.
Well, I asked one of my developers to go over and set up another PC =
today.
He went over, took it out of the box, and got it to the point where he
needed to change the network affiliation. However, instead of changing =
it
to join a domain, he left it as a workgroup and give it the name of our
domain. Naturally, he couldn't find anything listed in Active Directory
(printers, etc). He was confused, because he thought that he had =
instructed
it to join a domain. I went to the machine and discovered his mistake. =
I
tried to switch it to a domain, but now it says that it cannot join our
domain since it already has a network object by the same name (the
workgroup). I tried to fix this by changing the name of the workgroup =
to
something else, but that didn't help. I suspect that what happened is =
the
PC allowed itself to be changed to a different workgroup, but still =
believes
that there is another workgroup out there with a name identical to our
domain.
So, my question is, how do we fix the problem he's created?
Rod
=A0
==================================
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
==================================
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
Other related posts:
