Re: AP cant get DHCP address

Hey all, I'm hoping someone can help with a problem I am having with a AIRONET 1130AG Access point.
I have installed quite a few of these but this one has me baffeled. Now, I'm not a CCNA or anything like that.
I set up using the GUI; I use a simple WPA.
My devices connect with "Limited or no Connectivity" If I hard code an address, devices work fine. If I attach them to the switch, they obtain an address on the nic AND the Wirless connections.
If i check the AP, it shows my devices, but no IP. Under the log, the last entry say "interface Dot11Radio0, Deauthenticating Station (mac address) reason: Previous authentication no longer valid"
Any advice is greatly appreciated.
Thanks,
John

Should the command to enter the radius-server command be :-
radius-server host 204.100.100.100 auth-port 1812 acct-port 1813 key 0 fHKrJ6U26DQuw5yb ?
Add the number 0 to make it not encrypted ? But what is the reason for this to happen in the first place ?
- InternetB -

Similar Messages

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.

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

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...??!?!!!

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

Airport can no longer get DHCP address

Hello,
I'm at the point of dumping the airport base station in the trash, but thought I would try this first.
I have broadband internet service. It worked - until mid morning today. Suddenly it will not work. The base station (old one, white - snow?), though set for DHCP, now defaults to a self-addressed 169... address. I have tried:
- powering off the base station, the cable modem, powering up one at a time, etc etc. Internet provider (insight, IL) says they don't know why the apple base station is unable to renew the DHCP lease.
- The Airport Admin Utility is set to Ethernet, using DHCP. There is no "renew DHCP lease" button there, but I have switched it to connect using modem and then switched backed to Ethernet, hit Update, and back comes Using DHCP ... with a 169.254 address.
- I can connect through the cable modem with my powerbook without a problem. The address starts with 74.134.
I take it the self-assigned IP means there was a timeout or the airport was otherwise unable to get what it considered a valid IP.
Is the base station toast?
Should I buy a router and hook it to that? Seems redundant, with my setup (two laptops, one desktop connected to base station LAN port)
I've spent several hours reading (via direct connect to the cable modem) and trying different wiring / reset combinations, and have about had it. Any thoughts most welcome.
Thanks,
Brian

It is a long while since I tried Google Toolbar, I am not sure what it changes. But I would not expect it to totally remove your options to use the ordinary toolbars.
■ Try
* press the''' alt '''key on the keyboard, that may return the menu bar
* once you have the menubar '''View -> Toolbars ->''' and select which you need
* you may also use View-> Toolbars -> Customise and drag items back or use the restore default set option.
* right clicking on the toolbars also gets you to the customise and show toolbars options
■ have a look at [[Back and forward or other toolbar items are missing]]
PS
I hope you do not need to resort to editing registry settings, the firefox 'dragons' in prefs are user friendly compared with Windows registry. Messing up firefox prefs only really affects firefox normally; whereas errors in a registry edit may prevent you from even booting the computer.

One at a time - 1st iPhone gets DHCP address, 2nd iPhone gets a 169

We have a windows 2003 server as a DHCP server, it gives out a proper address to the first iPhone connecting to the network over wireless but then any other iPhones just get the 169.x.x.x address (which I know is a self configured address).
If the 1st phone disconnects then the next phone will get on and the 1st phone can't get back on. Also tried using a router to do the dhcp and the same thing happens. It looks to be because the name of the device as far as the dhcp server is concerned is "iPhone" even though the names of the phones are different. Both phones are running the latest 2.2.1 software, I did have a look and can see a few issues with dhcp posted but all un-answered.

Yep, both phones have had network settings reset, server has been rebooted and latest firmware on router. Thanks for the article, it is what I would do if the phone couldn't get an IP at all, seems strange that they can both get an IP address no problem when the other phone isn't around.

Mac mini server refuses to get DHCP address from router

Everything was going along fine. But after a power outage the server goes to a 169. address when the router puts out 198. addresses. If I put a static 198. address in it sees the network but won't connect to the internet. I've flashed the router (everything else sees the router fine, 3 computers and a time capsule). I've had the hardware checked at the Apple store - it picked up an address right away. After narrowing everything down the problem has to be in the operating system. I even did a full time machine restore to the day before the storm. No luck. Anyone heard of this problem.

