I ran into this a while back. What's happening is when the router at the remote site is taking in the DHCP broadcast on eth0 and sending it to the DHCP server, it's using the primary address on the receiving interface (i.e. eth0 in your case) and sending that DHCP request on. When the DHCP server, it tries to allocate an IP in the same subnet (scope) with the IP of that request (again, which is the primary IP on the eth0 of the IP-helper router). In our case, our DHCP server wasn't handling the IP range that included tha primary IP on the eth0, so it wouldn't respond with an IP.
Our solution was to swap the IPs. In your case that would be changing this on the spoke router: interface Ethernet0 ip address 192.168.12.1 255.255.255.0 secondary ip address 192.168.2.1 255.255.255.0 to this: interface Ethernet0 ip address 192.168.2.1 255.255.255.0 secondary ip address 192.168.12.1 255.255.255.0 This will allow the PCs in the 192.168.12.0 network to receive IPs from the DHCP server over the WAN. HTH, Mike W. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=35576&t=35532 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
