Re: running out of IP Address! help!

Tech-Archive recommends: Speed Up your PC by fixing your registry



The beauty of DHCP is that you can reconfigure the scope and reboot everyone
and the network will be all set - theoreticly!

Since you have .0 for a network and you need connectivity to .1 you can't
just expand your subnet mask. If you did not have connectivity to .1 then I
would have suggested adjusting the subnet to 255.255.248.0 which would have
given you access to .0 - .7 and adjust your scope to issue addresses in the
new IP range. But you can still do this and just change your IPs from .0 to
..8-.16

All the clients should just fall into place when you change the scope to
give out the new IP range however your real problem is getting all the other
static content into place. For instance if you have the direct connection
to .1 at the other company you have to configure everything to point to your
internal network numbers in the new range. If you have ISA server or Proxy
server it is a pain to get the LAT tables correct. RRAS is a pain to change
as well. You have also got to reconfigure your port forwarding on your
firewalls and routers if you have those.

You also could just segment your network a little. Since it looks like you
have about 200+ computers you could keep one DHCP server on one segment and
create a segment ending in .2 with a DHCP server and router in between. Put
half of the computers on the .2 segment. Preferably the ones that can hold
off on access to the other office while you work out the kinks.


"chris" <chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:63E81A54-9B41-43E6-9DC2-337CA2159690@xxxxxxxxxxxxxxxx
My company has a class C network 192.168.0.x and using AD with DHCP.
Only
5% available and need to think of something quick. I read some articles
about segmenting 2 with a router 192.168.0.x /192.168.1.x 255.255.255.0
and
this should work. I'm sorta new to this and the only problem with this is
that we have a remote facility that already has a segment of 192.168.1.x
through a dedicated T1 using 2 cisco routers. The remote site is using the
cisco dhcp from the router to assign the 192.168.1.x IP's. Is it possible
to
have another subnet while keeping my scope the same? maybe my HQ would
have 2
physical segmets with 192.168.0.x / 192.168.2.x ? since my remote site
already have 192.168.1.x.


.



Relevant Pages

  • Re: Preventing DHCP from allocating IPs
    ... Each segment is physically separate with a Linux ... unknown MAC addresses firstly don't get a DHCP ... >> wants access to your network, they will have to come to you to obtain ...
    (Security-Basics)
  • Re: DHCP Range
    ... If I change the NIC card details to 255.255.255.0, ... suggested (think i'll have to delete the existing DHCP scope to do this), ... details because the other network needs to be left alone. ... One thing i messd with is creating a superscope that includes a scope ...
    (microsoft.public.windows.server.setup)
  • Re: Change DHCP IP Adress
    ... What I am saying is that the Router needs to be on the same network as the ... scope. ... It really will depend on your network setup. ... >>> We recently switched our ISP and am trying to configure our DHCP ...
    (microsoft.public.win2000.networking)
  • Re: Changing corprate network addressing
    ... I have the original scope setup in my DHCP server. ... B network and bring them into Site A network and change the subnet mask to 255.255.255.0. ... Create a new Scope on the DHCP Server and configure the DHCP Helper Address on the LAN Router so it will forward the DHCP queries. ... Usually as simple as moving a patch cable in the MDF/IDF to another switch port on the other subnet. ...
    (microsoft.public.windows.server.networking)
  • Re: Renumber network & Keep IPs for DHCP clients
    ... >> IPs my DHCP gives is not enough. ... I want delete DHCP ... >That is part of creating the scope properly. ... segment bigger. ...
    (microsoft.public.win2000.networking)