Scope problems

  • Thread starter Thread starter Steve
  • Start date Start date
S

Steve

My current DHCP scope 192.168.0.1-192.168.0.254 is
running low on IP's. I have created a superscope and
created 2 new DHCP scope's of 192.168.1.1-192.168.1.254 &
192.168.2.1-192.168.2.254. After I authorize the new
scopes and deactivate the old one, the PC's start
receiving the new IP's but they cannot see anything on
the old scope and cannot get to the internet. I set both
new scopes with the same info as the old scope (dns, time
server & gateway address). What am I missing here.

I got a response a couple of days ago to add a route.
When I did this it is still pointing me to the wrong
gateway and not seeing the other scope. Does the other
scope need to be active to see it and do I need to set add
something on my router? Do I need to have more then one
gateway address? I only have one nic on the firewall.
 
You do need to make sure your router is configured with addresses on each
subnet and that it allows one port on a router to listen to multiple
(logical) subnets.

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Steve said:
My current DHCP scope 192.168.0.1-192.168.0.254 is
running low on IP's. I have created a superscope and
created 2 new DHCP scope's of 192.168.1.1-192.168.1.254 &
192.168.2.1-192.168.2.254. After I authorize the new
scopes and deactivate the old one, the PC's start
receiving the new IP's but they cannot see anything on
the old scope and cannot get to the internet. I set both
new scopes with the same info as the old scope (dns, time
server & gateway address). What am I missing here.

I got a response a couple of days ago to add a route.
When I did this it is still pointing me to the wrong
gateway and not seeing the other scope. Does the other
scope need to be active to see it and do I need to set add
something on my router? Do I need to have more then one
gateway address? I only have one nic on the firewall.
Click to expand...

Step back a moment and consider subnetting your network physically with
another router. Alternatively, in the case you have some transient clients
who only seldom use the network/ scope ip consider shortening your dhcp
lease time.

Did you add a new NIC or add an ip_address to dhcp server's existing NIC? In
RRAS, enable IP forwarding for the interface. That should create the route
between logical subnets for you. Double-check that routing table.

DHCP scopes should specify the DNS server's ip_address in its options.
Clients should not use the ISP's DNS to resolve. Only use local DNS server.
Configure the forwarders on local DNS instead.
 
Back
Top