Apple wireless clients authenticated but show no username in WLC

Running 7.0.220. There are several 'unknown' users every day reported in WCS. Investigating the connections on the WLC I find the clients are in a run state and passing traffic but there is no username listed on the client detail. (hence the unknown on WCS)
(mcm-189jsoc-wlc1) >show client detail 60:c5:47:07:b6:5a
Client MAC Address............................... 60:c5:47:07:b6:5a
Client Username ................................. N/A
AP MAC Address................................... 00:1e:13:42:16:a0
AP Name.......................................... mcm-208dorm-wap1
Client State..................................... Associated
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 1
BSSID............................................ 00:1e:13:42:16:a0
Connected For ................................... 599 secs
Channel.......................................... 11
Clients in this state are usually Apple products. From initial investigation it looks like the do authenticate with the ACS.
Any ideas for debugs to run, or fixes on the WLC? Perhaps there's a bug on this behavior?
Thanks
Kyle Morrison

Kyle:
I suppose you are using PEAP or some EAP that utilizes TLS tunnel.
The username that appears is what cold "outer identity" username. This is sent to the AAA server outside the TLS channel and need not to be the correct username although it can be the same. So I think with macBooks the outer identity is empty. But I don't remember if it appears on the WLC as unknown.
For ipad I can see my username explicitly appearing on my WLC which means the outer identity is same asthe correct username.
What mac devices that you use?
You need no debugs. Wireless packet capture while the client is trying to authenticate should be enough to show what outer identity is used.
HTH
Amjad
p.s: with windows it depends on the supplicant software if an outer identity can be configured or not.
Sent from Cisco Technical Support iPad App

Similar Messages

  • APEx '03 and Non-Apple Wireless Client Connection Problems

    Good morning. I have a 2003 vintage AirPort Extreme, running 5.5.1 firmware (due to the issues with the newer firmware discussed on this forum).
    --> Wired iMax
    My setup is DSL-->APEx--|
    --> Apple Wireless Clients
    --> Linksys w54 acting as a bridge
    In order to get the Linksys working in the first place, I had to remove the WEP, not a huge deal as we live in the boonies and no one within range of the APEx. I couldn't figure out how to get anything to work with Apple wireless security outside of the Family. I have it manually set to channel 1, and radio mode to G only.
    My problem basically is that non-Apple devices can see the SSID but cannot connect. The problem at hand are my kids' various PSPs & Ninendo DS's, and a little Windows CE netbook. Of course, none of these simple devices give anything helpful in terms of errors. Those three different devices all have their own version of the same error: See the SSID, try to connect, but fail.
    I'd like to figure out this problem, although the simpler solution might be to just buy another cheap Linksys on craiglist and use it for the non-Apple stuff.

    Bump?

  • Wireless clients load balancing on the APs on WLC 4404

    Hi Experts,
    I'm just wondering if the WLC 4404 with firmware 4.2.207.0 can load balance the wireless clients on different WAPs. Let's say that an AP is already handling 15 Wireless devices. When the 16th is trying to join, the controller somehow puts it on another nearby AP, even the signal from this AP is weaker. I heard the similar feature on other Wireless solution vendors. I'm just wondering if Cisco has the similar feature or not.
    Thanks!

    Yes it is known as aggressive load balancing sending a code 17 making the wireless client to loook at another nearby AP.
    here it is the documentation:
    http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00809c2fc3.shtml

  • All non-Apple Wireless Clients won't Connect to Time Capsule

    I have a latest gen Apple 2TB TC (ME177LL/A) and have had it for about 14 months. I have never had any issue with it in the past and have perhaps only had to reset it twice in that 14 month span.
    Came home from work last night to watch some Netflix on my PS4, and noticed my PS4 couldn't connect to the network. In the PS4 OS I kept getting errors that said either the network no longer existed or my password was incorrect. I simply tried to re-enter my password multiple times, but only once was the PS4 successfully able to connect. The one time it did connect the network speed indicated in the PS4 speed test was less than 200 kpbs. Within moments, the PS4 lost connection again. I was unable to reconnect.
    At this point I figured I would just use the PS3 instead...same issue, however. Initially thought it was perhaps a PSN issue, but this time I never once could get the PS3 to connect. It repeatedly just said the network wasn't available or the password was incorrect. Went through the same troubleshooting steps that I did on the PS4 with no luck.
    At this point I realized my Lyric thermostat had been erroring out and giving me a notification on my phone---the app on my phone wasn't able to connect to the Lyric via Wifi. Also noticed my August Connect was flashing red and was not connected. DirecTV Genie was not connected to my TC network either. Then went to my home office to discover my Slingbox was no longer connected either. Interestingly enough, though, my iPhone, MacBook Pro, Mac Mini, wife's iPhone, and MacBook all were still connected to my TC network with no issues. I performed speed tests on all of them and all were giving me well over my 60 Gbps Internet speeds. These devices never disconnected nor had any hiccups.
    Essentially determined all my non-Apple devices couldn't stay connected to the TC network.
    Proceeded to just reset the TC and see what would happen. None of the non-Apple devices could connect. Same "Network not found/incorrect password"
    Then proceeded to perform factory reset on TC. At the same time I unplugged my Charter internet modem from power and cat5 out. Powered on modem, waited. Then powered up TC. I did this process twice through, once with auto selected 2.4/5 Ghz channels--still had issue with devices being unable to connect. The second time through, I set up the 2.4/5 Ghz bases upon the most "open" channels as shown by iStumblr (I live in fairly large luxury apartment building that has many networks -- so there are A LOT of networks).
    This time I appeared to have success. One-by-one I was able to connect all my non-Apple devices to this new network with the new SSID and credentials. All devices were able to connect and the PS3/PS4 were able to connect to PSN and I was very easily able to get Netflix.
    Woke up this morning and noticed all non-Apple devices were once again not connected....really not sure what's going on. Didn't have time to dive in deeper before heading to work.
    Just as an FYI, I have 2 different Macs backing up to the TC via Time Machine wirelessly (the primary reason I have a TC and not another router). Also have an Asustor AS5008T connected to the TC via round robin link aggregation. All Macs are running Yosemite. All iPhones are running iOS 8.3. Offhand, I don't know the firmware the TC is running. I made no recent changes to the network or any of the hardware.
    Anybody have any idea what could be the culprit? Any help would be greatly appreciated.

    Whilst I said in my first post that apple had removed all the logs.. you can still get them via PC version 5 airport utility... you will need to plug in via ethernet since wireless is not working. You can also install v5 utility into a Mac but I cannot tell you how. Google it.
    The other method.. and I am not at all sure if it is useful or not.
    Using the airport utility in an ipad.. click on the TC, then edit.. then advanced.. Diagnostics and Usage Data.
    Go into this and you will see the Airport utility has got a stack of info out of the TC..(for secret transmission to apple).
    eg
    I guess it is comparison between normal functionality and when it fails that will show something interesting.. meaning you will need to track the info... and it is not so easy to get it out other than as a screenshot..

  • Wireless Client Authentication issues when roaming Access Points (Local)

    I have a Cisco 5508 with Software version 7.4.121.0 and Field Recovery 7.6.101.1.
    There are a handful of clients that when roaming between AP's with the same SSID that get an authentication issue and have to restart the wireless to get back on.
    From Cisco ISE
    Event
    5400 Authentication failed
    Failure Reason
    11514 Unexpectedly received empty TLS message; treating as a rejection by the client
    Resolution
    Ensure that the client's supplicant does not have any known compatibility issues and that it is properly configured. Also ensure that the ISE server certificate is trusted by the client, by configuring the supplicant with the CA certificate that signed the ISE server certificate. It is strongly recommended to not disable the server certificate validation on the client!
    Root cause
    While trying to negotiate a TLS handshake with the client, ISE expected to receive a non-empty TLS message or TLS alert message, but instead received an empty TLS message. This could be due to an inconformity in the implementation of the protocol between ISE and the supplicant. For example, it is a known issue that the XP supplicant sends an empty TLS message instead of a non-empty TLS alert message. It might also involve the supplicant not trusting the ISE server certificate for some reason. ISE treated the unexpected message as a sign that the client rejected the tunnel establishment.
    I am having a hard time figuring out what is causing this. My assumption is if there were a problem with the Controller or AP configurations then it would happen to everyone. My further assumption is if the client had a problem with their laptop (windows 7) then why does work at other times? So I have checked and the ISE certificate is trusted by client.
    Is something happening that the previous access point is holding on to the mac and the return authentication traffic is going to the old AP instead of the new one or something like that which is corrupting the data?
    I also had this from Splunk for the same client:
    Mar 5 13:44:51 usstlz-piseps01 CISE_Failed_Attempts 0014809622 1 0 2015-03-05 13:44:51.952 +00:00 0865003824 5435 NOTICE RADIUS: NAS conducted several failed authentications of the same scenario
     FailureReason="12929 NAS sends RADIUS accounting update messages too frequently"
    Any help on this would be appreciated. These error messages give me an idea but doesn't give me the exact answer to why the problem occurred and what needs to be done to fix it.
    Thanks

    Further detail From ISE for the failure:
    11001
    Received RADIUS Access-Request
    11017
    RADIUS created a new session
    15049
    Evaluating Policy Group
    15008
    Evaluating Service Selection Policy
    15048
    Queried PIP
    15048
    Queried PIP
    15004
    Matched rule
    15048
    Queried PIP
    15048
    Queried PIP
    15004
    Matched rule
    11507
    Extracted EAP-Response/Identity
    12500
    Prepared EAP-Request proposing EAP-TLS with challenge
    11006
    Returned RADIUS Access-Challenge
    11001
    Received RADIUS Access-Request
    11018
    RADIUS is re-using an existing session
    12301
    Extracted EAP-Response/NAK requesting to use PEAP instead
    12300
    Prepared EAP-Request proposing PEAP with challenge
    11006
    Returned RADIUS Access-Challenge
    11001
    Received RADIUS Access-Request
    11018
    RADIUS is re-using an existing session
    12302
    Extracted EAP-Response containing PEAP challenge-response and accepting PEAP as negotiated
    12318
    Successfully negotiated PEAP version 0
    12800
    Extracted first TLS record; TLS handshake started
    12805
    Extracted TLS ClientHello message
    12806
    Prepared TLS ServerHello message
    12807
    Prepared TLS Certificate message
    12810
    Prepared TLS ServerDone message
    12305
    Prepared EAP-Request with another PEAP challenge
    11006
    Returned RADIUS Access-Challenge
    11001
    Received RADIUS Access-Request
    11018
    RADIUS is re-using an existing session
    12304
    Extracted EAP-Response containing PEAP challenge-response
    12305
    Prepared EAP-Request with another PEAP challenge
    11006
    Returned RADIUS Access-Challenge
    11001
    Received RADIUS Access-Request
    11018
    RADIUS is re-using an existing session
    12304
    Extracted EAP-Response containing PEAP challenge-response
    12305
    Prepared EAP-Request with another PEAP challenge
    11006
    Returned RADIUS Access-Challenge
    11001
    Received RADIUS Access-Request
    11018
    RADIUS is re-using an existing session
    12304
    Extracted EAP-Response containing PEAP challenge-response
    12305
    Prepared EAP-Request with another PEAP challenge
    11006
    Returned RADIUS Access-Challenge
    11001
    Received RADIUS Access-Request
    11018
    RADIUS is re-using an existing session
    12304
    Extracted EAP-Response containing PEAP challenge-response
    12305
    Prepared EAP-Request with another PEAP challenge
    11006
    Returned RADIUS Access-Challenge
    11001
    Received RADIUS Access-Request
    11018
    RADIUS is re-using an existing session
    12304
    Extracted EAP-Response containing PEAP challenge-response
    12305
    Prepared EAP-Request with another PEAP challenge
    11006
    Returned RADIUS Access-Challenge
    11001
    Received RADIUS Access-Request
    11018
    RADIUS is re-using an existing session
    12304
    Extracted EAP-Response containing PEAP challenge-response
    12305
    Prepared EAP-Request with another PEAP challenge
    11006
    Returned RADIUS Access-Challenge
    11001
    Received RADIUS Access-Request
    11018
    RADIUS is re-using an existing session
    12304
    Extracted EAP-Response containing PEAP challenge-response
    11514
    Unexpectedly received empty TLS message; treating as a rejection by the client
    12512
    Treat the unexpected TLS acknowledge message as a rejection from the client
    11504
    Prepared EAP-Failure
    11003
    Returned RADIUS Access-Reject

  • Wireless dot1x authenticated but no IPv4 DHCP assignment

    Hi all, facing some issue on wireless not getting IP from the external DHCP server.
    01. Problem statement
    After authentication success, client PC cannot get IP from DHCP server.
    This is the error log found at the WLC
    *RRM-MGR-2_4-GRP: May 21 15:23:02.643: #LOG-3-Q_IND: dhcp_proxy.c:3944 Received a DHCP packet sent by the controller itself possible network loop![...It occurred 3 times.!]
    *DHCP Socket Task: May 21 15:23:02.171: #DHCP-3-DHCP_PKT_LOOPED: dhcp_proxy.c:3944 Received a DHCP packet sent by the controller itself possible network loop!
    *DHCP Socket Task: May 21 15:22:47.140: #DHCP-3-DHCP_PKT_LOOPED: dhcp_proxy.c:3944 Received a DHCP packet sent by the controller itself possible network loop!
    *DHCP Socket Task: May 21 15:22:43.009: #DHCP-3-DHCP_PKT_LOOPED: dhcp_proxy.c:3944 Received a DHCP packet sent by the controller itself possible network loop!
    *RRM-MGR-5_0-GRP: May 21 15:22:04.188: #LOG-3-Q_IND: acl.c:371 Unable to find an ACL by name ""
    02. Troubleshooting effort and finding
    There's 2 SSID create on the WLC, with different VLAN on each.
    When connecting to the first SSID, it's successfully authenticate and able to get IP from the DHCP
    When disconnect the client PC from first SSID, and connecting to the second SSID, from the client detail it is showing the connection is associated, no IP assigned, and policy manager state is "DHCP_REQD"
    There is no IP lease at DHCP server (using window server 2008 as external DHCP, because virtual WLC is not support hosting internal DHCP server)
    03. Existing Cisco device config and infrastructure setup
    WLC version     : virtual WLC 7.6.100.0
    client PC         :  window 7
    Any suggestion and idea on this? 
    million thanks in advance

    Hi,
    1. As per my understanding you have not properly configure the DHCP proxy, recheck you configuration and commands.
    2.   DHCP option 82 is a king of enhancement specifically employed for distributed DHCP/relay enviornments, using this option relays insert specific information to the request, for to get an idea of clients physical point of attachment or first interaction to the network.
       For understanding DHCP option 82 check the below blog.
       http://blog.ine.com/2009/07/22/understanding-dhcp-option-82/

  • Wireless client authentication failed

    hi all,
    I have a problem I have AP 1602i joined to WISM2 controller with IOS version 7.4.121 
    when client try to connect on the SSID, he receive a log "authentication failed" when I tried to rejoin the AP to other controller it work normally and when i back koining to the first controller it joins normally.
    when the problem occure i noticed that the AP led is flashing and on the controller i can see the AP.
    please advice
    thanks in advance

    hi Manannalage ras...,
    I already issue this command and tried to connect on the SSID but there is no output appeared on the controller it seem to be that the client MAC address is not reach to the controller
    note that,
    the AP connected through Modem to the controller and get the controller IP address from DNS by resolving its domain name to the controller IP

  • Client installed but showing as NO from the server

    Hi All
    I was hoping for a bit of advice, we have moved over to Config Manager 2012 from Landesk. Everything has been working well for a while now, we have pushed out our client to all the machines on our network via client push and everything was working correctly.
    We have a single site, no sub or secondary sites. Within the last week or so I have noticed that most PC's that have been rebuilt are appearing in the admin console as having no agent installed.
    When I have checked the machines they have the agent there, looking at the logs install looks successful. I have seen a couple of posts indicating that it could be a certificate that is the problem. One or two newly built PC's are successfully reporting
    back as ok and I can push software to them. The working ones have the line:
    [RegTask] - Executing registration task synchronously.
    [RegTask] - Client is already registered. Exiting.
    in the ClientIdManagementStartup where as the ones that haven't don't.
    Anyone any advice what could be wrong or which logs I can view to get some clues.
    Any advice would be appreciated at this point.
    Cheers
    Gary
    Gary Porritt Master of the Dark Arts

    You can always try a client re-registration by following this:
    http://www.scconfigmgr.com/2012/11/12/force-a-client-re-registration-in-configmgr-2012/
    What happens if you take one of the failing clients, uninstalls the client by running:
    ccmsetup.exe /uninstall
    from C:\Windows\ccmsetup, and then reinstalls the client. Will it show up as "Yes" then?
    Regards,
    Nickolaj
    Nickolaj Andersen - MCTS - www.scconfigmgr.com - @Nickolaja

  • Initial configuration of ACS 5.1 for EAP authentication for Wireless clients

    Hi,
    I have set-up with below devices :
    Wireless LAN controller 5508
    LAP 3302i
    and ACS 5.1
    since i am new in ACS 5.1 configuration , I need so information to go ahead to configure ACS 5.1.
    which EAP method to use for wireless client authentication ? what is the best practice ?
    I have gone through some cisco documents and it shows that best practice is to configure PEAP but for the same , I need to install certificate in ACS server as well in client PC. is that so ?
    I have no clear picture for this certificate ?
    from where i can get this certificate or do i need to purchase this certificate separately from cisco. how to install it in ACS server ?
    I will be obliged to get atleast initial configuration for ACS 5.1 to enable the EAP method,
    I need GUI based initial configuration for ACS 5.1
    This mentioned ACS 5.1 is installed on ACS 1121 hardware appliance.

    Hi,
    which EAP method to use for wireless client authentication ? what is the best practice ?
    -> I would advise the most widely spread EAP method, which has the best ratio security/easy to deploy: PEAP with MSCHAPv2, which is available by default by all windows machines.
    I  have gone through some cisco documents and it shows that best practice  is to configure PEAP but for the same , I need to install certificate in  ACS server as well in client PC. is that so ?
    -> You will always need to install a server certificate, however, there is no need for client certificate because the authentication is based on the MSCHAP credentials exchange, not certificate based. The only requirement on the client regarding certificates is the following.
    If you want to validate the server certificate, you have to install the server certificate under the trusted CAs of the clients.
    If you do not require to trust the server certificate, you can simply disable the option of server certificate validation.
    I have no clear picture for this certificate ?
    from  where i can get this certificate or do i need to purchase this  certificate separately from cisco. how to install it in ACS server ?
    -> The server certificate can be a simple self signed certificate that you generate and install on the ACS GUI.
    Please feel free to follow this step-by-step guide on
    PEAP under Unified Wireless Networks with ACS 5.1 and Windows 2003 Server:
    http://www.cisco.com/en/US/partner/products/ps10315/products_configuration_example09186a0080b4cdb9.shtml or in pdf
    http://www.cisco.com/image/gif/paws/112175/acs51-peap-deployment-00.pdf.
    HTH,
    Tiago
    If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.

  • Why do some devices show up as wireless clients and not DHCP clients

    When looking at the 'Logs and Statistics' section it shows me the MAC addresses of 3 wireless devices I have on my W/LAN (Macbook and 2 wireless PVR's) in the 'wireless clients' section but no info on the 2 wireless PVR's in the DHCP clients section. Only the Macbook appears there with its ip address shown. Can anyone tell me how to find out the ip addresses of these 2 other devices. I tried connecting one of the PVR's via a cat 5 but that one still doesn't show up in the DHCP clients section.

    Esterhazyinoz wrote:
    Can anyone tell me how to find out the ip addresses of these 2 other devices. I tried connecting one of the PVR's via a cat 5 but that one still doesn't show up in the DHCP clients section.
    Try scanning with WakeOnLan to get a list of all devices and their IP addresses. If the devices got fixed IP addresses at the factory, they won't show up under DHCP.

  • Who is 10.0.1.3 wireless client in my time capsule

    I use my time capsule as a router and there is this wireless client 10.0.1.3 along with all others (which are known to me), except this one.
    How can I find out who is this, or what is it?
    I have AirPort Express connected to TC too, but it shows separately in the AirPort Utility.

    OK Bob/John,
    Sorry for this long post - and thank you so much for your thoughts and time.
    It still shows that 10.0.1.3 wireless client. But now I think it could be my MacBook as the 10.0.1.3 wireless client on the TC has the same hardware address (xx:xx:xx...) as the one that shows in my System Information panel in the Network/Locations folder under the Wi-Fi Hardware (MAC) Address - see screen shots.
    Bottom line - 10.0.1.3 could be my MacBook, but is it really - I am not that tech savvy?
    If it is - where can I go and rename it so it shows my MacBook name?
    Anyway, I am going to tell you what I did if this is relevant for anything you were wondering about. Otherwise you don't have to read the statements below.
    Bob said:
    Power off the entire network....all devices....in any order that you wish when you go to bed tonight.
    In the morning, power up the modem first and let it run a minute by itself
    Power up the next device connected to the modem the same way
    Power up the next, etc.
    Keep powering up devices one at a time until the network is back up
    ------->
    I did that this morning.
    John said:
    The TC will retain the client's IP address until its DHCP lease expires, or you cycle its power.
    If you had a visitor with an iPhone or iPad or iPod Touch the TC will remember its IP address long after he's gone. Don't forget the guest network - if you enabled it, it's open.
    "Ping" that address using Terminal - if the client is no longer present you will get 100% packet loss so that was likely the source of this mystery. On the other hand if you get returns the times shown may be useful.
    -------->
    I have AU 6.1 and it shows on the TC in the Internet Tab option for "Renew DHCP Lease", but I haven't touched it yet, as I don't know what exactly to do. However, I did cycle power the modem.
    And yes, I had visitor a while back (approx. 4 weeks ago) - he has an iPad and and an iPhone too. Both were not on my WiFi though. They were on my Wi-Fi before that - around 8 weeks ago. But at that time I had a different ISP. I don't know if that's important to be mentioned.
    Guest Newtwork is disabled.
    John, I don't know how to "ping" any address in Terminal. Which address are you referring to?
    Bob is right - iPhones and iPads come and go as wireless clients depending on sleep/power off or when they are not on any Wi-Fi but on their celular network.
    John, Yes, all screen shots are from my MacBook 13" AL, late 2008 (yes, I know it is old) running on Mac Lion v.10.7.5.

  • Wireless user authentication detail at syslog server

    Hi Dear.  I configurated wireless network. i want to see my wireless user authentication detail(ip address, username and if it is possibly mac-address) at my syslog server. i do some configuration, the wireless controller send something to my syslog server but i need exctahly the user authentication detail.
    how i do that? please help me. thank you veru much.

    Hi dears. please help me

  • My Ipad2 won't pair up with my apple wireless keyboard.

    My Ipad2 won't pair up with my apple wireless keyboard. It shows it's available to be paried, but when I try to type the 4 number code and press enter, nothing happens and finally the bluetooth search times out.  Anyone with suggestions?

    I realize this is an old post, however I had the same problem (Apple 2009 Aluminum BlueTooth keyboard and iPad 2). I kept getting the "Pairing Unsuccessful" message.  Here's what worked for me:
    1. Turn off the keyboard by holding down the power button until the green light turns off.
    2. I power cycled the iPad by holding the sleep/wake and home button until the screen went to black, and turned it on again. (Not sure if this was necessary, but I figure it couldn't hurt.)
    3. Holding the keyboard in my lap, I pressed AND HELD the power button in through the next few steps.  (DO NOT LET GO UNTIL I SAY SO)
    4. At this point, I got the message on the iPad to type the code. YESSSSSSSSS!
    5. STILL CONTINUING TO hold in the power button, I keyed in the code and pressed return.
    6. Next thing I saw was:
    Bluetooth                                                                             (ON ( ))
    Devices
    Apple Wireless Keyboard ----------------------------------------- Connected (>)
    7. That's it. You can let go of the power button now.
    Hope this helps, I thought I'd post this in case anyone else was having similar problems.
    Cheers!

  • Mac fails to connect to non-Apple wireless network (& changing channel?)

    [sorry to post this in two forums - I think I posted it in the wrong one before]
    I have a wireless network set up from a Netgear wireless router. My Windows XP computer automatically connects to the network every time. But my Mac (OS X 10.4.11) only connects about 50% of the time. The rest of the time it says "None of your trusted wireless networks could be found." Then when I click the airport icon in top right and select the network from the list, it says "There was an error joing the Airport network [network name]." When I click "Try again" a few times, it sometimes eventually connects, but other times it fails repeatedly. It is completely unpredictable.
    I have been looking for solutions on the internet. Lots of other people have problems connecting Macs to non-Apple wireless networks. But no one else seems to have this exact problem: my Mac connects some of the time, but not all. Anyone have any suggestions?
    (One idea I found was to change the channel that the Mac tries to use. How do I do this? I can't find "channel" anywhere under System Preferences - Network - Airport.)
    All OSs are fully updated, so that is not the problem.

    I travel extensively, and both my I-Mac G5 and Intel MacBook are very inconsistent in this regard. I do not think it is a router issue given the variety of networks I try to access. Additionally frustrating once a connection is made is that Internet Connect or Network Status will say I am connected to the Internet via Airport, yet Safari and Mail say I am not connected to the Internet.
    Network Diagnostics has never had an answer. More often than not i end up using my cellular card. but the Mac often has issues with that too... sporadic like first poster describes.
    George

  • Connect multiple 2 apple wireless keyboards to one imac computer

    How to connect several apple wireless keyboards to one imac? Ive got 2 apple keyboards that I want keep and use in different rooms (have more screens connected there). I manage to connect my logitech edge keyboard and mouse in addition to the already connected apple magic mouse and apple wireless keyboard. But it does not seem as if the imac will accept another apple wireless keyboard?

    Hello Steve:
    I have not had a similar problem so I am fishing a bit. I think the problem is rooted in what I thought in my previous post.
    Now, how to fix it?
    Try this:
    Go to system preferences>bluetooth. Delete any KB entries there. Trash a preference file (com.apple.bluetooth.plist). Be sure that on and discoverable are checked in the BT preference pane. Restart your computer.
    Hopefully, whatever KB you have turned on will be "discovered."
    Barry
    .

Maybe you are looking for