DHCP Solutions using 2600 config 1

[arrrrrrrrrrrgh]

Background: There are 2 offices, and a serial link connecting the 2 individual 2600's together. network1 is 192.168.0.0/24 and network2 is 192.168.2.0/24. There is NO DHCP or DNS server, or DOMAIN CONTROLLER on network2.

Problem: client laptops that roam between offices are annoyed that they must change their static IP for each office (don't reccomend hw profiles.. no.. and I'd rather avoid placing a DHCP server on network2).

Question: Can/should I... and how DO I...

1. Somehow configure the routers to allow the DHCP clients on network2 to contact a dhcp server within network1 to hand out a network2 DHCP address (probably a question better asked in another subforum)

2. configure Transparent bridging and leave all laptop clients set to a static network1 address, and use netbios/netbui in addition to TCPIP on those laptops. Network2 would then ONLY have static network1 addresses on all laptops.. but what about the office IP printers and other static network2 stations? Can I set their IP to a network1 address?

I guess I am wondering if there is a way to create a TRANSPARENT IP NETWORK that spans 2 physical locations... and have them actually use IP as the protocol... the main trait being that ALL NODES ARE ON THE 192.168.0.0/24 network... a SINGLE broadcast domain spanning the 2 2600's.

tia..

 

[KiscoKid]

Out of those 2 options. I'd probably go with option 1 as it's less hassle because you won't have to reconfigure everything on network2.

1. DHCP Rleay config:

int fa0/0
ip helper-address x.x.x.x

where fa0/0 is the LAN interface for the router on network2 and x.x.x.x is a DHCP server on network1.

2. Bridge 2 WANs:

On both routers -

int f0/0
bridge-group 1
int s0/0
bridge-group 1
!
bridge 1 protocol ieee

where f0/0 and s0/0 are the LAN and WAN interface respectively.

 

[1fb]

If possible I would stay away from bridging. It is not considered a best practice by today’s standards.

Joe

http://CertificationChat.com

Cisco Discussion Forums

 

[arrrrrrrrrrrgh]

Kisco, Thank you.. I have multiple DHCP servers on network1 already (a step in a planned offloading of services from the original DHCP server), but they are providing addresses for network1 only. I'm guessing that if I set up a vlan using my 2924 that I can keep the network1 DHCP clients from getting a network2 DHCP address... am I missing a better way to avoid that? I don't see that uSoft DHCP server has anything built-in for understanding this config without being vlan'd.. so thats where I'll start.

1fb, Yes I don't like the idea of not being able to monitor things with my handy IP stuff.. plus its a little harder to explain to the generic support guy (not that I'm any bright star myself) Thanks!

I'll post the results... gimme a few days.. busy round here.. I've become a master of 'employee turnover processing'..

 

[KiscoKid]

At a very minimum, you will need to configure the router on network2 with an IP address from the range of available addresses to be used by the clients there.

When the DHCP server sees a forwarded DHCP Discovery packet to the server, the server looks at the IP address of the DHCP forwarder (in this the router on network2) to determine what IP address to allocate from its pool. Therefore your DHCP server must be configured with an appropriate pool for network2 for this to work.

So in summary, just configure the router on network2 with an appropriate address from the 192.168.2.x/24 subnet. Then create a new DHCP scope on the server (192.168.2.x/24 and exclude the IP address of the router).

This should be all you need to do at a minimum. However if you want to allocate everyone on network2 into a VLAN, this is good practice too but not strictly necessary as your networks are divided by routers anyway (which will effectively achieve the same kind of LAN segmentation as VLAN's anyway)