Clients connected to AP541N cannot get DHCP address

New install with 3 AP541N's in a cluster. Two AP's are connected by an ESW-520-8P PoE switch and one on its own power adapter and a 3COM switch. I have set up a single SSID with WPA-AES encryption. I am connecting with HP 2740P tablets with Intel wireless cards. Clients can see and connect to the AP's but only some can get IP addesses from our Small Business Server 2003 DHCP server.
It's intermittent, some will get an IP and work for a while, while other can't. Then the ones that are working will drop and then none of the devices can get an IP. Then suddenly a few will start to work again. I have solid connectivity everywhere in the building but can't get an IP. Also, strangely, even when assigning a static IP I can not pass traffic, although it says I am connected with "5 bars" of signal strength.
Clients show up under Cluster>Sessions, but sometimes with really high counts of "Signal" and "Error Rate". However, even the clients with a "good" connection cannot get an IP.
Here is what I have tried:
Upgrade firmware on all 3 AP's to 1.9.1 (latest)
Wiped and reloaded the devices several times
Tried no encryption, WEP, WPA, doesn't make a difference
Tried everything described in this thread: https://supportforums.cisco.com/message/3078962#3078962 including the registry entry on the DHCP server
I have a spare AP that I put into production with the same load, but it didn't seem to make a difference.
Broadcast/Multicast limiting set to off
Upgraded to latest drivers on tablets; Boosted power on adapter to highest strength; Turned off power saving
I have exhausted all efforts in searching and trying based on my own experience, so any help the community can provide would be appreciated.
Thanks,
Derek

Hi Derek,
Have you considered using our Online Chat Support?
Cisco Online Chat Support provides live, real-time technical support for Cisco Small Business products through a web chat session with a Small Business Support Center engineer during local business hours
Note: Warranty Coverage is one year from the date of purchase.
Regards,
Cindy Toy
Cisco Small Business
Community Manager

Similar Messages

VWLC clients getting DHCP address from management VLAN

Hi,
We have a strange scenario whereby some wireless employees are obtaining addresses from the management VLAN.
Some details:
DHCP managed by MS DHCP 2008 R2 (in remote data centre)
Cisco vWLC AIR-CTVM-K9 running v7.6.110.0
AP's are a mix of 2602 and 3702 (46 and 2 of each respectively)
SSID's are employee, guest, and production devices (all mapped to their own interface with relevant VLAN tag as per normal)
AP's all in FlexConnect mode as per vWLC caveats
Some employees are receiving addresses in the wireless management VLAN. This network only has six DHCP addresses available as it is solely for AP's, WLC and HSRP gateway. Obviously this gets exhausted very quickly leaving us with a scenario where clients are not obtaining DHCP addresses.
I understand that with FlexConnect mode, it will assign IP's from the native VLAN. What I don't understand is why most clients receive addresses in the correct VLAN, but a handful do not, and then cannot get an address from DHCP. Obviously the ideal scenario would be to put the AP's into local mode but unless this has changed in a SW release then I don't believe it's possible...
My question is: How do I get ALL the employees to obtain addresses from their interface and not the management VLAN?
Thanks in advance.

Hi,
I think we need a closer look to your configurarion to eliminate some possibilities:
- What is the WLAN security you choose?
- What is the interface that is configured under the WLAN?
- Does your WLAN have local switching enabled?
- If your security is using RADIUS server, do you have AAA override enabled under the WLAN config?
- If your security is using RADIUS server, do you send any attributes to the users?
- You have eliminate that clients that got management vlan IPs are always on same AP or they can be on any AP.
HTH
Amjad

I cannot get my address book to merge with iCloud?

I cannot get my address book to merge with iCloud?

Yes, the settings all appear to be correct on the Info page in Itunes. I have contacts checked to synch, calendars and mail accounts but only the contacts are not moving to the Iphone.

RRAS 2012 With DHCP Works, Cannot Get Static Address Pool To Connect Completely

Hello Forums Users:
I have set up RRAS/DA 2012 successfully incorporating my AD DHCP server. Every connection works and I see all networks that I have VPN tunnels set up with, which is totally cool. However, I want to assign remote VPN users IP's from a
static address pool - and while the setup completes without issue and the client connects, I can see absolutely nothing. No good pings, no connect to Lync client, Outlook, etc. etc.
I am OBVIOUSLY missing something but have no idea what that is. Do I need to add something (and I really have no idea what that "something" is) to RRAS config so the static address pool (192.168.40.0 in this case) has the same access as
the AD DHCP pool does?
Thanks again for taking the time to check this out and comment.

