dhcp: client cannot ping dc after renewing a ip from another scope in a superscope
Posted on 2005-05-13
I have a win2000 dhcp server which is authorised in AD. I have configured a superscope made up of 2 scopes:
Scope "A" has an address pool range 184.108.40.206 - 220.127.116.11 def sub mask
Scope "B" has an address pool range 18.104.22.168 - 22.214.171.124 def sub mask
Scope options are identical.
The network has 1 DC "static 126.96.36.199" which is also the dhcp and dns server.
In a recent migration test, I added scope "B" , activated it and then created a superscope consisting of scope A and B.
I then deactivated scope A and released/renewed 1 xpsp2 client. The client obtained an ip from scope B as I hoped.
But now when I try to ping the dc by host name or ip address the request is timed out.
I reactivated scope A and deactivated B ,release/renew again so the client is back in scope A and I now can ping my dc by host name or ip successfully. Why does this happen and how can I solve it?