Endpoint mapper error when joining a computer to domain

We are getting endpoint mapper error when trying to join domain. in the
netsetup log we are getting the following:

05/07 07:32:49 NetpChangeMachineName: from 'D630CLONE' to 'A24929' using
'OURDOMAIN\itsetup' [0x2]
05/07 07:32:49 NetpDsGetDcName: trying to find DC in domain 'OURDOMAIN',
flags: 0x1020
05/07 07:32:49 NetpDsGetDcName: found DC '\\DC1' in the specified domain
05/07 07:32:49 NetpChangeMachineName: status of connecting to dc '\\DC1': 0x0
05/07 07:32:49 NetpGetLsaPrimaryDomain: status: 0x0
05/07 07:32:49 NetpManageMachineAccountWithSid: status of NetUserSetInfo on
'\\DC1' for 'D630CLONE$': 0x0
05/07 07:32:49 NetpGetLsaPrimaryDomain: status: 0x0
05/07 07:32:49 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS domain
name: OURDOMAIN.com
05/07 07:33:11 NetpGetComputerObjectDn: Unable to bind to DS on '\\DC1': 0x6d9
05/07 07:33:11 NetpSetDnsHostNameAndSpn: NetpGetComputerObjectDn failed: 0x6d9
05/07 07:33:11 ldap_unbind status: 0x0
05/07 07:33:11 NetpChangeMachineName: status of setting DnsHostName and SPN:
0x6d9

ANY hints or suggestions? I verified that the WF/ICS is turned off on this
particular DC. We do not get the endpoint mapper problem every time we join
the domain but it is frequent enough to rule out a random error.

thanks,

James

Hello James1234,

Do you rename and join the machine at the same time? And is the d630clone
a sysprepped clone?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> We are getting endpoint mapper error when trying to join domain. in
> the netsetup log we are getting the following:
>
> 05/07 07:32:49 NetpChangeMachineName: from 'D630CLONE' to 'A24929'
> using
> 'OURDOMAIN\itsetup' [0x2]
> 05/07 07:32:49 NetpDsGetDcName: trying to find DC in domain
> 'OURDOMAIN',
> flags: 0x1020
> 05/07 07:32:49 NetpDsGetDcName: found DC '\\DC1' in the specified
> domain
> 05/07 07:32:49 NetpChangeMachineName: status of connecting to dc
> '\\DC1': 0x0
> 05/07 07:32:49 NetpGetLsaPrimaryDomain: status: 0x0
> 05/07 07:32:49 NetpManageMachineAccountWithSid: status of
> NetUserSetInfo on
> '\\DC1' for 'D630CLONE$': 0x0
> 05/07 07:32:49 NetpGetLsaPrimaryDomain: status: 0x0
> 05/07 07:32:49 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS
> domain
> name: OURDOMAIN.com
> 05/07 07:33:11 NetpGetComputerObjectDn: Unable to bind to DS on
> '\\DC1': 0x6d9
> 05/07 07:33:11 NetpSetDnsHostNameAndSpn: NetpGetComputerObjectDn
> failed: 0x6d9
> 05/07 07:33:11 ldap_unbind status: 0x0
> 05/07 07:33:11 NetpChangeMachineName: status of setting DnsHostName
> and SPN:
> 0x6d9
> ANY hints or suggestions? I verified that the WF/ICS is turned off on
> this particular DC. We do not get the endpoint mapper problem every
> time we join the domain but it is frequent enough to rule out a random
> error.
>
> thanks,
>
> James
>

Yes, the person who joined the device changed the name and joined the domain
at the same time. we have tested and found that if they change the name
first and reboot then join the domain then reboot that they do not get the
endpoint mapper. we use to be able to do both at the same time.

and no it is not a syspreped clone.

James


"Meinolf Weber" wrote:

> Hello James1234,
>
> Do you rename and join the machine at the same time? And is the d630clone
> a sysprepped clone?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > We are getting endpoint mapper error when trying to join domain. in
> > the netsetup log we are getting the following:
> >
> > 05/07 07:32:49 NetpChangeMachineName: from 'D630CLONE' to 'A24929'
> > using
> > 'OURDOMAIN\itsetup' [0x2]
> > 05/07 07:32:49 NetpDsGetDcName: trying to find DC in domain
> > 'OURDOMAIN',
> > flags: 0x1020
> > 05/07 07:32:49 NetpDsGetDcName: found DC '\\DC1' in the specified
> > domain
> > 05/07 07:32:49 NetpChangeMachineName: status of connecting to dc
> > '\\DC1': 0x0
> > 05/07 07:32:49 NetpGetLsaPrimaryDomain: status: 0x0
> > 05/07 07:32:49 NetpManageMachineAccountWithSid: status of
> > NetUserSetInfo on
> > '\\DC1' for 'D630CLONE$': 0x0
> > 05/07 07:32:49 NetpGetLsaPrimaryDomain: status: 0x0
> > 05/07 07:32:49 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS
> > domain
> > name: OURDOMAIN.com
> > 05/07 07:33:11 NetpGetComputerObjectDn: Unable to bind to DS on
> > '\\DC1': 0x6d9
> > 05/07 07:33:11 NetpSetDnsHostNameAndSpn: NetpGetComputerObjectDn
> > failed: 0x6d9
> > 05/07 07:33:11 ldap_unbind status: 0x0
> > 05/07 07:33:11 NetpChangeMachineName: status of setting DnsHostName
> > and SPN:
> > 0x6d9
> > ANY hints or suggestions? I verified that the WF/ICS is turned off on
> > this particular DC. We do not get the endpoint mapper problem every
> > time we join the domain but it is frequent enough to rule out a random
> > error.
> >
> > thanks,
> >
> > James
> >
>
>
>

Hello James1234,

Unfortunal you have to rename the machine first and then join the domain.
Also if you have a clone to create additional workstations WITHOUT syprep
it or use another tool for changing the SID you can become a lot of trouble
because all machines have the same SID, which has to be equal in a domain
environment. It can work, but you can get security problems. Additional this
is NOT supported from MS.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Yes, the person who joined the device changed the name and joined the
> domain at the same time. we have tested and found that if they change
> the name first and reboot then join the domain then reboot that they
> do not get the endpoint mapper. we use to be able to do both at the
> same time.
>
> and no it is not a syspreped clone.
>
> James
>
> "Meinolf Weber" wrote:
>
>> Hello James1234,
>>
>> Do you rename and join the machine at the same time? And is the
>> d630clone a sysprepped clone?
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> We are getting endpoint mapper error when trying to join domain. in
>>> the netsetup log we are getting the following:
>>>
>>> 05/07 07:32:49 NetpChangeMachineName: from 'D630CLONE' to 'A24929'
>>> using
>>> 'OURDOMAIN\itsetup' [0x2]
>>> 05/07 07:32:49 NetpDsGetDcName: trying to find DC in domain
>>> 'OURDOMAIN',
>>> flags: 0x1020
>>> 05/07 07:32:49 NetpDsGetDcName: found DC '\\DC1' in the specified
>>> domain
>>> 05/07 07:32:49 NetpChangeMachineName: status of connecting to dc
>>> '\\DC1': 0x0
>>> 05/07 07:32:49 NetpGetLsaPrimaryDomain: status: 0x0
>>> 05/07 07:32:49 NetpManageMachineAccountWithSid: status of
>>> NetUserSetInfo on
>>> '\\DC1' for 'D630CLONE$': 0x0
>>> 05/07 07:32:49 NetpGetLsaPrimaryDomain: status: 0x0
>>> 05/07 07:32:49 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS
>>> domain
>>> name: OURDOMAIN.com
>>> 05/07 07:33:11 NetpGetComputerObjectDn: Unable to bind to DS on
>>> '\\DC1': 0x6d9
>>> 05/07 07:33:11 NetpSetDnsHostNameAndSpn: NetpGetComputerObjectDn
>>> failed: 0x6d9
>>> 05/07 07:33:11 ldap_unbind status: 0x0
>>> 05/07 07:33:11 NetpChangeMachineName: status of setting DnsHostName
>>> and SPN:
>>> 0x6d9
>>> ANY hints or suggestions? I verified that the WF/ICS is turned off
>>> on
>>> this particular DC. We do not get the endpoint mapper problem every
>>> time we join the domain but it is frequent enough to rule out a
>>> random
>>> error.
>>> thanks,
>>>
>>> James
>>>

