×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

DHCP Client will not work on a WLAN 4402

Unanswered Question
May 8th, 2006
User Badges:

Wireless Scenario


I am attempting to create a wireless network using a 4402 WLAN Controller and 1200 series LWAPP access points.


The WLAN Controller has the following interface settings:


Management Interface 10.71.50.9


Ap-Manager Intereface 10.71.50.8


Virtual Interface 1.1.1.1


VLAN 451 10.29.64.27



I have two access points that both pulled a DHCP Address and recognize the WLAN Controller.


Access Point 1 10.29.64.20


Access Point 2 10.29.64.21


I have configured the WLAN Controller to use the Cisco ACS Server for Authentication. I am using LEAP at present, but intend to go with certificate based authentication at a later date. The ssid I am using is ybor-wirenew. The client gets authenticated and associated but does not get an IP Address from DHCP.


I have tried the internal DHCP server on the controller, and although the wireless client gets a 10.29.64.x address it will not communicate with the default gateway or the rest of the network.


The only thing that works is creating a scope on the 10.71.50.x network. The client then gets an address and functions normally.


I need this to work across subnets. Is there something that I am missing???






  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
a.raaz Thu, 05/11/2006 - 03:39
User Badges:

Hey try the dhcp "option 43" on your dhcp server.- this

information you will get from 4400 series controller manuals from documentation section on cisco website.

It looks like you have issues on subnets here.


Also check your vlan 451 is setup up properly and check the default gateway is correctly set.


:-)

estill@cityofta... Thu, 05/11/2006 - 06:46
User Badges:

The problem is with your AP's and wireless clients being in the same subnet/vlan. I learned the hard way the thw WLC's expect the AP's to appear like any other client device on your wired network. Once they are associated with the WLC, your wireless clients are dropped into a different VLAN/subnet. An example config would be:

Management - 10.0.1.2 VLAN 1

AP-Manager - 10.0.1.3 VLAN 1

AP - 10.0.2.2 VLAN 2

Wireless Clients - 10.0.3.x VLAN 3

There are other known issues with crossing address space and the service port on the WLC.

vochiquycmc Sat, 05/19/2007 - 15:45
User Badges:

hi ,


help me plz,


i have 1 WLAN 4402, 1 wireless controller 2710, and about 12 access point 1242.


what should i must config on WLan 4402, on controller 2710, and on AP 1242.


can you send me some document step by step?


thank you very much!!


rupert.wever Sun, 05/20/2007 - 16:48
User Badges:

Sounds like your WLAN is still mapped to the management interface.

#1 - Make sure you have an interface using VLANtag541

#2 - Go to WLAN, and select the inteface from #1

Let us know if this solves the issue.

Cheers!

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode