From: Castelino, Flavian (Flavian.Castelino@nexinnovations.com)
Date: Tue May 27 2003 - 16:58:25 GMT-3
Pls. check the following
- Is DHCP scope 192.168.3.0/24 bound to DHCP server NIC with Ip address
192.168.2.x
- Devices that need IP addresses in 192.168.3.x subnet should have
default router set to 192.168.3.1 (secondary IP address on router). Else
they will get addresses from any of the two scopes.
There is no need of helper-address or relay commands on router...
Flavian Castelino
-----Original Message-----
From: Jim Dixon [mailto:JDixon@communigroup.com]
Sent: Thursday, May 22, 2003 11:42 AM
To: ccielab@groupstudy.com
Subject: RE: DHCP and secondary addresses
You might also consult this book. A very good DHCP book.
-----Original Message-----
From: Jung, Jin [mailto:jin.jung@lmco.com]
Sent: Thursday, May 22, 2003 09:15
To: Hale, Wendy; ccielab@groupstudy.com
Subject: RE: DHCP and secondary addresses
I am bit confused with this config,, so let me see if I can make some
sense.
Normally,
You will need to do "helper-address" command on the remote/client side.
Not on the DHCP server network.
I see that you have helper-address configured on the same network as
DHCP server.
And I believe that "smart-relay" also needed to be on the relay agent,
not on the DHCP network.
And you said that when you change IP address to 3.0 network, it work,
this tells me that your relay-agent is not working.
I have not done this a while, so I may have miss something, but go ahead
check you relay-agent setup again.
Jin jung...
-----Original Message-----
From: Charles Church [mailto:cchurch@wamnet.com]
Sent: Thursday, May 22, 2003 7:58 AM
To: Hale, Wendy; ccielab@groupstudy.com
Subject: RE: DHCP and secondary addresses
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:48 GMT-3