Thanks. I know about the sysprep and we have been incorporating that into our
imaging practice.

We were just curious as to why we use to be able to join and rename at the
same time and now we can't. Not that big of a deal just a little more time
in the process.

thanks again!

"Meinolf Weber" wrote:

> Hello James1234,
>
> Unfortunal you have to rename the machine first and then join the domain.
> Also if you have a clone to create additional workstations WITHOUT syprep
> it or use another tool for changing the SID you can become a lot of trouble
> because all machines have the same SID, which has to be equal in a domain
> environment. It can work, but you can get security problems. Additional this
> is NOT supported from MS.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > Yes, the person who joined the device changed the name and joined the
> > domain at the same time. we have tested and found that if they change
> > the name first and reboot then join the domain then reboot that they
> > do not get the endpoint mapper. we use to be able to do both at the
> > same time.
> >
> > and no it is not a syspreped clone.
> >
> > James
> >
> > "Meinolf Weber" wrote:
> >
> >> Hello James1234,
> >>
> >> Do you rename and join the machine at the same time? And is the
> >> d630clone a sysprepped clone?
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> We are getting endpoint mapper error when trying to join domain. in
> >>> the netsetup log we are getting the following:
> >>>
> >>> 05/07 07:32:49 NetpChangeMachineName: from 'D630CLONE' to 'A24929'
> >>> using
> >>> 'OURDOMAIN\itsetup' [0x2]
> >>> 05/07 07:32:49 NetpDsGetDcName: trying to find DC in domain
> >>> 'OURDOMAIN',
> >>> flags: 0x1020
> >>> 05/07 07:32:49 NetpDsGetDcName: found DC '\\DC1' in the specified
> >>> domain
> >>> 05/07 07:32:49 NetpChangeMachineName: status of connecting to dc
> >>> '\\DC1': 0x0
> >>> 05/07 07:32:49 NetpGetLsaPrimaryDomain: status: 0x0
> >>> 05/07 07:32:49 NetpManageMachineAccountWithSid: status of
> >>> NetUserSetInfo on
> >>> '\\DC1' for 'D630CLONE$': 0x0
> >>> 05/07 07:32:49 NetpGetLsaPrimaryDomain: status: 0x0
> >>> 05/07 07:32:49 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS
> >>> domain
> >>> name: OURDOMAIN.com
> >>> 05/07 07:33:11 NetpGetComputerObjectDn: Unable to bind to DS on
> >>> '\\DC1': 0x6d9
> >>> 05/07 07:33:11 NetpSetDnsHostNameAndSpn: NetpGetComputerObjectDn
> >>> failed: 0x6d9
> >>> 05/07 07:33:11 ldap_unbind status: 0x0
> >>> 05/07 07:33:11 NetpChangeMachineName: status of setting DnsHostName
> >>> and SPN:
> >>> 0x6d9
> >>> ANY hints or suggestions? I verified that the WF/ICS is turned off
> >>> on
> >>> this particular DC. We do not get the endpoint mapper problem every
> >>> time we join the domain but it is frequent enough to rule out a
> >>> random
> >>> error.
> >>> thanks,
> >>>
> >>> James
> >>>
>
>
>