04-29-2010 07:50 AM - edited 03-11-2019 10:39 AM
Friday I upgraded my asa to software 8.2(2). I found out monday that users running anything other than windows XP, can no longer obtain a DHCP address my ASA. While trying to obtain a DHCP address a box pops up saying "There is an IP Address conflict" and it obtains a bad network address such as 169.254.4.X. It should be pulling down a 172.16.32.X address.
I have a guest wireless network that belongs to the DMZ. The asa acts as the dhcp server & dmz router/endpoint.
Has anyone else experienced this problem?
04-29-2010 08:14 AM
I'm not sure if this is part of the problem, but I found this in my log.
1 | Apr 29 2010 | 09:55:15 | 106021 | 169.254.4.101 | 169.254.255.255 | Deny UDP reverse path check from 169.254.4.101 to 169.254.255.255 on interface DMZ |
the 169.54.4.101 address is the bad address on my test machine when it cannot obtain a good DHCP address.
05-01-2010 04:54 AM
Can you double check if the DHCP server configuration is correctly configured? ie: all configuration still exists after the upgrade?
05-03-2010 08:58 AM
TAC was able to help me fix this.
We had to add this to my config:
sysopt noproxyarp dMZ
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide