G
Guest
Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)
Currently, I have one PDC and two BDCs on my network. Last year, I replaced
the PDC and BDC with the new servers. I kept the same ip addresses of both
PDC and BDC. I changed the ip address of the old BDC and leave it on the
network. I took the old PDC offline and out of the network. Everytime, I
reboot either one of the BDCs, I have Domain name 1c in conflict in the
netbios name table of the new BDC. We use WINS as name resolution method.
When I look at WINS database, the new BDC will not register Domainname 1c.
The new PDC is also a primary WINS. The new BDC is the secondary WINS. Both
servers WINS setting is pointing to its own ip address.
The problem will resolve if I remove name mapping from WINS server before I
reboot the server. But if I don't do that before I reboot the server, I will
get domain name 1c conflict. I'm trying to resolve this problem because the
BDC won't authenticate users when PDC went down.
Does anyone know how to fix this problem ?
Currently, I have one PDC and two BDCs on my network. Last year, I replaced
the PDC and BDC with the new servers. I kept the same ip addresses of both
PDC and BDC. I changed the ip address of the old BDC and leave it on the
network. I took the old PDC offline and out of the network. Everytime, I
reboot either one of the BDCs, I have Domain name 1c in conflict in the
netbios name table of the new BDC. We use WINS as name resolution method.
When I look at WINS database, the new BDC will not register Domainname 1c.
The new PDC is also a primary WINS. The new BDC is the secondary WINS. Both
servers WINS setting is pointing to its own ip address.
The problem will resolve if I remove name mapping from WINS server before I
reboot the server. But if I don't do that before I reboot the server, I will
get domain name 1c conflict. I'm trying to resolve this problem because the
BDC won't authenticate users when PDC went down.
Does anyone know how to fix this problem ?