Mauricette has a point.
A server function is not designed to accept a floating or dynamic IP address. If that is the case, how do you create firewall rules that prevent those unnnecessary ports being left opened from being attacked by rogue machines in Romania and China on a hourly basis when you announce to the world that your server is available if the server IP address keep changing due to the DHCP lease change? Yes, they do have bots that do this VERY EFFICIENTLY!
By changing the very nature of your firewall rules by working with DHCP, you are opening ports you do not know to accommodate DHCP dynamic addressing, which was the reason why your Mac Mini Server stopped working in the first place. It's ok for a client, since a client isn't serving any files to any one right.
By using client based firewall rules, you are exposing your server to attacks and when they get through your Mini server, which they can if they are persistent, they get into your home network and then whatever file server services you have opened and unprotected at the time WILL BE copied by these people easily.
I have a client once who did just that. She was attacked, the hacker went through her network like a rampaging bull. They were from China. My Synology RAID server gets this attack all the time, but I have a well establish IDS system and the Synology RAID has logs that tracks attacks.
For a server setup. Use static IP and then build a strong firewall around it and protect it and never compromise.
Recently, I just noticed someone somehow hacked and broke my WPA-PSK AES passkey for one of my Wireless N network router. It was not set up with a strong password though, but thankgod I had a firewall around that so my internal networks were safe. So this teaches you that if someone wants in bad, they will get in.
Hope this helps.

Clients are unable to get DHCP Addresses

Hi, I have a setup where managment interface is in different vlan, ap-manager is in different vlan, APs are in different vlan and the clients are on their own vlans respectively. Everything works except for when I try to associate a client to an ap on the floor. It doesn't get an IP address..Here is a debug of DHCP on the controller.
any help would be greatly apreciated...

I got it to work, I had to create seperate AP groups and virtual interface for each client vlan and point it to the DHCP server.

SPA525G Won't get DHCP Address

So I have a couple of brand new SPA525Gs right out of the box and we are having trouble with them on the network.
I've setup a sniffer capture to see what's happening and it looks like the phone sends out a dhcp request but never accepts the offer from the switch.
I then setup a static IP address on the same subnet and it will not respond to the ARP requests either.
If I connect it back to back with my laptop, however I can ping it and get to the web interface fine.
Other older 504 and 525 phones are all working fine on this same subnet and switch port.
The phones came with version 7.5.2a and we upgraded them to 7.5.5 still does the same thing.
Has anyone else seen this? Small business support didn't offer up much help.

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!!!

Can't get dhcp address.. even if I do a -dhcp in my settings.txt

Ok odd problem. I have already tried the Jan 2010 update to see if it
fixes, no go.
I'm imaging an HP Elitebook 8530w.. I've already done these without issue.
I select maintenance mode imaging and I get the Linux splash screen and
it sits there. If I hit escape to see the console it's got
Sending DHCP Request to eth0...
ctrl-alt-f3 shows scrolling errors of
err, eth0: ARPOP_REPLY received from 192.168.11.98 (mac address here)
In my settings.txt I made the following change
netsetup=-dhcp,now,all
Then I gave it a static ip with the hostip, netmask and gateway commands.
Not my preferred route but I'm on a deadline.
No effect. It's still sending dhcp server requests. I stopped and
started the imaging server as well.
Why is it still trying to do a dhcp request when I have -dhcp in there?

Originally Posted by grimlock
On 2/2/2010 12:45 PM, Patrick Farrell wrote:
> Ok odd problem. I have already tried the Jan 2010 update to see if it
> fixes, no go.
>
> I'm imaging an HP Elitebook 8530w.. I've already done these without issue.
>
> I select maintenance mode imaging and I get the Linux splash screen and
> it sits there. If I hit escape to see the console it's got
>
> Sending DHCP Request to eth0...
>
> ctrl-alt-f3 shows scrolling errors of
>
> err, eth0: ARPOP_REPLY received from 192.168.11.98 (mac address here)
>
> In my settings.txt I made the following change
>
> netsetup=-dhcp,now,all
>
> Then I gave it a static ip with the hostip, netmask and gateway commands.
>
> Not my preferred route but I'm on a deadline.
>
> No effect. It's still sending dhcp server requests. I stopped and
> started the imaging server as well.
>
> Why is it still trying to do a dhcp request when I have -dhcp in there?
FYI I just ran into this again, and I remembered I had posted about it
earlier. Sweet I thought I will just look up the solution. Well there
was none posted. As I've grown older and wiser since I originally
posted this I figured out what it was.
It's an IP Address conflict. Whatever device is the culprit this time
isn't pingable, but the mac address listed on the error line is not the
mac address of the machine you are imaging but rather of the offender.
I didn't pick up on that last time around. For whatever reason it
didn't have anything in dhcp console for this address so it kept giving
it out again. As a temp workaround I assigned a manual bogus mac to
that IP address it was receiving to prevent any devices from being
assigned to it (because it's already in use). After a few days when
leases expire, I'll delete that entry. It's possible that some brain
child manually assigned an IP to their machine. I'll have to track it
down later.
I have the same problem, and your solution worked perfectly. Thanks for this as you have saved me a lot of time in troubleshooting!

Re: AP cant get DHCP address

Similar Messages

Maybe you are looking for