Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Superscope and 1710 router

Status
Not open for further replies.

jfc1003

IS-IT--Management
Joined
May 2, 2002
Messages
146
Location
US
I have run out of IP address on my network, using all addresses from 192.168.1.1 to 192.168.1.254. I have no budget to buy more equipment, and I am wondering if I can use a "superscope" in Windows 2000 DHCP Server and somehow configure the Cisco 1710 to treat it all as one network. So if I add 192.168.2.1 - 192.168.2.254 to the existing scope, how to make everything see each other???

Or am I missing the boat altogether and there is an easier way?
 
use this:

interface f0/0
ip address 192.168.1.1 255.255.255.0
ip address 192.168.2.1 255.255.255.0 secondary

use 192.168.2.1 (rtr) as the gateway for all the devices in the DHCP scope on Windows Server. All traffic between the (.1 and .2 subnets) will bounce off the router and flow in between the host devices

i used this when i migrated our network from a /24 mask static IP network to a /16 mask DHCP network

-gC-
 
Maybe I misunderstood the question but..

Why wouldn't you just set the DHCP scope to 192.168.0.0 255.255.0.0 and the router's inside interface to 192.168.1.1 255.255.0.0? this way, all hosts inside will see each other regardless of the last two octets, as all 16 bits would be host bits. Just remember to change any access lists to the new mask.
 
Both above would work. You can even use on your router

ip address 192.168.0.1 255.255.254.0

That will give you 510 usable addresses. Your cisco router and windows dhcp scopes will handle classless subnetting just fine.

Something to think about for future growth. This is just my personal rule I follow. I never use a 192.168.x.x network on a company network. Here's why. Most home routers use that range. If you end up having remote vpn clients connecting, you may have conflicts with overlapping subnets.

I only use 10.x.x.x or 172.16.x.x - 172.31.x.x for business networks. This leaves 192.168.x.x wide open for remote users. It's less of a hassle for me that way.

It's just something to think about if you are going to be resubnetting anyway. I always like to plan a couple years down the road.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top