Q
quentinhudson
Hi,
We run a Windows 2000 network with DNS and have one WINS server for
legacy clients.
I built a new server (DC5) with the IP address 172.16.0.47 which I was
given by my boss, with the intention of making it a DC. Unfortunately,
I had to scrap it a few days later as it was a Windows 2003 box, and
after consultation I came to the conclusion that the new DC should be a
Windows 2000 box like all the others. I deleted the object from AD, and
tombstoned it in WINS, and built a new server (DC6) using the same IP
address. Unfortunately, now it is several weeks later and if you ping
DC5 or DC6 they both resolve to the same IP adddress. If you run an
nslookup on the IP address it chooses the correct server. I had a look
in DNS and did not see it in there - although I am no expert in this
area. Obviously, somewhere in AD there is a reference to the defunct
DC5, but I dont know where. I would like to get rid of this record and
resolve this problem. Any suggestions gratefully received.
Kind regards,
QH
We run a Windows 2000 network with DNS and have one WINS server for
legacy clients.
I built a new server (DC5) with the IP address 172.16.0.47 which I was
given by my boss, with the intention of making it a DC. Unfortunately,
I had to scrap it a few days later as it was a Windows 2003 box, and
after consultation I came to the conclusion that the new DC should be a
Windows 2000 box like all the others. I deleted the object from AD, and
tombstoned it in WINS, and built a new server (DC6) using the same IP
address. Unfortunately, now it is several weeks later and if you ping
DC5 or DC6 they both resolve to the same IP adddress. If you run an
nslookup on the IP address it chooses the correct server. I had a look
in DNS and did not see it in there - although I am no expert in this
area. Obviously, somewhere in AD there is a reference to the defunct
DC5, but I dont know where. I would like to get rid of this record and
resolve this problem. Any suggestions gratefully received.
Kind regards,
QH