Archived from groups: microsoft.public.win2000.advanced_server (More info?)
Hi,
I'm setting up a DHCP server with a Scope of 5000 IPs. Briefly, heres
my setup:
(Mobiles) -> Cisco Router -> DHCP Server
The DHCP server has a physical NIC IP of 20.20.20.113, no aliases, the
Cisco router has lots of IP routes, one of them being a vlan for the
20.20.20/24 network. The local loopback IP of the Cisco is
172.19.241.36. The DHCP scope is set for 172.19.192.1 - 172.19.223.254,
a single scope.
When one of the Mobiles sends a request, the Cisco is putting in a Relay
agent IP of 172.19.241.36. But the DHCP server is ignoring it.
Here is an Ethereal packet taken from snooping the 20.20.20.x vlan
network (the same vlan that the DHCP server is on).
I see the Discover, but no replies at all.
I'm looking for answers to two things:
1) How can I get the MS server to serve DHCP requests to the 172.19.192
network, even if the source address isn't in that range (my answer: I
don't think I can)
2) Although I see the DHCP Discover request going out from the Cisco, I
see nothing in the DHCP log file about reciving the request and
rejecting it or ignoring it (is this normal) - is there any more debug I
can turn on? I need to confirm the Discover packet reaching the DHCP
server.
My thinking is that the Cisco server *should* put in an IP of 20.20.20.x
as the relay IP and thats why its not working, but I'm not sure.
Archived from groups: microsoft.public.win2000.advanced_server (More info?)
I found that DHCP Server requires Relay Agent IP (Bootp giaddr field) to
be in the DHCP server's sub-net. DHCP Server ARPs the Relay Agent IPSA
before responding. Setting up a static route to the RA may work also,
and perhaps allow a non-local IPSA for the RA?
HTH,
Russell Smith.
Adrian Marsh (NNTP) wrote:
>
> My thinking is that the Cisco server *should* put in an IP of
> 20.20.20.x
> as the relay IP and thats why its not working, but I'm not sure.
--
raasmith63
------------------------------------------------------------------------
Posted via http://www.mcse.ms ------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message1621968.html
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.