- Joined
- Dec 15, 2007
- Messages
- 1
- Reaction score
- 0
i renamed a pc --
unjoin domain -> rename [go to ADID to remove old pc name]-> rejoin domain ->
(-> means reboot pc)
after tat .. i can still ping the old pc name -- ip addr 10.1.2.3
ping new pc (same name) -- ip addr is 10.1.2.3
remote desktop to old pc (by pc name) ends up accessing new pc.
this happen even after a few days..
i will remote access the the old name and end up accessing new pc
instead of not being able to remote the old pc name anymore.
Normally we dont care much abt this.
until then, for example, the antivirus parent server detects some prob and shows that the old name pc has a problem and dispatch an onsite engineer to find the pc but of cos cannot find it.
but he ping the machine and it is ping-able.
so he cant explain why he cannot find it.
is this a bug on the win 2003 server part?
unjoin domain -> rename [go to ADID to remove old pc name]-> rejoin domain ->
(-> means reboot pc)
after tat .. i can still ping the old pc name -- ip addr 10.1.2.3
ping new pc (same name) -- ip addr is 10.1.2.3
remote desktop to old pc (by pc name) ends up accessing new pc.
this happen even after a few days..
i will remote access the the old name and end up accessing new pc
instead of not being able to remote the old pc name anymore.
Normally we dont care much abt this.
until then, for example, the antivirus parent server detects some prob and shows that the old name pc has a problem and dispatch an onsite engineer to find the pc but of cos cannot find it.
but he ping the machine and it is ping-able.
so he cant explain why he cannot find it.
is this a bug on the win 2003 server part?