Domain IP Changed after running dcpromo on NT backup domain controller

[Richard Wu]

I recently upgrade my NT PDC(ip:192.168.1.253) to Window
2000 and I don't have DNS in NT environment, only WINS.
The upgrade was perfect and no problem. It installed AD
and DNS integrated. I used the same FQDN name for both AD
and DNS. All my other clients including NT backup
controller can login without any problems. At this point,
if I ping my domain, abc.com, it returns 192.168.1.253.

Then I started to upgrade the NT backup controller(ip:
192.168.1.254). Again the dcpromo will start and installed
smoothly. There is no DNS installed on this machine.
Everything work fine except when I ping my domain,
abc.com, it returns 192.168.1.254. Even I ping it from the
first controller, it returns 192.168.1.254.

I tried to convert the backup computer down to member
server, then the ip for abc.com is back to 192.168.1.253.
Once I promoto it back to domain controller, it changed
back to 192.168.1.254.

Is something I have to do on the first win2000 domain
controller before I upgrade other NT backup controller??

Please Help, Thanks
Richard Wu

 

[Kevin D. Goodknecht [MVP]]

In

I recently upgrade my NT PDC(ip:192.168.1.253) to Window
2000 and I don't have DNS in NT environment, only WINS.
The upgrade was perfect and no problem. It installed AD
and DNS integrated. I used the same FQDN name for both AD
and DNS. All my other clients including NT backup
controller can login without any problems. At this point,
if I ping my domain, abc.com, it returns 192.168.1.253.

Then I started to upgrade the NT backup controller(ip:
192.168.1.254). Again the dcpromo will start and installed
smoothly. There is no DNS installed on this machine.
Everything work fine except when I ping my domain,
abc.com, it returns 192.168.1.254. Even I ping it from the
first controller, it returns 192.168.1.254.

I tried to convert the backup computer down to member
server, then the ip for abc.com is back to 192.168.1.253.
Once I promoto it back to domain controller, it changed
back to 192.168.1.254.

Is something I have to do on the first win2000 domain
controller before I upgrade other NT backup controller??

Please Help, Thanks
Richard Wu

This is by design, your domain name will resolve to all domain controllers.
If you run nslookup and resolve he domain name it will return all IP
addresses on all DCs.
If you ping your Domain name only one DC can return the ping it could be
either. It depends on which record is cached, you can still ping both by
there FQDN.
If you want to see something interresting, type this in your browser
\\abc.com\sysvol then click on the properties of the share you opened and
select the Dfs tab, it will show you the Active DC the share is on. That is
provided you still have two DCs, the Dfs tab is only available if you have
more than one DC.

 

[Ace Fekay [MVP]]

In

In

This is by design, your domain name will resolve to all domain
controllers. If you run nslookup and resolve he domain name it will
return all IP addresses on all DCs.
If you ping your Domain name only one DC can return the ping it could
be either. It depends on which record is cached, you can still ping
both by there FQDN.
If you want to see something interresting, type this in your browser
\\abc.com\sysvol then click on the properties of the share you opened
and select the Dfs tab, it will show you the Active DC the share is
on. That is provided you still have two DCs, the Dfs tab is only
available if you have more than one DC.

Kevin, actually I have only one DC and I get the DFS tab when I connected
by:
\\domain.com.

But the alternate under the DFS tab shows up as:
servername.domain.com

I guess by any other name, a sysvol is still a sysvol?




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory