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.

Similar Messages

Bizarre WiFi Connectivity Issue; Self-Assigned IPs, Static IP Doesn't work

The short and sweet of the problem: Macs/Apple Devices are pulling self-assigned IP addresses when connecting to a Linksys EA6900/AC1900 router.
Here’s the detail: I am working at an office with 1 Airport Extreme and 1 Linksys EA6900/AC1900, both are configured for Bridge Mode and both use WPA. DHCP is being handled by a Watchguard XTM5 series firewall.
When Macs (and often iPhones) connect to the Linksys (on 2.4 or 5Ghz) they get a self-assigned IP address. If you enter a manual address you still do not have any connectivity. However, if you connect to the Extreme you will instantly get an IP address, and if you switch to the Linksys your DHCP address will carry over and you will retain connectivity. This problem does not happen to the Windows machines in the office- they all connect to all base stations without any issue. Total users on the network range from 5 to 20 WiFi users at any given time plus and AppleTV (also affected).
More info: When there are between 5-10 people in the conference room for a morning meeting the Macs will all revert to self-assigned addresses (even if they were working before). The workaround has been to connect to the Extreme, but there are occasions when this occurs that the Extreme will also not seem to pass the DHCP addresses from the firewall; addresses become self-assigned and you lose all internet. To make matters more odd, this behavior seems to really only affect the network during business hours; after hours the Linksys works pretty much normally and any device can connect without issue.
Things I’ve done: Run Wireshark and located a number of rogue devices that were handing out overlapping DHCP addresses. Identified machines that were ARP storming and removed them. Expanded the DHCP pool so that we aren’t running out of addresses and confirmed that we had enough by checking the logs.
More things I’ve done: Used Netspot to check signal strength and channel overlap and isolation. I have mapped the signal strength by location and we have strong signals to the various locations (the Linksys AP is 7 feet from the conference room). I have checked that the firmware is the most recent version.
I can’t find any logical reason for the Macs (and pretty much only the Macs/Apple devices) to not be picking up DHCP info through the bridge mode devices. I would tell them to get another Extreme but they are going to be deploying a Cisco Meraki system soon and I suspect that this problem will persist since the Linksys was put in place because the last AP displayed the same behavior with the Macs picking up self-assigned IPs. Affected Macs range from 2010 era MBP and Air to 2013 MBP and Air and they are running OSX 10.8 through 10.10.
As for the history of this network, I just walked into this company and know very little about how well it worked before, but apparently it has always been flaky according to the staff.

I agree that something isn't right; I am going to cut over DHCP services from the Watchguard to the newly deployed OS X Server tonight and see if that changes anything.
On the other hand, faulty DHCP server/client settings doesn't explain why applying a static IP still leaves you with no connectivity. I think that clue is also fairly important but I can't figure out what would be blocking connectivity on a static IP setup.

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!

Network connection fails with a "self assigned IP" or "no IP" msg displayed

I am having problems staying connected to the wireless network. I have four Macs - 3 MBPros and 1 iMac. They have all been upgraded to Snow Leopard and have had all recent updates from Apple.
One of the MBP, and just now the iMac, keeps disconnecting from the wireless network with a message that the IP address has been self assigned or that no IP address is found. These computers cannot connect right now but I am using another MBP and it is connected.
I've read through the forums and these are the solutions I have tried:
1. reset everything - the router, WAP, and the computers - this sometimes works and sometimes does not.
2. renewed my DHCP lease - at first this worked like a charm but now it makes no difference
All computers are using Airport Extreme
Router is Motorola, new last year
WAP is a Linksys Dual N band new last month (thinking that maybe the Netgear g was failing)
There are two PCs connected to the same WAP and they are (strangely) working fine.
How can I get these computers to just stay connected?

Since upgrading to Snow Leopard, I'm having the same type of problem and I have to reset my airport exterme because of NO I/P address. I would really like to find out what's up/ Until the Upgrade there wan NEVER a Problem - which is what I expect from MAC!

EA6500 Version 2 router wireless self assigned IP address

Since installing the router replacing a version 1, I am having problem connecting to the internet on several of my machines, ie. 2012 MacBook Pro. Checking under the network wireless it show wireless as self assinged IP address and no internet connection. I checked the router an all setting look good. Network people are telling me it is a router issue with DHCP. Can someone please give me some help on fixing this issue. Connecting to the internet wirelessly should be effortless. This router has certainly been problematic. Ideas, help.

You have to start over.
1. Unplug your ISP modem from electrical outlet for 20 minutes.
2. Reset EA6500 to factory defaults.
3. Now try.
4. Make sure you give the 2.4 Ghz and 5 ghz unique/different SSIDs. Use something that you've never used before. Don't use previous SSIDs. You can also remove your old wireless profile.
5. For the 2.4 ghz radio, us "20 MHz only" and use inSSIDer to help you find best channel.

Apple Mac wireless self-assigned IP address help

I just got FiOS today. Everything appears to be working fine except for one thing, my Apple Macbook Pro, running 10.5.8 is getting a self-assigned IP address when I connect it to my FiOS wireless router (ActionTec MI424-WR).
The Mac has a physical connection to the wireless router. The "My Network" tab in the wireless router configuration screen shows it as connected, with an assigned IP address of 192.168.1.6. However, the ping test fails, and the Mac's Airport settings show a self-assigned IP address.
I've tried rebooting everything, turning airport on and off, and renewing DHCP, but nothing is working.
I haven't touched any of the default settings on the ActionTec, it's still running WEP.
I did verify that my firewall is turned off on the mac.
What else can I try?
Solved!
Go to Solution.

I have a 6 month old MacBook Pro running the latest version of OS X, so it's affecting newere Macs as well. I found some on-line discussion that it's a problem with only the Macbook Pro.
FWIW, a few hours after finally getting it working it happened all over again. I had wireless connectivity but only got a self-assigned IP address. I tried shutting the airport on and off, deleting the wireless key from key chain, and clearing the wireless network. However nothing worked until I rebooted the Mac.
I then checked the firmware on the ActionTec and found it was 20.8.0 and 20.9.0 was the latest (mind you I just got this router installed today). I updated to the 20.9.0 release and everything has worked for about the last 6 hours. Fingers are crossed. :-)

Frustrated with apple self assigned IP (ethernet)

Hi,
I have ethernet self assigned IP problem. Can anyone help ?

If the computer is connected through a switch to a cable or DSL modem, and the modem is not acting as a router, then only the first device to connect will get an address. You need to change the configuration of the modem so that it shares its Internet connection with all devices on the local network, or else connect a router.
If there are other devices on the same network, and none of them can get an address, then the problem is on the DHCP server (most likely, the router.) If other devices are working normally, or if there are no others, see below.
Open the Network pane in System Preferences and make a note of your settings in the Ethernet service. It may be helpful to take screenshots of the various tabs in the preference pane.
If the preference pane is locked, unlock it by clicking the padlock icon and entering your administrator password.
From the Location menu at the top of the window, select Edit Locations. A sheet will drop down. Click the plus-sign button to create a new location. Give it any name you want. In the new location, set up the Ethernet service with the same settings you used before. Click Apply and test.

Sharing Airport connection with Ethernet - Self Assigned IP

WHy is the ethernet port getting a self assigned IP Address. I want to share the wifi connection with the ethernet to run a cable to my ps3. Need to update trophies so i can wipe it. Wifi doesnt work on PS3 at this time(reason for wiping)

This is a major debacle with Apple. I contacted support and they informed me that they don't support this function.
After many hours of playing around and reading forums this is quite easy (once you know what to do)!
Setup internet sharing (airpor to ethernet)
Go to Network under system preferences
View the Ethernet icon (should be yellow as it self assigns the IP)
Click on TCP/IP and in the Configure IPv4 menu, select "Using DHCP with manual address"
Set the Ethernets IP address to 192.168.2.1
Set the Subnet Mask to 255.255.255.0 (255.255.0.0 is default on OSX 10.6)
On the NIC tring to use the shared connection (PS3/XBOX/Network DVD/PC), you should just be able to "Obtain IP and DNS Automatically". If not, enter the following:
IP Address(connecting device): 192.168.2.2
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.2.1
This has nothing to do with the IP of the airport connection or your router, this is the internal Ethernet port settings on the hardware (as far as I can tell).
My internal Airport IP is 10.0.1.4, with 10.0.1.1 for airport extreme, and the self assigned IP was 169.254.151.92 on my shared Ethernet port on the Mac when it wasn't configured properly.
Let me know if this works!!!

Issue with Wireless AP.

Hi All,
Greetings.
we have an issue with user who says that he is unable to connect to AP and he need to re-boot it everytime to re-connect to it.
But when i check from WLC all the AP uptime is more than 150 days and the AP associate time of respective AP's is also more than 150 days.we are using cisco AIR-CT2504-K9 wlc and all the AP's are connected to Cisco 3750X and cisco4510R+E.please suggest.
pasting logs from wlc below.
Tue Feb 26 17:06:05 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 207) for client 88:53:95:7b:8f:56 / user 'unknown'
1 Tue Feb 26 17:06:05 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
2 Tue Feb 26 17:06:05 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
3 Tue Feb 26 17:06:05 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 206) for client 60:c5:47:44:4d:d7 / user 'unknown'
4 Tue Feb 26 17:06:05 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 191) for client 88:53:95:7b:8f:56 / user 'unknown'
5 Tue Feb 26 17:06:05 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
6 Tue Feb 26 17:06:05 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
7 Tue Feb 26 17:06:05 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 190) for client 60:c5:47:44:4d:d7 / user 'unknown'
8 Tue Feb 26 16:51:24 2013 User guest logged Out. Client MAC:8c:a9:82:ae:a2:4a, Client IP:10.40.101.33, AP MAC:0c:85:25:c7:dc:e0, AP Name:NTW100-AP07
9 Tue Feb 26 16:45:16 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
10 Tue Feb 26 16:45:16 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
11 Tue Feb 26 16:45:16 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 44) for client 10:40:f3:5e:3b:26 / user 'unknown'
12 Tue Feb 26 16:45:16 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
13 Tue Feb 26 16:45:16 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
14 Tue Feb 26 16:45:16 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 204) for client 10:40:f3:5e:3b:26 / user 'unknown'
15 Tue Feb 26 16:05:29 2013 RADIUS server 10.12.2.34:1813 activated in global list
16 Tue Feb 26 16:05:29 2013 RADIUS server 10.12.2.33:1813 deactivated in global list
17 Tue Feb 26 16:05:29 2013 RADIUS server 10.12.2.33:1813 deactivated in global list
18 Tue Feb 26 16:05:29 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 113) for client b8:c7:5d:e0:48:be / user 'unknown'
19 Tue Feb 26 16:05:29 2013 RADIUS server 10.12.2.33:1813 activated in global list
20 Tue Feb 26 16:05:29 2013 RADIUS server 10.19.3.104:1813 deactivated in global list
21 Tue Feb 26 16:05:29 2013 RADIUS server 10.19.3.104:1813 deactivated in global list
22 Tue Feb 26 16:05:29 2013 RADIUS server 10.19.3.104:1813 failed to respond to request (ID 132) for client b8:c7:5d:e0:48:be / user 'unknown'
23 Tue Feb 26 16:05:17 2013 User guest logged Out. Client MAC:00:22:fa:95:d2:58, Client IP:10.40.101.69, AP MAC:0c:85:25:c7:dc:e0, AP Name:NTW100-AP07
24 Tue Feb 26 15:42:36 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
25 Tue Feb 26 15:42:36 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
26 Tue Feb 26 15:42:36 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 111) for client 7c:c5:37:18:ca:2b / user 'unknown'
27 Tue Feb 26 15:35:53 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 247) for client 68:a8:6d:e9:7d:36 / user 'unknown'
28 Tue Feb 26 15:35:53 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
29 Tue Feb 26 15:35:53 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
30 Tue Feb 26 15:35:53 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 246) for client 68:a8:6d:e9:7d:36 / user 'unknown'
31 Tue Feb 26 15:35:53 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 137) for client 68:a8:6d:e9:7d:36 / user 'unknown'
32 Tue Feb 26 15:35:53 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
33 Tue Feb 26 15:35:53 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
34 Tue Feb 26 15:35:53 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 136) for client 68:a8:6d:e9:7d:36 / user 'unknown'
35 Tue Feb 26 15:06:17 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
36 Tue Feb 26 15:06:17 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
37 Tue Feb 26 15:06:17 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 67) for client 24:ab:81:af:2f:da / user 'unknown'
38 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
39 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
40 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 245) for client b8:17:c2:49:d5:37 / user 'unknown'
41 Tue Feb 26 14:49:54 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 229) for client c0:9f:42:65:37:af / user 'unknown'
42 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
43 Tue Feb 26 14:49:54 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
44 Tue Feb 26 14:49:54 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 230) for client 60:fa:cd:b6:f6:d6 / user 'unknown'
45 Tue Feb 26 14:49:54 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
46 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
47 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 228) for client b8:17:c2:49:d5:37 / user 'unknown'
48 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 243) for client c0:9f:42:65:37:af / user 'unknown'
49 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
50 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
51 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 242) for client 60:fa:cd:b6:f6:d6 / user 'unknown'
52 Tue Feb 26 14:14:41 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 227) for client 0c:77:1a:a7:97:6e / user 'unknown'
53 Tue Feb 26 14:14:41 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
54 Tue Feb 26 14:14:41 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
55 Tue Feb 26 14:14:41 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 226) for client 0c:77:1a:a7:97:6e / user 'unknown'
56 Tue Feb 26 14:14:41 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 226) for client 0c:77:1a:a7:97:6e / user 'unknown'
57 Tue Feb 26 14:14:41 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
58 Tue Feb 26 14:14:41 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
59 Tue Feb 26 14:14:41 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 225) for client 0c:77:1a:a7:97:6e / user 'unknown'
60 Tue Feb 26 14:13:57 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
61 Tue Feb 26 14:13:57 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
62 Tue Feb 26 14:13:57 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 34) for client ec:85:2f:a2:4d:ba / user 'unknown'
63 Tue Feb 26 14:13:57 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
64 Tue Feb 26 14:13:57 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
65 Tue Feb 26 14:13:57 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 225) for client ec:85:2f:a2:4d:ba / user 'unknown'
66 Tue Feb 26 13:22:55 2013 Radar signals have been cleared on channel 52 by 802.11a radio with MAC: 00:1f:ca:cc:f0:00 and slot 1
67 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 214) for client e8:8d:28:7f:0e:5a / user 'unknown'
68 Tue Feb 26 13:20:02 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
69 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
70 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 213) for client e8:8d:28:7f:0e:5a / user 'unknown'
71 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 33) for client e8:8d:28:7f:0e:5a / user 'unknown'
72 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
73 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
74 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 32) for client e8:8d:28:7f:0e:5a / user 'unknown'
75 Tue Feb 26 12:52:55 2013 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1f:ca:cc:f0:00 Cause=Radio channel set. Status:NA
76 Tue Feb 26 12:52:54 2013 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1f:ca:cc:f0:00 Cause=Radio channel set. Status:NA
77 Tue Feb 26 12:52:54 2013 Radar signals have been detected on channel 52 by 802.11a radio with MAC: 00:1f:ca:cc:f0:00 and slot 1
78 Tue Feb 26 12:48:34 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 164) for client 7c:c5:37:18:ca:2b / user 'unknown'
79 Tue Feb 26 12:48:34 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
80 Tue Feb 26 12:48:34 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
81 Tue Feb 26 12:48:34 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 163) for client 7c:c5:37:18:ca:2b / user 'unknown'
82 Tue Feb 26 12:48:34 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 212) for client 7c:c5:37:18:ca:2b / user 'unknown'
83 Tue Feb 26 12:48:34 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
84 Tue Feb 26 12:48:34 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
85 Tue Feb 26 12:48:34 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 211) for client 7c:c5:37:18:ca:2b / user 'unknown'
86 Tue Feb 26 12:45:09 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2019, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 161, Cluster ID: 1c:75:a0:02:41:22, Previous Cluster ID: 1c:75:a0:02:41:22, Event: Clear
87 Tue Feb 26 12:42:07 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2019, Type: WiFi Invalid Channel[31], Severity: 3, Channels: 161, Cluster ID: 1c:75:a0:02:41:22, Previous Cluster ID: 1c:75:a0:02:41:22, Event: Set
88 Tue Feb 26 12:41:25 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2018, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 161, Cluster ID: 1c:75:a0:02:41:22, Previous Cluster ID: 1c:75:a0:02:41:22, Event: Clear
89 Tue Feb 26 12:37:38 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2018, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 161, Cluster ID: 1c:75:a0:02:41:22, Previous Cluster ID: 1c:75:a0:02:41:22, Event: Set
90 Tue Feb 26 12:35:47 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2017, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 161, Cluster ID: 1c:75:a0:02:41:01, Previous Cluster ID: 1c:75:a0:02:41:01, Event: Clear
91 Tue Feb 26 12:20:01 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 115) for client e8:8d:28:7f:0e:5a / user 'unknown'
92 Tue Feb 26 12:20:01 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
93 Tue Feb 26 12:20:01 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
94 Tue Feb 26 12:20:01 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 114) for client e8:8d:28:7f:0e:5a / user 'unknown'
95 Tue Feb 26 12:20:01 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 162) for client e8:8d:28:7f:0e:5a / user 'unknown'
96 Tue Feb 26 12:20:01 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
97 Tue Feb 26 12:20:01 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
98 Tue Feb 26 12:20:01 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 161) for client e8:8d:28:7f:0e:5a / user 'unknown'
99 Tue Feb 26 12:18:26 2013 User inventiv-guest logged in. Client MAC:8c:a9:82:ae:a2:4a, Client IP:10.40.101.33, AP MAC:0c:85:25:c7:dc:e0, AP Name:NTW100-AP07
100 Tue Feb 26 12:11:01 2013 RADIUS server 10.12.50.52:1813 failed to respond to request (ID 106) for client a4:67:06:dd:ed:6a / user 'unknown'
101 Tue Feb 26 12:11:01 2013 RADIUS server 10.19.3.104:1813 activated in global list
102 Tue Feb 26 12:11:01 2013 RADIUS server 10.12.50.52:1813 deactivated in global list
103 Tue Feb 26 12:11:01 2013 RADIUS server 10.12.50.52:1813 deactivated in global list
104 Tue Feb 26 12:11:01 2013 RADIUS server 10.12.50.52:1813 failed to respond to request (ID 105) for client a4:67:06:dd:ed:6a / user 'unknown'
105 Tue Feb 26 12:11:01 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 108) for client a4:67:06:dd:ed:6a / user 'unknown'
106 Tue Feb 26 12:11:01 2013 RADIUS server 10.12.50.52:1813 activated in global list
107 Tue Feb 26 12:11:01 2013 RADIUS server 10.19.3.108:1813 deactivated in global list
108 Tue Feb 26 12:11:01 2013 RADIUS server 10.19.3.108:1813 deactivated in global list
109 Tue Feb 26 12:11:01 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 107) for client a4:67:06:dd:ed:6a / user 'unknown'
110 Tue Feb 26 12:10:12 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2017, Type: WiFi Invalid Channel[31], Severity: 0, Channels: 161, Cluster ID: 1c:75:a0:02:41:01, Previous Cluster ID: 1c:75:a0:02:41:01, Event: Set
111 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 68) for client 28:e0:2c:38:64:b3 / user 'unknown'
112 Tue Feb 26 11:45:29 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
113 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
114 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 67) for client 28:e0:2c:38:64:b3 / user 'unknown'
115 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 113) for client 28:e0:2c:38:64:b3 / user 'unknown'
116 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
117 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
118 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 112) for client 28:e0:2c:38:64:b3 / user 'unknown'
119 Tue Feb 26 11:42:27 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
120 Tue Feb 26 11:42:27 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
121 Tue Feb 26 11:42:27 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 183) for client 7c:c5:37:18:ca:2b / user 'unknown'
122 Tue Feb 26 11:14:06 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
123 Tue Feb 26 11:14:06 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
124 Tue Feb 26 11:14:06 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 65) for client 7c:c5:37:18:ca:2b / user 'unknown'
125 Tue Feb 26 11:06:56 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 93) for client ec:85:2f:a2:4d:ba / user 'unknown'
126 Tue Feb 26 11:06:56 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
127 Tue Feb 26 11:06:56 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
128 Tue Feb 26 11:06:56 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 92) for client ec:85:2f:a2:4d:ba / user 'unknown'
129 Tue Feb 26 11:06:56 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 200) for client ec:85:2f:a2:4d:ba / user 'unknown'
130 Tue Feb 26 11:06:56 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
131 Tue Feb 26 11:06:56 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
132 Tue Feb 26 11:06:56 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 199) for client ec:85:2f:a2:4d:ba / user 'unknown'
133 Tue Feb 26 10:54:54 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
134 Tue Feb 26 10:54:54 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
135 Tue Feb 26 10:54:54 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 16) for client 34:15:9e:f0:00:bf / user 'unknown'
136 Tue Feb 26 10:54:54 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
137 Tue Feb 26 10:54:54 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
138 Tue Feb 26 10:54:54 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 90) for client 34:15:9e:f0:00:bf / user 'unknown'
139 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
140 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
141 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 38) for client ec:85:2f:eb:d0:0b / user 'unknown'
142 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
143 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
144 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 15) for client ec:85:2f:a2:4d:ba / user 'unknown'
145 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 31) for client 60:fa:cd:b6:f6:d6 / user 'unknown'
146 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
147 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
148 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 32) for client ec:85:2f:eb:d0:0b / user 'unknown'
149 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 35) for client ec:85:2f:a2:4d:ba / user 'unknown'
150 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
151 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
152 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 34) for client 60:fa:cd:b6:f6:d6 / user 'unknown'
153 Tue Feb 26 10:41:10 2013 AP NTW100-AP17[0] (18:33:9d:b7:a0:70) Device ID: 0x319a, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 6, Cluster ID: 1c:75:a0:02:40:c7, Previous Cluster ID: 1c:75:a0:02:40:c7, Event: Clear
154 Tue Feb 26 10:38:54 2013 AP NTW100-AP17[0] (18:33:9d:b7:a0:70) Device ID: 0x319a, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 6, Cluster ID: 1c:75:a0:02:40:c7, Previous Cluster ID: 1c:75:a0:02:40:c7, Event: Set
155 Tue Feb 26 10:24:39 2013 AP NTW100-AP17[0] (18:33:9d:b7:a0:70) Device ID: 0x3197, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 6, Cluster ID: 1c:75:a0:02:40:c1, Previous Cluster ID: 1c:75:a0:02:40:c1, Event: Clear
156 Tue Feb 26 10:22:46 2013 AP NTW100-AP17[0] (18:33:9d:b7:a0:70) Device ID: 0x3197, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 6, Cluster ID: 1c:75:a0:02:40:c1, Previous Cluster ID: 1c:75:a0:02:40:c1, Event: Set
157 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 13) for client b4:f0:ab:06:25:b6 / user 'unknown'
158 Tue Feb 26 10:15:02 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
159 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
160 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 12) for client b4:f0:ab:06:25:b6 / user 'unknown'
161 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 30) for client b4:f0:ab:06:25:b6 / user 'unknown'
162 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
163 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
164 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 29) for client b4:f0:ab:06:25:b6 / user 'unknown'
165 Tue Feb 26 09:59:58 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 38) for client ec:85:2f:eb:d0:0b / user 'unknown'
166 Tue Feb 26 09:59:58 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
167 Tue Feb 26 09:59:58 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
168 Tue Feb 26 09:59:58 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 37) for client ec:85:2f:eb:d0:0b / user 'unknown'
169 Tue Feb 26 09:59:58 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 11) for client ec:85:2f:eb:d0:0b / user 'unknown'
170 Tue Feb 26 09:59:58 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
171 Tue Feb 26 09:59:58 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
172 Tue Feb 26 09:59:58 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 10) for client ec:85:2f:eb:d0:0b / user 'unknown'
173 Tue Feb 26 09:49:25 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
174 Tue Feb 26 09:49:25 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
175 Tue Feb 26 09:49:25 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 156) for client 8c:58:77:8e:a3:f6 / user 'unknown'
176 Tue Feb 26 09:46:41 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
177 Tue Feb 26 09:46:41 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
178 Tue Feb 26 09:46:41 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 16) for client 24:ab:81:af:2f:da / user 'unknown'

Can you post the output to the command "debug client "?
Can you try if the client has any issues if he was connected to an SSID with OPEN authentication?
Is the wireless NIC drivers updated?

Satellite L500 and issues with wireless connection

Hello people
Ill just throw my problem out there.
First of all my details and info which may help you help me!
Satellite L500 running windows 7 (note: same issues when Vista was installed)
Latest wireless drivers as well as latest drivers for everything else.
My wireless router is a billion voip enabled router 7000 series its quite a good one for when I got it about 2 yrs ago and works fine.
Basically the problem is the wireless on my Satellite L500 keeps dropping out. Im no more than 20m away at most, right now Im 10m away with 1 wall in the way. I tried to get to a website and it says connection dropped out or unable to find host.
However the other laptops in the same room same spot at the same time has no issues at all. Never has.
As soon as I go into the same room as my router it works again. Sometimes works if I just stand on the opposite wall.
So basically Im thinking my wireless card in my laptop is either faulty or just no good?
Can u replace the wireless card with a different one? Maybe the Toshiba ones are just no good? Ive read so many problems with these wireless cards in Toshibas...
Anyone have any ideas? Have I missed any info u need? Ill repost again in a day or so with the types of wireless devices in each laptop.

Hi
At the moment I doubt that your WLAN card is faulty. Before you exchange it you should also update your BIOS and not only the WLAN card driver. Both updates you should download from the Toshiba website:
http://eu.computers.toshiba-europe.com > Support & Downloads > Download Drivers
I had a similar issue with my Toshiba notebook and WLAN connection. The problem was the WLAN power saving mode in Windows Power Management. There you can also choose a power saving mode for the WLAN card. Disable it and choose Maximum Performance.

Having issues with wireless on my iMac

Hello,
I have had my iMac since August of 2011 and sometime last year I decided to upgrade to Lion (like maybe a two three months after I got it). The upgrade was rather smooth, with the big exception that ever since I have updated to Lion I have had annoying issues with my Wireless Internet. I know that this is a known issue, but I am hoping to get some answers/assistance... maybe there is something I can do in my particular case.
Originally the issue was that whenever I turned on the computer from sleep, the Internet was disconnected. Now, I have a been a iMac/Mac Mini user for over 7 years now and I never had such issue, you turn on the computer, the Internet goes on with it too. It would require me to manually connect to the Internet evertime by selecting our Wireless Network from the drop-down menu.
About, I want to say, two months ago? Apple sent out a fix via Software Update that said it would correct issues with the iMac wireless not turning on when returning from sleep, "Finally!" I thought and I enthusiatically waited for the update to come.... and it came and it just made things worse. It doesn't make me manually connect the Network anymore, but it takes it sweet time connecting (like a minute some times) and other times it will connect and disconnect a few times before not giving any more problems. Oh did I mention sometimes it just decides to turn off for no reason at all? Yeah, happens a lot. Especially annoying when I am excersizing my nerd rights and playing an MMO and suddenly get booted from the game because for whatever reason my Internet decides to log me off.
This morning, it was connected to the Internet but websites were taking forever to download, eventually Chrome was just giving up and saying it couldn't connect... but the Internet was connected (full bars if it makes any difference). I tried turning Airpor on and off but no dice. Now, this totally sounds like a router issue, except my boyfriend was sitting behind me on his brand-spanking-new HP and he was happily surfing Reddit or whatever he does whilst online, no issues there.
So the question is: Is it possible to "revert" back to the time before the update? I guess I could use Time Machine, but uhh, I dont want to revert the whole computer. So how exactly would that work (Time Machine noob here)? Is it possible to look at updates done and simply remove? Also, is there a more amicable fix that packing the whole thing up and taking it to the Genius bar? I'm willing to try some DIY fixes as long as they dont involve messing up with the whole network, especially since no other device is having issues, just this one and we have a lot devices.

If you have a router that can do a 5GHZ network try it. There seems to be less interference in that part of the spectrum.
Apple DNS Servers:
208.67.222.222
208.67.220.220
Wireless Improvements
Move the Base Station If interference is particularly bad in one part of your house or office, move the base station to another location. But this can be tricky if your AirPort base station has to connect to the broadband feed coming into the house and that feed happens to enter at a particularly interference-prone spot.
Use the 5GHz Band Compared with the 2.4GHz band, the 5GHz band is practically empty. The newest AirPort Extreme Base Station is one of the few Wi-Fi base stations designed for home use that work in that 5GHz band. All of Apple’s Core 2 Duo laptops and iMacs (except the discontinued 17-inch 1.87GHz model) can also use the 5GHz band; with the build-to-order wireless option, so can the Mac Pro.
To switch to the 5GHz band, launch AirPort Utility, select your base station, and switch to Manual Setup. Click on the AirPort button and select the Wireless tab. Select 802.11n Only (5 GHz) from the Radio Mode pop-up menu. Click on the Wireless Options button and select Use Wide Channels. Click on Update to restart the base station.
Currently, no Mac-compatible adapters enable you to use the 5GHz band in older Macs or with older versions of OS X.

OfficeJet Pro 8600 Plus - Wireless connection issues with Wireless Extender

