Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


dhcp: client cannot ping dc after renewing a ip from another scope in a superscope

Posted on 2005-05-13
Medium Priority
Last Modified: 2008-01-09
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 - def sub mask
Scope "B" has an address pool range - def sub mask
Scope options are identical.
The network has 1 DC "static"  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?  

Question by:gpersand

Accepted Solution

joedoe58 earned 500 total points
ID: 13999132
Do you have a router/switch between the subnets that filter out echo packets?

Assisted Solution

S3quence earned 500 total points
ID: 13999692
This will be happening as they are on different subnets. I assume the server is on the - can you not create the 2 scopes to be... - -

Both having subnet masks of

I think that this should resolve the issue



Author Comment

ID: 14000658
Thanks micheal but what if scope "A" was in the range -
and scope  "B" -

Now how would i resolve this?

You also mentioned above that ""This will be happening as they are on different subnets"" Why does it happen?

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.


Expert Comment

ID: 14001514
As Michael says the problem comes from no routing taking place to the other subnet. How are your machines connected?

Author Comment

ID: 14002377
My home configuration consists of only 1 win 2000 server DC and 1 client XPsp2(firewall disabled) machine.
I use this setup for testing.The client machine is directly connected to the DC via a CAT5 network cable.

The larger range scope senario relates a problem at work where a manager needs to have two scopes active at once any way possible. Both senarios are having the same problem though.
At work a switch, patch panel and floor boxes are used to support the larger range senario.

Although I need reasons why I connot ping the dc at work or home and possible solutions?


Expert Comment

ID: 14004206
Guys - superscopes imply managing your subnets. If you have machines in subnet 200.200.200.x and subnet 200.200.201.x then you need a mask to encompass both ranges. This would be to give 512 hosts which is, I think, what you are looking for.

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

572 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question