Created a new scope in existing superscope but PCs in the new scope cannot ping anything.

I am running a domain with a windows 2003 server as my PDC. It is also the DHCP server. I have a superscope built with 2 scopes of IPs- 192.168.1.0 and 192.168.2.0.  I am trying to add a third, 192.168.20.0, but whenever I add it, the computers that are pulling the address in that scope are cut off from the rest of the network. They are unable to ping anything. I double checked the router setting, dns setting..etc same as the other two scopes. There is no reason why it shouldn't work. The only thing I'm doing different is that on this scope I'm reserving IPs by using MAC addresses from computers because I want the computers in this scope to eventually be routed differently. Some assistance would be greatly appreciated. Thank you.
lilceezAsked:
Who is Participating?
 
DenisCooperCommented:
yeah...

i thought it wold have been something wrong with the mask....

cheers,
denis
0
 
DenisCooperCommented:
what subnet masks are you using on all the scopes?

can the pc's picking up an IP from the new scope ping the DHCP server by IP?

What routing is in place - how is it configured?
0
 
DenisCooperCommented:
oh, and what is their default g/w
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
lilceezAuthor Commented:
The subnet for all three are the same, gateway is the same, DNS is the same... that's what doesn't make sense. Right now the routing is set the same on all three. Here is the weird thing- if computer is not on the .20 scope it can ping the dhcp server. As soon as I reserve that MAC in the .20 and do an ipconfig /renew, it picks up an IP in the .20 range but now it can't ping anything, even the DHCP server. I'm stumped?????
0
 
DenisCooperCommented:
okay...

can you provide me your exact ip address range for each scope, and the subnet mask you are using.

thanks.
denis
0
 
lilceezAuthor Commented:
I figured out my own problem but thanks for the replies Dennis. It looks like I overlooked changing the subnet on the firewall. It was at 192.168.1.0/22, I just recalculated it and changed it to 192.168.1.0/19 and then was able to get to the .20 scope I created.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.