netdom move no - explorer yes - why?

  • Thread starter Thread starter hfs2
  • Start date Start date
H

hfs2

At the DC of domain A as administrator.
In explorer I can see domain B, enter and log into PC_B.


I want to move PC_B from domain B to A. Using netdom move
gets me error 53 'The network path cannot be found'

net view fails with error 5 - access denied.

So why can explorer see and log into PC_B and not netdom?
I don't think it can find PC_B.

I've tried naming the target PC argument as:
B\PC_B, \\B\PC_B, \\PC_B, PC_B...


OF the many things I don't understand, just which one is killing
me here?

Thanks
 
hfs2 said:
At the DC of domain A as administrator.
In explorer I can see domain B, enter and log into PC_B.


I want to move PC_B from domain B to A. Using netdom move
gets me error 53 'The network path cannot be found'

net view fails with error 5 - access denied.

So why can explorer see and log into PC_B and not netdom?
I don't think it can find PC_B.

I've tried naming the target PC argument as:
B\PC_B, \\B\PC_B, \\PC_B, PC_B...


OF the many things I don't understand, just which one is killing
me here?

Thanks
Click to expand...


You said that the domain controller can "see" Domain B and PC_B, but really
what needs to happen is the other way around, PC_B needs to be able to
resolve the name of Domain A and connect to it's domain controller.

You need to run NETDOM from PC_B, it sounds like you are running it from the
domain controller of domain A.
 
Thanks. I figured someone had to see someone. I tried going to
the OLD_DOMAIN controller, an NT4 box. It runs netdom too but
a NT 1.8 version that has a different syntax - it doesn't have
'move'. I'm posting a translation request elsewhere but question
still haunts me. Why can the browser see and do things netdom.exe
cannot? Thanks again.
 
Back
Top