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 news:1b20801c44f9f$0fa9d800$(E-Mail Removed),
justin <(E-Mail Removed)> posted a question
Then Kevin replied below:
> 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

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


--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
--
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
http://www.lonestaramerica.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================

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

>-----Original Message-----
>In news:1b20801c44f9f$0fa9d800$(E-Mail Removed),
>justin <(E-Mail Removed)> posted a
question
>Then Kevin replied below:
>> 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
>
>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\Netlo
gon\Parameters
>
>Registry value: DnsAvoidRegisterRecords
>Data type: REG_MULTI_SZ
>
>LdapIpAddress
>
>
>--
>Best regards,
>Kevin D4 Dad Goodknecht Sr. [MVP]
>Hope This Helps
>============================
>--
>When responding to posts, please "Reply to Group" via
your
>newsreader so that others may learn and benefit from your
issue.
>To respond directly to me remove the nospam. from my
email.
>==========================================
> http://www.lonestaramerica.com/
>==========================================
>Use Outlook Express?... Get OE_Quotefix:
>It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
>==========================================
>Keep a back up of your OE settings and folders with
>OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
>==========================================
>
>
>.
>

In news:1b36801c44fab$b8851d70$(E-Mail Removed),
justin <(E-Mail Removed)> posted a question
Then Kevin replied below:
> 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
>

Post your ipconfig /all



--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
--
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
http://www.lonestaramerica.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================

TCP/IP properties, uncheck "enable LMHost Lookup". Reboot.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
"justin" <(E-Mail Removed)> wrote in message
news:1b20801c44f9f$0fa9d800$(E-Mail Removed)...
>
> 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
>
>

Many thanks,. got it working at last,.. keep up the good
work, you saved my bacon