From: Charles Church (cchurch@wamnet.com)
Date: Thu May 22 2003 - 08:57:36 GMT-3
I think this problem could also be fixed by using a 'super scope' on the
server. Haven't done it in a while, but I think it handles secondary
addresses nicely. HTH.
Chuck Church
CCIE #8776, MCNE, MCSE
Wam!Net Government Services
13665 Dulles Technology Dr. Ste 250
Herndon, VA 20171
Office: 703-480-2569
Cell: 585-233-2706
cchurch@wamnet.com
PGP key: http://pgp.mit.edu:11371/pks/lookup?search=chuck+church&op=index
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Hale, Wendy
Sent: Thursday, May 22, 2003 1:41 AM
To: 'ccielab@groupstudy.com'
Subject: DHCP and secondary addresses
I have an ethernet address with a primary address in the 192.168.2.0/24
subnet and a secondary address in the 192.168.3.0/24 subnet.
The Windows 2000 DHCP server has a scope for the 192.168.3.0 subnet, but the
DHCP server itself has an address in the 192.168.2.0 subnet.
I can ping the DHCP server from the secondary address on the router.
I tried using the smart-relay command and debug showed that the router is
indeed forwarding the DHCP request to the DHCP server with a giaddr of
192.168.3.1. However, the DHCP server is returning an answer which the
router says has an invalid XID not_for_us.
When I change the ip address of the DHCP server to 192.168.3.2, it works
fine.
What do I need to do to get the secondary address to work with DHCP?
interface e0
ip address 192.168.2.1 255.255.255.0
ip address 192.168.3.1 255.255.255.0 sec
ip helper-address 192.168.2.102
!
ip dhcp smart-relay
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:46 GMT-3