Announcement

Collapse
No announcement yet.

DHCP - Running out of IP

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • DHCP - Running out of IP

    Hi,
    Scenario;

    We've 3 class C segment being used for production;
    Subnet A: 192.168.1.0/24
    Subnet B: 192.168.2.0/24 (isolated, no internet access)
    Subnet C: 192.168.3.0/24 (Office LAN, Office Automation Servers)

    DHCP on Subnet C is running out of IP addresses.

    What we have in Subnet C:
    1- DC, DNS, DHCP
    2- Exchange Server
    3- File Server (DFS)
    4- Printers
    5- Client Desktop/Laptop
    6- Staging Servers Environment

    Anyone can help me to plan the migration increase the DHCP range address?

    I've thinking a few plan;
    1- Supernetting (Resubnet)
    2- Superscope

    Plan:
    as for Supernetting;
    1- Change firewall MAP/NAT
    2- Delete current DHCP scope & create with new subnet
    3- Change IP/Subnet/Gw on static address machine
    note : instead of 192.168.3.0/24(254 ip) change to 192.168.3.0/23 (512 ip)
    new range will be : 192.168.2.1 - 192.168.3.254 subnet 255.255.254.0

    question;
    1- how this will impact on the Domain controller?
    2- how about exchange server/service?
    3- what are other consideration?


    as for Superscope;
    1- DHCP server will require two connected NIC with different IP & subnet.
    1- Add new superscope and add additional subnet to the superscope.
    2- configure routing table to serve new subnet to access internet
    note : instead of 192.168.3.0/24(254 ip) add additional to 192.168.4.0/23 (512 ip)
    new range will be : 192.168.3.0 subnet 255.255.255.0 and 192.168.2.0 subnet 255.255.255.0 and

    question;
    1- is this really work?
    2- what are other consideration?

    This is only a theory plan. I am not sure whether this will be the correct plan.
    Please advise.

  • #2
    Re: DHCP - Running out of IP

    Since all your subnets are private address spaces, why not simply leave Subnet C alone, and stand up a Subnet D (192.168.4.0/24) to put your clients on? Make certain the addresses on your servers are static IPs, and let the client devices us a new subnet all their own.

    Routing between C & D should be straight forward, assuming you're already familiar with VLANs, switchports accessing the VLANs, and how the current routing is done.
    *RicklesP*
    MSCA (2003/XP), Security+, CCNA

    ** Remember: credit where credit is due, and reputation points as appropriate **

    Comment

    Working...
    X