Bill:
Thanks for the reply.... yes, the idea is to free up a pool of IP's large enough to accomodate all 170 staff. Our current 192.168.2.x DHCP hands out 150, but I need to plan for DR/BCP when other locations (about 110 users) remote in when their
location goes dark.
I already have VPN tunnels between the main locations and a VPN user can see ALL of them when it gets an IP from DHCP. Are you saying that I have to add routes to all the routers/firewalls to accomplish this?
Or would I use IPv4 Static Routes? A network I'd like access to is 192.168.14.0 /24. Would the route look like any of these? Sorry it's not clear what I would use as the gateway (192.168.2.1 is the RRAS server network gateway, 192.168.2.6
is RRAS IP)
Destination Net Mask Gateway Interface
192.168.14.0 255.255.255.0 192.168.2.1 LAN
192.168.14.0 255.255.255.0
192.168.14.254 LAN (
(.254 is the remote gateway)

Wireless clients cannot get ip address

I have 7 WLANs configured all work fine but the latest. The 7th WLAN I configured will not let clients get an IP address. I can plug a wire into the port with the same VLAN configured on the port and I get an IP address but wireless clients connected to an AP on that port cannot get an IP adddress. Any suggestions would be appreciated.

Hello,
where is the DHCP server configured?
- do all other 6 WLAN's work fine with the same DHCP server.
- do you have any H-REAP VLAN mapping , or AP groups configured?
they will override the WLAN-interface configuration.
Kind regards
Talal
=======
please rate answers that you find useful , and mark as answered - when it is :-) - so others can find it easily

Wireless Router 877W users cannot get ip address from DHCP

Users can connect to wireless but they cant get ip address what can be the problem ?
Thanks
no aaa new-model
resource policy
ip subnet-zero
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 10.10.10.1
ip dhcp excluded-address 192.168.239.1 192.168.239.50
ip dhcp pool users
   network 192.168.239.0 255.255.255.0
   default-router 192.168.239.1
   dns-server 4.2.2.2
bridge irb
interface ATM0
no ip address
no atm ilmi-keepalive
dsl operating-mode auto
interface ATM0.1 point-to-point
no snmp trap link-status
pvc 8/35
pppoe-client dial-pool-number 1
interface FastEthernet0
interface FastEthernet1
interface FastEthernet2
interface FastEthernet3
interface Dot11Radio0
no ip address
encryption vlan 1 key 1 size 40bit 0 1234567890 transmit-key
encryption vlan 1 mode wep mandatory
ssid wirele
    vlan 1
    authentication open
    guest-mode
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
channel 2437
station-role root
interface Dot11Radio0.1
encapsulation dot1Q 1 native
no snmp trap link-status
no cdp enable
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Vlan1
description $ETH-SW-LAUNCH$$INTF-INFO-HWIC 4ESW$
ip address 192.168.239.1 255.255.255.0
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1452
bridge-group 1
bridge-group 1 spanning-disabled
interface Dialer1
ip address negotiated
ip nat outside
ip virtual-reassembly
encapsulation ppp
ip tcp adjust-mss 1452
dialer pool 1
no cdp enable
ppp authentication pap callin
ppp pap sent-username xxxx password xxx
crypto map MerkezVPN
interface Dialer0
no ip address
interface BVI1
no ip address
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer1

go into config t and add "bridge 1 route ip" and see what you get....

Cannot get On 100 to get DHCP address

I have used two different network cables, 3 different network locations and factory reset device twice but cannot get it to get a DHCP address.
It boots and status 1 goes solid amber and status 2 blinks amber
Anyone have an issue like this before?

thanks Robert,
The customer has both voice and data scopes defined on a single dhcp server (C2811 Router). I've managed to get the static ip configured on the ON100 agent. This was accomplished by moving the ON100 lan connection to an uplink port on the switch. Odly enough, I was able to see the ip address assignment in the dhcp pool, but the configuration on the ON100 still had the static configuration from the previous network it was moved from. I used the new dhcp assignment to log into the device and make the change. I am now having the following two problems:
1.) After moving the ON100 back to a switchport (so the pc and monitor would be in the same network surface), the ON100 is still pulling a second ip address from the voice scope, (even though the static ip is still assigned to the mac address). When I clear the entry in in dhcp cache, it reappears, leaving me with a voice and date ip for the same mac.
2.) When attempting to activate the ON100, I get the following error, could this be related to moving the unit from the lab to the customer site?
Subsystem Status
Cisco OnPlus Network Agent
Customer Name       WCV
Portal ID       64907.7376.cisco-onplus.com
System Name       onplus20F7DA
IP Address       10.1.1.110
Netmask       255.255.255.0
Network Gateway       10.1.1.1
MAC Address       64:00:A1:20:F7:FA
Current       OnPlus-Release-7.3.2.021
Base Firmware Version       34.47
Device Model       ON100
Firmware status       Current
Account Status       Portal access error: Operation timed out after 10008 milliseconds with 0 bytes received
PKI Subsystem Status       OK
Settings Monitor       Running
Service Announcement       Running
Zeroconf Management       Running
Discovery       Running
Time Service       Running
Monitoring       Running

