DHCP issues on wireless

When I connect to my wireless router (D-Link WBR-2310 I believe) using my mac, it gets the default self-assigned address instead of DHCP-assigned address. My PC connects fine wirelessly and wired over ethernet. If the router is reset, it works fine. If I assign manual address to iBook wireless, it works fine (by "works fine" I mean that I can connect to the internet).
Had similar problem with my old Linksys router (Linksys WRT54G) where the following devices had issues connecting to the internet iPod Touch, iBook, PowerBook, and MacBook. This was under unsecured, WEP and WPA settings.It seems that the issue is resurfacing with my current router.
Currently, I am using WPA security (I don't like WEP and neither does my PC). I would rather not switch security settings to unsecured due to the close proximity of my neighbours (yes it's canadian spelling!).
Any suggestions?

I have encountered this same router and issue visiting my future in-laws for the holidays. DHCP with manual address appears to work, but I also still encounter occasional drops. The router is setup for WPA2 security, and support a mix of Mac and Win clients. I haven't put a lot of time into trying to fix it, but here is what I know so far:
1) Sometimes it does just work with DHCP
2) DHCP with manual address works, but will still drop occasionally for brief periods
3) Sometimes, just turning the airport off then on again will resolve the issue and pull an address
4) Just waiting about 30-60 seconds also seems to work -- usually
5) Plugging into the wire works great!
I haven't sat by the router and worked on this, but it seems that occasionally the router just drops the signal, and with it the DHCP assignments. Something about the DHCP implementation is very slow, and it just take a while to get around to assigning an address to my machine. I haven't looked into firmware updates since it's not my box and I don't want to mess it up further and then leave, but that's certainly something to check into.
We also have an 12" PB that cannot even connect to the wireless with the "Error joining wireless network" message. Haven't been able to figure that one out at all.
They may just be getting an Airport or Linksys as a late x-mas gift here... (as my connection drops again while I type this! Airport off, airport on, wait 30 sec, and we're back)
Cheers, and good luck!

Similar Messages

10.5 DHCP issues with Wireless - self assigned IPs?

We're having an issue with Mac OSX 10.5.4 clients, running the latest software updates, not getting an IP address via DHCP on our wireless network.
We're using Cisco APs, with multiple VLANs & SSIDs. They authenticate, but get automatic self-assigned IP addresses. None of our PC clients are experiencing this issue, nor older 10.4.x OSX clients. This looks like a bug, from what I was able to discover:
http://forums.macrumors.com/showthread.php?t=384947
Is Apple aware of this, and/or working on a fix? I've seen many issues over the last year or so with Airport clients and wireless connectivity..

This is a "user to user" help forum that is designed as a self-help system, independent of Apple's Technical Support system. No one here can say what Apple knows or is doing about a specific issue (pure speculation is discouraged). We share experience and suggest possible solutions or workarounds.
One way to ensure that your issue is brought to Apple's attention is to use their feedback form for OSX - http://www.apple.com/feedback/macosx.html
Since the link you posted is from late last year, there have been many updates to Leopard. Some of the updates mention network reliability. Even though Apple has stated that the Pram chips don't control network connections, I have had some luck by Zapping The Pram - http://support.apple.com/kb/HT1379 - Remember to check your System Prefs for things like date/time settings after you Zap.

Wierd DHCP Issue

Hello All,
I facing a very wierd DHCP issue and would like to know your thoughts on it.
I have my wired clients on vlan 1 and wireless cleints(eap-peap) on VLAN 2.
We are facing an issue where multiple wired clients who were on access port vlan 1 are receiving IP address from wireless subnet(vlan2) -their DHCP server was the WLC virtual gateway IP address(1.1.1.1). This is causing an outage to few wired clients.
The WLC trunk does not have vlan 1 allowed on its ports and all APs are in local mode and all on access vlan.
I'm not entirely sure whats causing this, but only way I think this is possible is that 'A Client' laptop has his network connections bridged - his wired nic on VLAN 1 and wireless NIC on vlan 2, acting like a WGB, which is causing new wired clients(vlan1) DHCP broadcast request forwared through the bidge mode laptop to AP--> WLC. Do you think this is possible??
Havent been able to identify which client is causing this issue yet.
Has anyone faced a similar issue and anyway to block this through WLC/ACS policy?
Thanks
Jino

Hi,
Might we consider to make use of network monitor to take a look at the traffics for the 1.1.1.1 address?
How to use Network Monitor to capture network traffic
Download link here:
Microsoft Network Monitor 3.4
Best regards
Michael Shao
TechNet Community Support

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

Airport Extreme - possible DHCP issues on UTP ports?

I have a recent (late 2012) iMac which has been consistently connected to my Airport Extreme via UTP with no issues until recently. The Airport Extreme is connected to my single port Motorola 5101 Bigpond Cable Modem.
Connected to the Airport Extreme via UTP are the iMac and a Lacie 4TB NAS media server. There are generally multiple devices connected wirelessly (iPhone, iPad, PS3, XBox) again with no issue.
I have a PC connected to an Airport Express at the other end of the house (PC has no wireless card) and the Express and Extreme are bridged with a common SSID.
Saturday night the "house network" occasionally lost wireless (iPhone switching to 3G) but after resetting the Extreme and the iPhone this seemed to settle down and has been working fine since then (4 days prior to this post).
Later on the Saturday night my iMac lost internet connectivity and resetting the Airport Extreme and resetting the Motorola 5101 did not help. Eventually rebooted the iMac and the Extreme and the 5101 and eventually (after a few minutes) internet connectivity was restored. (Error was "no IP address" and Airport Utility could not see either the Extreme or Express). Connectivity was restored by first turning on WiFi on iMac which immediately got an iP (10.x.x.x) allocated and then after a few minutes the UTP link also came up and remained up when WiFi was turned off.
The iMac has since "lost internet connection" around 3 times in total and a similar process to the above has not always restored connectivity – i.e. doing all the above worked some of the times and did not work others.
When this problem is happening on the iMac UTP connection there are no issues with wireless devices getting an IP allocated.
I am now running the iMac on WiFi with the UTP cable removed. Today I will try a new UTP cable between the iMac and the Airport Extreme to see if there is perhaps some intermittent cable issue.
The Airport Extreme and Airport Express (both a few years old) are running 7.6.4 firmware. I had recently setup timed access for a few wireless devices and also trialled the "guest wireless account" but these were set up around 1 week prior to the recent issues occurring. I have now removed both of these so that the Apple network devices are back to the settings they had which worked fine for years (albeit with different firmware versions over this time).
My diagnosis is that it seems that there is a problem with IPs being allocated by DHCP to devices connected to UTP ports but not over wireless. The only thing that seems to contradict this is that the Lacie NAS drive which is UTP connected (to UTP port 3) seems to still work and be accessible without issue.
So am also wondering if there is some intermittent iMac issue with the UTP port or with the cable. Will change the cable today as mentioned above to confirm or otherwise.
Any advice on further diagnostic processes and/or thoughts on Airport Extreme issues (hardware or firmware) etc would be appreciated. A search of the forums did not show anything similar but my search was not super-extensive.
Thank you for any help anyone can provide.
Andrew

In the end after LOTS of troubleshooting and testing - and WAY too much frustration Apple - this issue has proved to simply be what I assume is a bug in the Automatic network location management under Mavericks and I had this issue to a lesser degree with 10.8.5.
I have now setup a "Home" new network location and my connection has been 150% stable ever since.
So nice to not need to reboot my Mac 7 times a day or more after several weeks of significant frustration.

RV042 second DHCP issue

Hy all,
I have a CISCO RV042 in a network with 2 subnets 192.168.1.x and 192.168.2.x and I want multiple DHCP on both subnets. How can I do that?
If I use a second router for the second subnet (192.168.2.x) to use its DHCP. The bandwith management will work? Do I need port VLANs?
The network is like this:
The RV042 is the main router thru it we acces the internet, it also suplies DHCP 192.168.1.x, I enabled multiple subnet for 192.168.2.x.
The reason I want 2 subnets is beacause I have 2 acces points for wireless clients and I want to use rate control on WAN with bandwith management from RV042 too give wired clients more bandwith than wireless clients.
I know that RV042 doesn't supply multiple dhcp like RV180,but I needed dual WAN.
Thank You

Hi,
Thank you for the answer, but my issue remains, below I tried to write a little bit more
If I make the configuration like this:
On CISCO RV042:
Port based VLANs:
VLAN 1 on LAN 1
VLAN 2 on LAN 2
On AT-FS750/24 switch:
Port-based VLANs:
VLAN 1 for 2,3,4 ports where 2,3 are the AP's (TL-WA901ND) and 4 uplink to RV042
VLAN 2 for the rest, let's say 5,6,7,8,9, etc ports that are for wired clients.
Tagged-based (802.1q):
VLAN ID 11 for 2,3,4 ports where 2,3 ports are tagged are the AP's (TL-WA901ND) and 4 untagged uplink to RV042.
VLAN ID 22 for 2,3,4 ports where 2,3 ports are tagged are the AP's (TL-WA901ND) and 4 untagged uplink to RV042.
On AP's (TL-WA901ND):
Multi-SSID with tagged based VLAN:
SSID 1 on VLAN ID 11
SSID 2 on VLAN ID 22
If I use the second router (not supporting VLANs) only for DHCP for the wired clients with the configuration:
-In the WAN I'll plug RV042 LAN 2 (VLAN 2) and from its LAN 1 I'll connect LAN 5 (VLAN 2) in the switch.
second router WAN:
IP:    192.168.2.2
SM:   255.255.255.0
DG:   192.168.2.1
DNS: 192.168.2.1
For DHCP
LAN1:
IP:   192.168.3.3
SM: 255.255.255.0
It will work to split wireless from wired ?
How can I split the 2 wireless networks in guests and business more efficient?
Let's say the wireless clients from "SSID 1" have to have a guaranteed bandwidth.!
How can I set it up so the wireless clients gets different IP class on the 2 wireless networks?
Can I use the rate control from RV042 on the IP (192.168.2.2) of the second router?
My problem is that I need all the subnet available from RV042 DHCP for the wireless clients (192.168.1.x), because RV042 can route only in class C (254).
I configured the static IP's in 192.168.2.x subnet for Ethernet equipments, I used multiple subnets from RV042.
Momentarily I use COS from the switch for the tagged VLAN to prioritize the traffic, but this is no longer an option for me.
Can a CISCO RV180 make a difference in this configuration?
Thank you,
Dragos

Very weird dhcp issue

We've started 're-vlanning' our main location here, breaking up depts
into their own vlans.
All seems ok so far, aside from a real doozy.
For the IT vlan, we have one address that will not talk to our web
content mgmt appliance. It's the 2nd address in our assignable pool,
and it doesn't matter if it's dhcp or statically assigned, that address
will not talk to that device.
That is the *only* device that cannot be reached from this particular
address in our dept vlan, every other one works fine.
Any ideas on this?
Stevo

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> and it doesn't matter if it's dhcp or statically assigned, that
> address
So.... the title of this thread should actually be 'Very weird non-DHCP
issue', since your own testing confirms this has nothing to do with DHCP?
If you do a LAN trace on this machine as well as your web content
management appliance do you see packets on either side? Both sides? If
not on both sides but you do on the source (workstation) side see
packets going out, then get LAN traces after each network device
(switch, router, firewall, etc.) to see when the packets disappear.
Feel free to post the LAN traces somewhere with descriptions of IPs,
ports, and what you should be seeing, if you want to post them somewhere
for review.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJP4jFPAAoJEF+XTK08PnB55aMP/3Rg9u6LX6jFCXGYuex/oXdS
NZ/liqfCgjyIcykWWeKGgdtm2I7JZOcFiG8YW2le55mcltvCL1VJW +1VGng4kZER
0f4hjfyQ3CcQ6HIU3RM6VL5U2Pblb80MsEQe0qo0xgtPXipmjs i7Q0xIv9p0wT7A
7JMkfgM9tfuI5Yro+BDLfSIkFWicKuKs1sKpNugKalPuyyRrzW IiznoalIKFshon
a40ETLJVZmngBYfqfeZL9nPNsFlveFNXrDkdbl2WbaprsHtNnA NwZfVUIlc5kOCT
MknY0GXof4/tk149OVCCLgjEzoRtTIZH0BJTHQwW7ANkWUUNYwi49+Mk46V0o awl
oe1aA+NK9gl2bWXWLCtTro4ERSVMvkcI0OffytrfcBsqdCKg/g3QPMjV3kiVEULI
xnSTsqFgOl2qO8qGaL6FJtk39ZBnCwqDPtmoNt93OK4hAhWBuA Xihc+kiQHrwkpO
O04quZu8qQG6A6qwFDr+r+QqarFR3kielfvi7H6o5iLfZn/sDhvijGOAknJVctH8
j8fezki9PMznkcT+of2Oe4T99K9fChN2WFSgUKdlpkYSjbkmjP fdbWloou+WBjCm
7hHwnAbKPPgoN8aPPfw9rG9E+K/0YW2kt4wRu79BEDvF6eMv0UdDPE1qPuw1ttmm
jg2zzMZDkgIG39A0P3u7
=+fCy
-----END PGP SIGNATURE-----

6500 DHCP ISSUE

Hello All,
I am having an issue do DHCP from the 6500, and was hoping someone cant help. So, I tried to setup DHCP from the FWSM to the clients and this worked fine with giving out the IP, however the gateway for devices on the inside is supposed to be the 6500, not the FWSM, which is why the clinets wouldn't get out to the internet. Do I need to set up DHCP relay on the FWSM or does anyone know the way I can setup DHCP on the 6500 to give out IP's to the clients. Again just to reiterate, when I setup DHCP on the FWSM the clinets get the IP's but do not get out to the internet and when I setup DHCP on the 6500 the clients do not get an IP. Also I know tghis is a dhcp issue becasue when I assign a static address on the network the clients get out fine. Thanks in advance for the help!
6500 Config
ip dhcp pool TEST
   network 1.1.1.0 255.255.255.0
   default-router 1.1.1.1
   dns-server x.x.x.x y.y.y.y
FWSM Config
FWSM/TEST# show run
interface Vlan3
nameif outside9
bridge-group 1
security-level 0
interface Vlan203
nameif inside9
bridge-group 1
security-level 100
interface BVI1
ip address 1.1.1.4 255.255.255.0
passwd 2KFQnbNIdI.2KYOU encrypted
access-list INSIDE1_IN extended permit ip any any
global (outside1) 1 x.x.x.x
nat (inside1) 1 1.1.1.0 255.255.255.0
access-group INSIDE1_IN in interface inside1
route outside1 0.0.0.0 0.0.0.0 1.1.1.1 1
FWSM/TEST#

Hello Alain,
Thanks for your quick response. I attached a Diagram of the layout. Just to let you know this is an FWSM with many virtual contexts and most including this one that are Transparent. I understand that I need an access-list on both ends to specifiy so the FWSM opens it, I am just having issue because the FWSM sees this as unsual traffic and the access-list needs to be on-point to work. Thank you for the response and I'll look forward to hearing back from you.

VRF and DHCP issue

VRF and DHCP issue
We have a 6500 ( 12.2 (33) SXH5 ) that has a VRF running for our guest network. On this 6500 resides the DHCP pool with a range defined for our guest network. We have a stack of 3750's (12.2 (46) SE) connected to the 6500 with a L3 connection. The 3750's have a local guest VLAN with its gateway defined in a VLAN interface. This VLAN on the 3750 has an IP helper address pointing to an IP within the VRF on the 6500. When debugging DHCP on the 6500, a request is received and sent back out. The client never receives this request.
If a static IP is applied, the client is able to communicate anywhere within the VRF successfully (including pinging the IP within the helper-address. As many posts have pointed out - there is no VRF <name> under the ip dhcp pool <name> within the 6500. I am just wondering if anyone else has run into this and what their solution was.
Thanks.

Hi,
I have tested the dhcp server and vrf on Cisco 3640 and it is working without VRF under the ip dhcp pool. Please ensure that you have configured routing for the dhcp-relay agent(VLAN facing dhcp client on 3750 in your case).

Using X3500 as a Wireless Extender DHCP issue iPhone 6

Hi
Hopefully a simple question with a simple answer.
Background:
I've transitioned away from my ADSL ISP to a cable provider (VirginMedia). My new ISP comes with a cable modem (SuperHub 2 ac) and I've connected the two devices together to extend my home wireless network. The cable modem is The two routers are physically remote from each other - connected via just their Ethernet ports - via power-line technology (Devolo dLAN 1200+). The two routers have the same broadcast SSID albeit on separate channels.
Issue:
All devices in my house, laptops tablets, phones roam between the two wi-fi zones seamlessly *except* the iPhone 6 (iOS8.1), this works on the cable modem wi-fi - but not on the X3500 wi-fi. I also have an iPad Mini 2 (also iOS8.1) which also works - so rightly / wrongly I've ruled out iO8.1 as the issue. Oddly the iPhone 6 connects to the x3500 but doesn't obtain an IP address (the cable modem is the DHCP server). Even setting a static IP address doesn't help.
Observation(s):
If the X3500 is setup as a DHCP server, the iPhoen connects (and gets an IP address), but then the default gateway is incorrect (gatway is the IP address of the X3500 not the remote cable modem). I can't find anywhere to specify a default gateway in the setup.
Question
I'm beginning to think this is an issue with the iPhone 6 (knowing all other devices work correctly), but I just want to make sure I'm configuring the X3500 correctly. I'm specifically interested in the whether I'm using the right "Mode"ADSL / Ethernet. I've tried "Bridged Mode Only" (ADSL) and "Automatic DCHP Only" (Ethernet) but neither seem to resolve the issue that the iPhone 6 is having.
any suggestions on how to resolve / troubleshoot would be most welcomed.
Thanks!
Solved!
Go to Solution.

Yes, there's a way for you to override the IP Address. It is on Router Address under Network Setup on the Basic Setup tab. If I'm not mistaken, one end of the Ethernet cable should be connected to the regular Ethernet port of the cable modem and the other end to the cable port of the X3500.
But if it's just the iPhone that won't connect to the X3500, it might be okay to retain the current configuration of the router, but try adjusting the wireless security mode or set the wireless channel to 11 and observe what happens.

WVC200 DHCP issue (LAN vs Wireless

Hi All,
I have a WRT600N router from Linksys and bought a second WVC200 camera.
While setting up the first camera I had some trouble during set up (now I have the same issue with the second one).
During installation of the first camera while on the ethernet hookup as instructed the DHCP assigned a specifc IP (192.168.1.107). After succesfully finishing the initial set up I detached power and the ethernet and hooked up power alone again to switch to a wireless connection.
For whatever reason the router assigned a different IP (192.168.1.115) or so I thought....
After tinkering for a while I upgraded the Firmware to the last version and the wireless conection suddenly worked (the IP did not change).
Now to the second camera.
Did the same thing but somehow after the upgrade the IP still doesn't remain the same (despite DHCP reservation). Still falls back to the 192.168.1.115.
What I realised after checking the router is that the router doesn't recognize the wlan connection for whatever reason. I do WPA TKIP and it works just fine with the other wireless equipment. I also switched off and on the wireless MAC Filter and added the MAC address of the second camera with the right IP (192.168.1.108) in the DHCP reservation list as a device (same in the wireless filter list). I also checked the MAC address at least 10 times....
What else can I do to trick the router in finding the camera and assigning the right IP address or is the wireless connection just broken?
Thx for any help.
Malte
Message Edited by Malte on 08-18-2008 03:14 PM

I have the exact same problem! I have a WVC200 since a couple of years. It have served well but for a while ago it stopped to work properly. I didn't do anything about it right away but today I thought I should set it right.
I did a firmware upgrade, reseted the camera and started all over with the settings. At first I had a TP-cable in it. My router is a Zonet ZSR0140CP that also acts DHCPserver. I have told the DHCP that the MAC-adress of the camera should have a specific IP-adress. In the camera I have set that it should get a IP-adress from DHCP. I have a D-Link DWL-900AP+ that acts wireless AP. It is WEP Encryption with 64 bit HEX. And it doesn't act as a DHCPserver, it's just an AP
Everything went fine until I broke the electricity to the camera unplugged the TP-cable and plugged the elecricity in again.
For a long while it just serched an IP-adress and when it got one it was 192.168.1.115! Thats not much right in that ip adress... Wherever did it got that from??
Please don't tell me to reset everything. I have already done that. And I still have the same problem. I dont think it is the router/switch/AP who is the problem here.
//Camilla

Extending Wireless Network - DHCP Issues

I have an Airport Extreme 802.11n and I want to extend the range of it with my Airport Express 802.11n. I found the "Designing Airport Networks Using Airport Utility" from the Apple support page. "Extending the Range of an 802.11n Network" on page 46 says to manually set up. Under "wireless" when I check the box to "Allow this network to be extended" I get a dialog box that says, Correct the 2 problems below before updating this Apple device. Those problems are DHCP Beginning Address 10.0.1.2 and DHCP Ending Address 10.0.1.200. The Airport Extreme has the IP Address of 10.0.1.33. It says the DHCP range you have entered conflicts with the WAN IP address of your wireless device. If I limit the beginning address to start at 10.0.1.34 should that solve my issue? Any help is appreciated.
Thank You!

Sorry but I should have read your original post closer.
Since you already have a router distributing IP addresses, you don't need the AEBS doing that. Configure your AEBS so that it is acting as a bridge (not sharing a single IP address).

Macbook Air (Mid 2011) Wired/Wireless DHCP issues

All,
I have been attempting to fix a nagging problem with my brand new MBA 'Ultimate' - while at home it connects fine wirelessly and I do not experience any issues (note this is the first SSID it has ever connected to) I have not been able to connect to my office's wireless - I do not pull a DHCP address or connect. In an attempt to rule out the wireless issues everyone has, I purchased the 10/100 Apple RJ-45 (ethernet) adapter and have attempted this morning to connect via a known working patch cable.
The wired connection fails to pull a DHCP address as well!
I have followed wifiguru's posts and attempted to disable the firewall, reset the SMC, reset the PRAM, delete the offending plists, changed the network order, etc.
I do not believe my issue lies on my computer network as multiple other iOS and OSX devices can connect (that are Lion as well)
Admittedly, I have not attempted to go to another third party wireless location (Starbucks, McD's, etc) but for the wired connection to fail as well and my home wireless (802.11n) connection to work leads me to think I am missing something. I do not believe I should have to reboot my work's wireless router to accept me as a client as well - especially since the wired does not connect.
Any thoughts?
Cliffs:
- mid-2011 MBA Ultimate
- wireless works at home network (802.11n) - gets DHCP address
- wireless doesn't work at work (802.11b/g) - no DHCP address
- wired doesn't work at work (apple adapter) - no DHCP address
- firewall off/on doesn't matter
- deleted problematic plists, no change
I also feel I should add, I'm not computer illiterate by any stretch of the imagination and have used OSX products in the past.

Really?
No input at all?

2100 wireless LAN controller intermittant DHCP issue does not respond to clients

Hi everyone,
I have been struggling with a difficult problem for some time now:
The cisco 2100 wlan controller I have is configured with a dhcp scope in the same ip address range as its WLAN. The configuration works and on a good day I have up to 200 clients connecting with out issue. In the web interface they display as associated and authenticated
On a bad day I find I will begin seeing about 50-80% of all new devices that attempt to join the WLAN show up as associated but not authenticated. These clients end up self assigning themselves a 169.254.0.0/16 (APIPA) address
When my controller / WLAN enters into this state: if clients leave the WLAN they typically fail to get back on and successfully authenticate. By the end of a day around 80-90% of all devices are essentially without Internet access due to this issue.
Rebooting the controller and or APs typically makes no difference or makes things worse – although sometimes it appears to resolve the issue. The same holds for disabling the entire wlan for about 10 minutes and then re enabling it.
Im using 1130 cisco aironet APs with the controller. I have checked extensively for interference and congestion – I think I have congestion – some APs typically host 40 to 90 devices. However as mentioned on a good day the wlan will host 200 devices all day without any issue and some APs will host 50 to 70 devices without major issue.
I can provide more specifics if anyone should need – eg firmware, IP addresses, exact model numbers etc.
Please let me know if anyone has seen something like this before ?
I believe the 2100 is rated to handle up to 350 devices and its recommended not to load a 1130 AP with more than 25 devices ??
Regards
Matthew

Hi Amijad, Hi George:
Thank you both for your time in considering my situation.
I will think about implementing an independant DHCP server; im really wondering if the equipment is just overloaded
- What software versoin the WLC uses?
Product Version.................................. 6.0.199.4
RTOS Version..................................... 6.0.199.4
Bootloader Version............................... 4.0.191.0
Emergency Image Version.......................... 6.0.199.4
PID: AIR-WLC2106-K9, VID: V05
- What ports of the WLC are connected to the neighbor swtich? one or more?
2 ports connect to the neighbor switch on separate vlans
- port 1 is vlan 0 and hosts the management and ap-management IPs for the wlan controller
- port 2 is vlan 1 and hosts the wlan
- the controller has one dhcp scope defined on port 2 for the WLAN
- What is the security of your WLAN?
WPA+WPA2
AES
PSK
- Do you have "DHCP required" enabled on the WLAN?
yes DHCP required is enabled in the WLAN
please let me know if you have any additional advice.
regards
Matthew

Wireless Guest Users DHCP issue

Dear all
We have 2 wism as well as Anchor controller
Guest users are getting ip address from anchor controller.
We had created DHCP scope on anchor controller itself.
We had opened particular ports to communicate between guest controller and inside controller for EOIP tunneling to take place.
Issue is that some times user is getting IP address in the range of AP management vlan.
Do we require to open ports for bootpc and bootps as well or do we need to create dhcp scope in the switch.
If any one has faced the above issue pls reply me at the earliest.
Regards
-Danish

If the anchor goes down, or mobility fails, the user should never egress from the Foreign WLC (in my opinion). However, if you are saying that the user gets an IP from the MGMT Interface of the Foreign WLC (not the Anchor), then it is doing exactly what it shouldn't.
What version of code is this?
I've seen a lot of deployments implement a "dummy interface" on the Foreign WLC. So a fake vlan/subnet is created on the WLC and mapped as the default interface for the Foreign's Guest WLAN. In the event anchoring does fail and the client sticks to the foreign WLC this dummy interface would actually prevent the user from having network access.
Are you seeing this often?

DHCP issues on wireless

Similar Messages

Maybe you are looking for