Is in the config the DHCP server resides on VLAN 11(IP Address: 10.69.63.10) so the helper-address is defined for the right VLAN. This is a cut out from the Cisco Manual for my switch: interface VLAN 14 ip address 10.33.234.1 255.255.254.0 ip helper-address 10.5.1.2 so also the different subnet should not be an issue.
I possess a hub site with a Cisco 2811 and several remote sites, working a combination of Cisco 851 and 871 routers configured for site-to-site VPN. I have always been in the procedure of incorporating DHCP scopes and DNS specific zones for the remote control computer systems to allow easier administration, and have many of these sites successfully tugging IP tackles and registering in DNS at the central site. Here's a sample of the speech config from a working site, which I duplicated to another web site (10.30.1.1):
And right here's UDP packet debug from the non functioning site, 10.30.1.1 which provides identical settings (hardware and software program, both Cisco 870 operating g870-advipservicesk9-mz.124-15.T7.) As you can discover, the router can be correctly packaging up the transmission from a Processor sending a DHCP put out and sending it on to the assistant tackle.
But at this site, the helper address in no way responds, or the response never get through. I have not however place a monitor on the DHCP machine, as I'meters out at the spoke site.that's the following step. But all the access-lists are the exact same, and what's even more, conversation to the DHCP server, state, via remote desktop, functions flawlessly. Data source connections to machines at main site are great. Every type of conversation works, TCP or UDP, except DHCP queries.
So, what have got I skipped? The DHCP machine will be a Windows 2008 machine, and provides several scopes on it already, is right now there a limit to the complete amount of scopes allowed? I didn't believe so.
Obviously the scope is activated. The tackles match. The exact same DHCP server is gladly serving contact information to all the some other remote websites.
Obviously the scope is activated. The tackles match. The exact same DHCP server is gladly serving contact information to all the some other remote websites.
atroonatroon
3 Answers
Twice examine your scope on the DHCP server, It almost seems like DHCP is not viewing a valid scope definition for this subnet. Create certain your router tackle is appropriate in the scope options.
Try eliminating the range and re-adding it from nothing to notice if you may have got something inserted incorrectly that you're also not viewing.
Nick ZeppNick Zepp
I have got exactly the same senario and have got located the problem, but don'testosterone levels possess a answer :-(
The unicast dhcp demand is developed before the NAT will take location and the IP Deal with of the inside of interface is integrated in the request as component of the data field mainly because properly as becoming the IP resource tackle. The IP supply address will get NATed on the outdoors interface and so the packet looks fine.
The problem comes when the DHCP server attempted to react to the demand. Everything functions good in DHCP except it transmits the response to the addres it discovers in the DHCP demand (ie the inside interface) and not really the IP supply address of the packet it obtained.
I hope this assists to discover a solution as I as well am nevertheless incapable to function it out.
RickRick
I understand this can be an aged write-up, but for anyone else searching, the solution to the query about debugging IP Assistant can be 'debug ip UDP' You will see output such as the using:
RWRRWR