DHCP SuperScope Issues

[Cookie]

Bonjourno,

I've got a few issues with our DHCP here that I've inherited.

First of all, the range runs from 192.168.0.1 to 192.168.5.254. Fine. Has some exceptions obviously where I have the printers, servers, switches et al.

192.168.0.1 - 192.168.0.254 work fine, can ping all servers. 192.168.1.* doesn't work, can ping some of the network but not all of it.

Does this sound DNS related? I'm fairly sure whoever set it up didn't have a f**king clue

 

[Cookie]

Nm, I fixed this bit (that I posted, the rest above is still an issue )

 

[David]

pre configured vlan? if you can ping other network objects from that subnet it would suggest either a dns issue or a firewall one i would have though, depends on how your setup i guess.

 

[Cookie]

No VLANs active, that I know of

It's all using the same subnet, so I can't understand why it can only see bits and pieces of the range :/

 

[sn00p]

Your subnet mask is set correctly isn't it??? (i.e it cannot be 255.255.255.0 cause that won't work with the IP ranges you have listed)

 

[Cookie]

255.255.248.0 is what's set

Whether it's right, f**k knows

 

[Mike_182]

It'll work, but it's not how I would have done it...

 

[Cookie]

It'll work, but it's not how I would have done it...

Me either

The way I've done it in the past is create separate scopes on ranges (10.16.72.*, 10.16.73.* etc) and that worked well.

I might change it all up one afternoon

 

[cava83]

Would be nice if you could put a scenario here of why you changed it and how you went about it plus reasoning, so when someone searches on here, they have your answer