I have a TPLink Wireless 300MBps wall plug extender to boost the wireless signal around my home.
When in use my OfficeJet fails to connect to the wireless network at all, even if you 're-configure' the wireless as a new connection from the printer.
Turn off the extender, reboot the printer, and voila - it connects within seconds.
Any ideas as to what I can try?

I think there are several things at play here. The most suspicious is that the extender and the router are not the same brand. There may be some protocol issues with this setup that the printer will never be happy with.
Can you move your main router and forget the extender?
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

Self-assigned IPS address problem

Hi,
I have Airport Extreme on G4 with OSX 10:3.9. On open networks, (such as in a coffee shop) I get on no problem. But in some homes with wireless base stations I can't get on, no matter what we try. I keep getting the message:
"Airport has a self-assigned IP address and may not be able to connect to the Internet."
I travel a lot and this has become a real problem. I've tried everything to try and figure out how to make my Airport receive the IP address assigned to it by the base station, but with no luck. Does anyone know the secret?
Thanks so much!!!
Blake

Do you have "ask to join new networks" enabled in System Preferences / Network with the "Airport" option in the left hand pane selected, Dale? If not, try enabling it.
Is Airport the "top" option in the left hand side of the Network panel? If not, try shifting it to the top using the "Set Service order" option (available through the "rosette" next to the "+" and "-" buttons.
In the System preferences /Network panel, with Airport selected on the left, If you click on the "Advanced" button and select the TCP/IP tab, do you have "Using DHCP" selected in the IPv4 box and "Automatically" chosen in the IPv6 box?
How are you going about seeking to join the networks? (the process can vary depending on the provider)
Cheers
Rod

DHCP issue with Airport Express??

HI again, another home networking on a budget question for you all:
I want to create a home network with 2 seamless wireless access points and 2 wired points in two different rooms, on a budget of...well whatever I have my hands on right now. I want to be able to heavily use iTunes Home sharing as well as regular family home internet access.
Here is my setup:
DSL signal to Actiontec Modem/Router
From Actiontec, I broadcast Wifi, and connect a Mac G4 via ethernet, and a second ethernet line uses a powerline adapter to get signal to a Westell router/modem on the other end of the house (small house)
From Westell I connected a PC with no Wifi via ethernet and an Airport Express to broadcast the Wifi
Here are the settings changed from default:
Actiontec: changed ip range to start at 192.168.1.4
changed Wifi name and password
Westell: assigned static IP 192.168.1.2
disabled Wifi (doesn't have the same encryption)
Disabled DHCP (unchecked Private LAN DHCP Server enable)
Airport Express (1st Gen single band)
Wireless Mode: Create a Wireless Network
same Wifi name, password and encryption as Actiontec
Connect Using Ethernet
Connection Sharing:Off, Bridge Mode
Assigned static IP (not sure if I needed to) 192.168.1.3
(configure IPv4:Manually;IP address 192.168.1.3; router address 192.168.1.1; DNS server fields are blank and domain name is blank)
After hooking it all up, programming them all, I powered all the devices down and turned them on Actiontec first, then Westell, then AX.
Problems:
#1 Everything works fine until I plug in the Airport Express. Then ethernet still functions. However, I came home to an IP address conflict on my G4. Wifi will connect on SOME devices. An iPad connected fine, my iPhone 2 inches away would connect but never get a network signal and no internet;it stayed on cellular. As soon as I unplug the AX functionality is resumed but I don't get WiFi out as far as I'd like. Plus I am using it as a Print Server so I dont have to keep a computer on but I havent even attached that one yet.
#2 I can never seem to get all of my libraries to show up on HOme Sharing with iTunes. Specifically the PC connected to the Westell is missing even with the AX disconnected.
What did I miss??
Thank you for reading!!
Joey

Do I need to direct the AX to the 192.168.1.1 for DHCP or is it automatic? If so where?

Sporadic issues with wireless connection (dhcpcd times out)

I'm using a wireless usb adaptor Dlink DWA 110 (chipset rt73). It can connect fine some times, but many times it times out on dhcpcd. Raising the time out time causes it to hold indefinitely on the message "offered 192.168.0.132 from 192.168.0.1". Analyzing the dmesg, I see
[ 118.065433] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 507.792005] wlan0: deauthenticating from 00:1e:58:16:89:8c by local choice (reason=3)
[ 507.795984] wlan0: direct probe to AP 00:1e:58:16:89:8c (try 1)
[ 507.798617] wlan0: direct probe responded
[ 507.798622] wlan0: authenticate with AP 00:1e:58:16:89:8c (try 1)
[ 507.800482] wlan0: authenticated
[ 507.800506] wlan0: associate with AP 00:1e:58:16:89:8c (try 1)
[ 507.802986] wlan0: RX AssocResp from 00:1e:58:16:89:8c (capab=0x431 status=0 aid=6)
[ 507.802991] wlan0: associated
[ 507.816784] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
I'm writing this from an ubuntu live cd, where it works just fine. Here follows my rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="America/Bahia"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(!usblp !ipv6)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="pedro"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
#INTERFACES=(wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
NETWORKS=(dlink)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng network net-profiles cups dbus hal netfs crond alsa webmin timidity++)
I've tried googling, but no suggestion seems to work. Any help?

This is basically a workaround, but still. You can try hold_connect script to automatically watch connection status. It can be found here: https://bbs.archlinux.org/viewtopic.php?id=103139. Just add "iwconfig wlan0 power off" string in function connect under "sudo netcfg down ..." line.

10.5 DHCP issues with Wireless - self assigned IPs?

Similar Messages

Maybe you are looking for