06-18-2008 01:54 PM - edited 07-03-2021 04:02 PM
I have a 2106 controller setup and all the APs associate to it fine. I can access the web interface fine. When we add machines to the wireless network we start getting "IP address conflict" in Windows XP. The network is one subnet with 3com switches on native VLAN1.
The controller:
Management: 130.0.0.60/16 Untagged Port 1
AP Manager: 130.0.0.61/16 Untagged Port 1
Virtual: 1.1.1.1
DHCP Server is 130.0.1.227
The code is 4.2.112 and using Windows 2003 server for DHCP. The APs are getting different addresses, but the clients are not.
I am thinking of running "config dhcp proxy disable" to see if that corrects the issue, but I dont know if that is the right route to take.
Anyone have any ideas?
06-18-2008 03:03 PM
Recheck your configuration on your wlc and also your ip helper address on your layer 3 interface.
06-20-2008 06:38 AM
I looked over the configuration again and everything seems fine. I talked with the IT staff about a helper statement and they said they dont have one because their network is one big network. They only have the one vlan.
Would it be possible to run DHCP off the controller to try to narrow down the problem? We could add a range of addresses to exclude from the DHCP server and run them on the controller instead.
06-21-2008 11:13 AM
You can do that.... One thing you should know is that it is recommended that your wireless users are not placed on the same subnet as the wired. This has caused issues in the past and that is why its not recommended to have a mixed subnet.
06-26-2008 01:19 PM
I have tried the DHCP server running on the controller and we still get that error.
Since the 2106 only does layer 3 LWAPP, if we changed to a 4400 series controller that can do layer 2 LWAPP, would that work in this environment?
Thanks fella5 for the information you provided.
06-26-2008 01:34 PM
Layer 2 is only supported in the old airspace ap's. Post your show run-config.... so we can see if there is a configuration issue.
06-26-2008 01:59 PM
06-26-2008 05:38 PM
Looking at your configuration, here is what I would change:
1) Upgrade the boot loader to 4.2.112
2) Disable Ethernet Multicast unless you are using it.
3) Add the secondary DHCP 130.0.1.128 to the AP-Manager interface (for consistency)
4) Remove the DHCP override on the bcmh profile. It is pointing to a DHCP server of 130.0.0.60
5) Disable WMM unless you have IP phones
6) bcmh is configured for WEP, so verify the client is setup correctly.
That is all for now. Hope this helps.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: