|
View Full Version : netdom move no - explorer yes - why?
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
Marty List 10-22-2003, 07:39 PM "hfs2" <hfs2@yahoo.com> wrote in message
news:17f20df0.0310220544.41fcf4bb@posting.google.com...
> 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
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.
Marty List 10-22-2003, 07:39 PM "hfs2" <hfs2@yahoo.com> wrote in message
news:17f20df0.0310220544.41fcf4bb@posting.google.com...
> 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
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.
"Marty List" <Bill.Gates@sun.com> wrote in message news:<bn6it5$tdf2f$1@ID-172409.news.uni-berlin.de>...
> "hfs2" <hfs2@yahoo.com> wrote in message
> news:17f20df0.0310220544.41fcf4bb@posting.google.com...
> > 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
>
>
> 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.
"Marty List" <Bill.Gates@sun.com> wrote in message news:<bn6it5$tdf2f$1@ID-172409.news.uni-berlin.de>...
> "hfs2" <hfs2@yahoo.com> wrote in message
> news:17f20df0.0310220544.41fcf4bb@posting.google.com...
> > 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
>
>
> 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.
|
|
|