Re: I'm Stumped...



You won't damage the profiles if you remove and add a workstation to a
domain. You could normally try the netdom reset password but since it
doesn't sound like there is currently an account for these two machines it
wouldn't be of any value.

I would just do as you were thinking remove and add one of the workstations
and see what happens. To be honest I don;t think it is going to work, since
it can't find the machine name.

Have you searched AD to make sure the account isn't sitting in an OU you
weren't aware of?

--

Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

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

"Douglas Hiser" <DouglasHiser@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1983B8D8-E5B7-40A5-9664-3D7EFB42CCDE@xxxxxxxxxxxxxxxx
In the process of migrating from windows 2000 to 2003 and noticed a little
problem. Two workstations cant access the new server, even if I log in
with
the domain admin account. They are receiving an IP, I can PING other
computers/servers on the domain and can PING the workstations in question
from other computers/servers. I can resolve the hostname and reverse
lookup
with no problems. The one problem I did notice is in AD under the
Computers
OU, the two workstations in question are not listed and I can not create a
new object for them, I get an error that the pre-windows name is already
in
use. I tried renaming on of the computers, rebooted DNS and DHCP records
change but still no OU in AD. My next step is to rejoin the computers to
the
domain, but I wanted to see if there is another way, as I hate messing
with
profiles. Can you help me? Thanks




.



Relevant Pages

  • Re: Im Stumped...
    ... I attempt to access the server via the UNC path. ... On 6 workstations I had no problems but 2 of ... involved plus I didnt feel the problem was the account I was using since ... I tried renaming on of the computers, ...
    (microsoft.public.windows.server.active_directory)
  • Error 1385, Win2k Pro
    ... I have two Windows 2000 Pro workstations ("One" ... account I have set up), ... or Active Directory Users and Computers. ... Both workstations are 2000 Pro. ...
    (microsoft.public.win2000.security)
  • Re: Im Stumped...
    ... I attempt to access the server via the UNC path. ... involved plus I didnt feel the problem was the account I was using since it ... still do not see objects in the Computer container for the two workstations, ... I tried renaming on of the computers, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Im Stumped...
    ... I attempt to access the server via the UNC path. ... On 6 workstations I had no problems but 2 of ... involved plus I didnt feel the problem was the account I was using since ... I tried renaming on of the computers, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Plz help- tried all possible solutions- Outlook does not connect to Exchange
    ... isolated to the particular workstations. ... It seems that 4 of the 30 computers on the network refuse to ... "The connection to the Microsoft Exchange Server is unavailable. ... Then re-ran the Internet Connection Wizard. ...
    (microsoft.public.windows.server.sbs)

Loading