DCPromo problem please help

  • Thread starter Thread starter justin
  • Start date Start date
J

justin

Hi
I'm currently trying to promote a domain member server to
a second domain controller.
I'm running Win2000 advanced server.

Each time after entering credentials for the domain I'm
try to join it gives an error that the domian could not be
contacted or there may be a DNS lookup problem.
I know DNS is wroking fine, i can ping forward and
reverse, I can do NSlookups. It all work fine.
The IP of the domain controller is lets say 159.140.82.20
there is a management card in the DC on IP 159.140.101.99
which is on a different subent v-lan.
When I do NBTSTAT -c on the DC
it shows the name of the domian 'JRTWED' on IP address
159.140.101.99 so I know this is why it cant'f find the
domain. I've tried a few things including disabling the
managment card but problem still persists.
Is the a registry edit I need to do...?
Please adive most gratefully appreciated
 
In
justin said:
Hi
I'm currently trying to promote a domain member server to
a second domain controller.
I'm running Win2000 advanced server.

Each time after entering credentials for the domain I'm
try to join it gives an error that the domian could not be
contacted or there may be a DNS lookup problem.
I know DNS is wroking fine, i can ping forward and
reverse, I can do NSlookups. It all work fine.
The IP of the domain controller is lets say 159.140.82.20
there is a management card in the DC on IP 159.140.101.99
which is on a different subent v-lan.
When I do NBTSTAT -c on the DC
it shows the name of the domian 'JRTWED' on IP address
159.140.101.99 so I know this is why it cant'f find the
domain. I've tried a few things including disabling the
managment card but problem still persists.
Is the a registry edit I need to do...?
Please adive most gratefully appreciated
Click to expand...

Network properties, Advanced menu, Advanced settings make sure internal
interface is at the top of the connections pane.

DNS server properties, interfaces tab check that the listener IP is the IP
you want the record created for.

Stop the auto creation of the (same as parent folder) record with the below
regedt32 entry and manually create the (same a parent folder) record with
the correct IP.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ

LdapIpAddress
 
Tried this but didn't work, anymore ideas..?
Interface is already looking at the right IP adress, did
everything detailed above but still no joy
 
In
justin said:
Tried this but didn't work, anymore ideas..?
Interface is already looking at the right IP adress, did
everything detailed above but still no joy
Click to expand...

Post your ipconfig /all
 
Back
Top