dustaine
asked on
DHCP/DNS issue
I have an issue where my company is expanding into a new building. The old building has an internal ip range from 192.168.8.1 - 192.168.9.254. Everything seems to work fine. They want to bring the majority of the servers, including DNS, to the new building where the internal ip range is from 192.168.23.1 - 192.168.24.254. The subnet for both locations is 255.255.248.0. The gateway for the new location is 192.168.23.1. We set up the server to do both DNS and DHCP. The DHCP ended up being a super scope that ranges from 192.168.16.1 to 23.254 on one scope and 24.1 - I think 30.254 on the other scope. We have the 23.XXX set aside for our servers, printers, cameras etc and have set the 24.XXX set for the users. I have gone into DNS and the NICs and changed the pointers and IP addresses to match the new location. My clients seem to be getting the 24.XXX address from DHCP. My issue is that they cannot access or ping anything on the 23.XXX portion of the network. The servers can ping one another but not any clients and the clients cannot see the servers or anything on the 23.XXX portion of the network. What am I missing? Is it because of the super scope in DHCP?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Neil Russell
Do you understand IP address's and routers and netmasks?
as for me - i do.
if dustaine want use that network - hi can use it.
actualy all 192.168.x.x range is private.
Yes it's not best choice but it can be :)
of cause without router or withuot routes on computers he can't acces computers from 192.168.8.x range, but he doesn't wrote about this problem
if dustaine want use that network - hi can use it.
actualy all 192.168.x.x range is private.
Yes it's not best choice but it can be :)
of cause without router or withuot routes on computers he can't acces computers from 192.168.8.x range, but he doesn't wrote about this problem
Classful addressing... it's been a long long time since that was the root of any problem. 192.168.0.0/16 is the private range in Class C. Convention and tradition may have us use masks /24 or more, but no rule in the network stack enforces that. There's nothing wrong with using the range above provided the mask does not prohibit acces between networks or a router is present to help out.
And yeah, 255.255.240.0, I miscounted that one earlier :)
Chris
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You all have been really great in your assistance. Honestly, I am just a Information Security person who had been put in charge of putting this together. I remember some things from subnetting and figured the mask was the issue, especially when I saw the range as 16 - 23. I figured the .23 wouldn't be able to talk to the .24 without some routing. The .23 and .24 are actually on the same network in the same building. The .8 network is in the building next door. I am not really interested in the two building communicating except perhaps via vpn because of ITAR and other concerns. I was just momentarily stumped as to why on the same network .23 and .24 would not talk to one another then I remembered binary. lol.