No Hyperv Virtuals get DHCP address - but Physical Host Can

HyperV Server 2012 Core on a dedicated machine on local domain.
Machine connected directly into local network that has a DC running DHCP.
None of the VM's can get a DHCP Address from the server. Even if i set static addresses still they cannot route anywhere, cannot even ping the HyperV server they are sat on but other local machines can!!!!
The physical host cant ping the
The physical HyperV server has no problem getting a DHCP address or any routing issues, nor do any of the other clients on the local network, including another HyperV server running server VM's
What ive tried so far
Deleted Virtual Switch and removed the NIC from the virtual hosts in HyperV Manager- then re-adding new one.
Put in a different network card
Removed Physical host from Domain, renamed machine to different name and re-joined
Used different IP addresses for the Physical host
Reloaded the HyperV server from scratch and created new VM.
Ive had HyperV previously running on this machine without problem, so now i cant see why i cant get it running again.
Anybody have any suggestions on what i can try next, im all out of ideas.

Hi Fulgent,
I am assuming that , the hyper-v server have two NICs , one for host and the other one was configured as an external switch for VMs .
If the VMs can not access the dhcp and local network , please try to delete the external switch then uninstall the Physical NIC in device manager and click " scan for hardware changes " to reload it.
Try to create external virtual switch for VMs again .
Any further information please feel free to let us know .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Help please - cannot get IP address

Hi everyone, I have a WRT54GS router with WEP encryption. I have 2 laptops, both with XP. I cannot get one of the laptops to get an IP connection. It connects to the router, but when I run ipconfig, I get the following error message Windows IP Configuration An internal error occured. A device attached to the system is not functioning. Please contact Microsoft product support services for further help. I have many years of IT experience, and I've also had my network admin brother help me, but we can't figure it out. I have entered the WEP address correctly and have unchecked the box "Key is provided for me automatically". The key index is the same on both PC's. We have released the IPconfig. The PC that can't connect has been recently acquired and has never successfully got an IP connection on this wireless LAN. Any suggestions greatly appreciated. Thanks so much, Lynne

Sounds like an issue on the computer itself not the network. You might need to uninstall reinstall your wireless card.

Linksys WRT54GL won't get dhcp address from isp

I'm using Linux.
I just bought this router because it had good reviews on Newegg but for the past 4 hours I have gotten nowhere with it.
When I connect the router to the net and click the refresh button on the browser interface, the router doesn't go out and get a dhcp address. I see the initial click of the mouse that hits the modem but no information comes back. No addresses are updated.
I have tried cloning the mac address but that does no good either.
Any hints appreciated.
Thanks

Try resetting the router for 30 secs in such a way that power light is blinking on the router.Also, try doing the complete network power cycle i.e., unplug the power cables from the modem & from the router.Then, plug in the power cable to the modem first once all the lights are solid on the modem you could plug in the power cable to the router & then try configuring the router & it will definately work!!!

Hyper-V - Legacy NIC not getting DHCP address at boot, but when OS loads the NIC gets a DHCP address

Hi, I have a strange issue with DHCP.
I have a lab environment on a single Hyper-v 2012 Server. AD, DNS & DHCP exist on a single virtual machine, I have a flat network 192.168.1.x, all VM's are on this network. I have authorised DHCP and Setup the scope.
A VM has a legacy adaptor, the legacy nic is configured in the boot order as the first device.
When I boot the machine I do not get a DHCP address, however when the OS boots the Legacy NIC then gets a DHCP address??
I need to use a legacy NIC as I need to PXE boot the VM, however I should get an IP address at boot time, which I don't get.
I have run Wireshark on the DHCP server, I can see the legacy NIC do a "DHCP Discover and the DHCP Server respond with a DHCP Offer" however all communication ends there. I have disable all firewalls and I see no reason for this not to work.
I have done tis before with no issues but I am unable to get this to work on this server!!!!!

Hi
According to your description , it is recommended to make sure or do :
        In your environment , there is no any other valid DHCP, BOOTP or proxy DHCP offers.
        Make sure if the DHCP server is overload.
        So suggest to test that creating a new “internal virtual switch” and change the settings of VM which provide DHCP service to connect to the new “virtual switch”.
        Then create a new VM use legacy NIC also connect to the new “internal virtual switch” and try to PXE Boot.
Hope this helps.
Best Regards
Elton ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Not getting DHCP address on HP 8000 Elite

I'm using the Feb 2010 CD. Windows 2003 DHCP server
Boot with the cd and no dhcp address.
If I type "dhcpcd eth0 -n" enough times I will eventually get an address, although the first time it's usually "err, eth0: Failed to lookup hostname via DNS: Name or service not known"
The same CD works OK with a HP dc7900, dc7800, etc. It looks like they all have the same Intel e1000e nic, but maybe no?

I'm starting to investigate issues that may be similar to yours and I had a
thought that I thought I'd share with you ;-)
In what may be a related situation one of our admins is having issues with
the dhcp client on an openSUSE 11.1 (and 11.2) during and after the install
on some Dell servers. Sometimes the dhcp client will not get an ip address.
After some poking he found that there are in fact two dhcp clients available
: dhcpcd (dhcp client daemon) and dhclient (package is called dhcp-client).
The default client in openSUSE - and presumably the Linux environment of
ZENworks Imaging - is dhcpcd v3.x. It seems that there are a number of
reports of this client being problematic. The maintainer of this client has
recently released v5.x which may resolve the issues with v3.x.
In our testing on openSUSE dhclient works much more reliably than dhcpcd,
where "more" is equal to 100%. None of this helps us of course, but it is
background info that leads up to my idea: is it possible to use the other
client, dhclient in the ZEN Linux environment? I don't know if this client
is even included in the ZEN Imaging Linux environment or not. If it isn't
then maybe it might be possible to modify the initrd/root/linux files to
include it. This would at least let you have another means of acquiring a
dhcp ip address. I'm sorry that I do not have the Linux skills to do more
than make a suggestion...
Cheers,
Ron
PS I have submitted an enhancement request via the openFATE website to have
the dhcp client daemon upgraded to v5.x. Maybe if you think it a good idea
you could login to the openFATE portal and vote it up!

WRVS4400N Unable to get DHCP address via wireless

I am having an issue with the WRVS4400N. I am unable to get a DHCP address via wireless. If I connect directly to the router via RJ45, I get a dhcp address an and able to get to the internet. Has anyone ran into this issue.

This seems to be a problem with the latest firmware (v1.01.03) available from Linksys for this router. The stock firmware for my WRVS4400N router assigned DHCP addresses to wireless devices without any issue. As soon as I upgraded the router to v1.01.03, the router no longer assigns DHCP addresses to wireless devices. I have verified there is no issue with the router itself by rolling back to version 1.00.16 with the recovery utility.
One workaround I noticed with firmware v1.01.03 is that the router will actually assign DHCP addresses to wirelss devices temporarily if it assigns a DHCP address to a device connected to the physical port. This only last for a little before the router stops giving out DHCP address to wireless devices though. It's a shame since I was looking forward to some of the features in the v1.01.03 firmware.
Chuck

AEX fails to get DHCP address, but works on DLink

Sorry for the long post -- I'm hoping the details will help you diagnose the problem faster in the long run.
My DLink router gets a DHCP IP address from the (Comcast) cable modem, but when I switch to the AirPort Extreme (5th gen, refurbished), it doesn't. It shows an autoconfiguration IP address of the 169.254 variety, suggesting that DHCP isn't working for the AEX. (Just fyi, my girlfriend's macbook can connect to the AEX and get 10.0.1.x IP addresses; I can ping the AEX over wifi.)
Airport Utiltiy shows a red number 2 with a single error indicating Internet failure to get IP address or something. The suggested solution is power-cycling the modem; failing that, contact the ISP. Contacting Comcast was amusing but useless...they gave me instructions for setting up AEX with a DSL modem -- twice -- without understanding my objection!
The AEX is configured for DHCP (not Static or PPPoE), and uses all stock settings (I did both a soft reset and used the Airport Utility to restore default settings...not sure if those two are the same).
I've tried power-cycling the router and cable modem numerous times, including leaving them off for 15+ minutes and leaving the AEX connected for 6+ hours. I tried using the DLink to release the DHCP reservation and then quickly switching the cable over to the AEX.
I read somewhere that resetting the "CMTS (cable modem termination system)" might help. I mentioned it to the Comcast tech support, but they didn't respond.
At this point, I'm not sure what else to try. It could be the refurbished unit is broken, but 95% of the time these sorts of things are configuration issues. (I know a fair amount about networking, but I'm new to Apple products so I could be doing something stupid.) I may try connecting the AEX to the LAN side of the DLink to see if it can get a DHCP address from that...but I'm clearly grasping at straws.
<whimpers>...Help?

Update: The AEX does get a DHCP address when connected to the LAN side of the DLink gateway. (But the AEX doesn't get one when connected directly to the cable modem. Yet the DLink gets a DHCP address when connected to the cable modem.) So...??!?!!!

Get message "the Connection was Resdet" cannot get into email

I just completed a message and did a save so it would be a draft and I got this "The connection was reset" and so I could not get by that so I powered down and up again and still get the same message and cannot get into email on my account {edited for privacy}
Doug Hadley
{edited for privacy}

What e-mail client are you using?
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Clients connected to AP541N cannot get DHCP address

Similar Messages

Maybe you are looking for