Windows 8 clients can't associate to Cisco 2125 controller

HI All,
I have 2125 controller with running IOS 7.0.230.0, now unable to connect windows 8.1 laptops.
It is support Windows OS 8.1 wireless clients, you need to upgrade the firmware to 7.0.250.X.. I think windows is latest version are supported or not. kindly confirm.
Thanks & Regards,
Johnson.

Hi Johnson,
Yes, You have to upgrade to your WLC code at least 7.0.235.0 or above if you are hitting this bug CSCua29504.
https://supportforums.cisco.com/document/113836/windows-8-clients-cant-associate-cisco-unified-wireless
HTH
Rasika
**** Pls rate all useful responses ****

Similar Messages

Client can't associate

I've AP 1121G -
here config-
dot11 ssid 354783729734
authentication open
authentication key-management wpa
wpa-psk ascii xxx
interface Dot11Radio0
no ip address
no ip route-cache
encryption mode ciphers tkip
ssid 354783729734
Client -Cisco PI-21AG configured via Cisco ADU -
selected WPA/WPA@ passphrase.
The client can't associate. in log i see
17: dot11_dot1x_send_ssn_eapol_key: eapol->length 95
*Mar 2 21:31:52.217: dot11_dot1x_build_ptk_handshake: building PTK msg 1 for 0040.96b1.59a5
*Mar 2 21:31:52.317: %DOT11-7-AUTH_FAILED: Station 0040.96b1.59a5 Authentication failed
*Mar 2 21:31:52.317: dot11_auth_client_abort: Received abort request for client 0040.96b1.59a5
*Mar 2 21:31:52.317: dot11_auth_client_abort: No client entry to abort: 0040.96b1.59a5 for application 0x1
Which are the possible reasons of that problem?

The logs clearly indicate that the authentication is failing. Which RADIUS server are you using? And what type of EAP authentication are you using? Has the user database been created on the Radius server? For instructions on configuring WPA on the AP read the document available at http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_example09186a00801c40b6.shtml

Quicktime on Windows clients can't open files in folders with long names!!

Hi,
we've got a really strange problem. We have an Intel Xserve with Leopard Server 10.5.4 which is sharing files over SMB. Everything works fine, except Quicktime on Windows clients (XP Pro and Vista). It looks like the length of the folder names is the problem. If a single folder in the path to the mov has a name that's longer than 8 characters, Quicktime fails with "Error -43: A file could not be found."
x:\test1234\test.mov works
x:\test12345\test.mov doesn't work
Same for UNC paths. VLC on Win and Quicktime on OS X work without problems over SMB. Also the problem doesn't exist on other Samba based fileservers.
Any ideas? Perhaps some smb.conf tweaks to fix this?
Best regards

Just found this post
http://discussions.apple.com/thread.jspa?threadID=1360461&tstart=0
Seems like a well known problem

How windows client can access iCal directory?

I setup Sunbird on Windows can access iCal server calender event.
How can i in windows access iCal server OD user database?
Because when i in Sunbird add new event and invite attenders seems not function.
I think is Windows haven't bind to OD directory.
How can i solve it?

user738616 wrote:
Hi,
The last time I checked - transactional cache cannot be used from Extend clients. Your best bet would be to use "EntryProcessors"
Hope this helps!
Cheers,
NJActually the best bet would be an Invocable sent via an InvocationService accessing the transactional caches from the proxy.
Best regards,
Robert

How many clients can be connected to an Access Point

Hi friend,
I want to know how many clients can be connected in Cisco AP 1140.
Best Regard,
Marco.

Hi,
As Stephen mention the best answer is it depends.
What you need to keep in mind is that wireless is halfduplex and a shared medium and due to this the bandwith will go down per client.
http://www.cisco.com/en/US/products/hw/wireless/ps430/products_qanda_item09186a008009483e.shtml
Q. How many clients can associate to the AP?
A. The AP has the physical capacity to handle 2048 MAC addresses, but, because the AP is a shared medium and acts as a wireless hub, the performance of each user decreases as the number of users increases on an individual AP. Ideally, not more than 24 clients can associate with the AP because the throughput of the AP is reduced with each client that associates to the AP.

Failure of ACL setting for CIFS share resource on Windows client logined with administrator account

Hi,
We accounter a puzzle of ACL setting for a CIFS share resource. In our application, we use the
administrator account to login a Windows 7 OS which is used as the CIFS client. We can access the share resource by "\\server_ip" on this CIFS client, but we can't add
a new ACE to the ACL of a CIFS share resource provided by a CIFS server.
Why dose this hanppen? Note that the CIFS server maybe a Windows OS or a self-developed CIFS server.
The operation details as followed:
1.Access the share resource by "\\server_ip", login the CIFS server by a valid account on the CIFS server.
2.On the Windows client, select the "Security" panel in the mouse-right-button properties dialog of a cifs share resource.
3.To add a new ACE for someone eg. user0, we input "user0" in the "Select Users ans Groups" dialog popped up.
4.Click OK, but the Windows client will not get the user information for user0 from the CIFS server.
WHY?
5.By wireshare network trace, we find the Windows client didn't send any SAMR requests to the CIFS server.
6.Restart the Windows client OS and login again with another account except administrator, carry out the above operations. We find that the Windows client can get the user information, opposite with the step 4 above.
WHY?
7.By wireshare network trace, we find that the Windows client has sent SAMR requests to the CIFS server to get user informations. But that is different from step 5, WHY?
If the Windows client OS is login with administrator account, is there any configuration on Windows client to decide whether request user information on CIFS server when setting ACL for CIFS share resource?
Expect your help.Thanks.
Best wishes.

The purpose of this forum is to support the Open Specifications documentation. You can read about the Microsoft Open Specifications program here,
http://www.microsoft.com/openspecifications/en/us/default.aspx
The library of Open Specification documents is located here,
http://msdn.microsoft.com/en-us/library/dd208104.aspx
It doesn’t appear that you are implementing one of the protocols cited. Your question may be more applicable to Technet's Windows Server Platform Networking forum at
https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverPN or the File Services and Storage forum at
https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverfiles.
If you are working on implementing a protocol using the specifications cidet above, please provide more detail.
Bryan S. Burgin Senior Escalation Engineer Microsoft Protocol Open Specifications Team

OS X DHCP problem for Windows client

I have DHCP server running on my mac OS X Mountain Lion and all my user client (they all are using macbook) are able to access the network by IP address given by this DHCP.
Unfortunatly, any Windows 7 or Windows client can't get DHCP. Appreciate a help.
Thanks

Since you are asking about Snow Leopard Server, you might have better luck of getting an answer if you ask it over in the Snow Leopard Server Forum .
Allan

10.4.9 as Domain Controller fails daily for Windows clients

I have a 10.4.9 Open Directory Master server which also serves as a PDC for Windows XP clients. Windows clients can log in and get roaming profiles with shared homes for Mac and Windows environments. This all works fine.
But, for the last week, every morning, the Windows clients cannot find the domain. I can replace the /etc/smb.conf file with a saved good file, restart the Windows service and all works fine until the next morning, where it fails again. Simply restarting the Windows service does not help; it needs to be reconfigured with a new smb.conf file.
Mac clients can authenticate and connect via smb. The Windows XP Pro clients are up to date with latest updates, so there could be a problem from that, but the updates don't match the date the problems started. The start of the problem coincided with removing an Open Directory Replica, which was no longer needed. It is probably unrelated, but it is the only change I can think of.
There must be some overnight process which resets some setting. Anyone have an idea?
Thanks for any help!
Mostly Xserve servers Mac OS X (10.4.9) 400 + node Open Directory domain Win & Mac All Mac servers
Macs & PCs (too many!) Mac OS X (10.4.4)
Macs & PCs (too many!) Mac OS X (10.4.4)

Tom,
We destroyed our domain and rejoined all our XP boxes. This did not fix the problem. There appears to be a bug in Apple samba-100.7 (10.4.9).
As a quick fix we extracted the smbd binary and smbd.plist from a 10.4.8 combo update (Note: you could also grab the files from a working 10.4.8 install)...
1. Download the 10.4.8 combo update from http://www.apple.com/support
2. Mount the 10.4.8 update .dmg
3. In Terminal navigate to the folder containing Archive.pax.gz, in our case this was...
cd /Volumes/Mac\ OS\ X\ Server\ 10.4.8\ Combined\ Update/MacOSXSrvrCombo10.4.8PPC.mpkg/Contents/Installers/MacOSXSvrCmbBase10.4.8 PPC.pkg/Contents
4. Copy Archive.pax.gz to a location on your HDD, like Desktop
cp Archive.pax.gz ~/Desktop
5. Unzip Archive.pax.gz
cd ~/Desktop
gunzip Archive.pax.gz
6. Grab a copy of Pacifist and use it to open Archive.pax
7. Using Pacifist, extract (drag and drop) the following files from the archive to your Desktop...
/System/Library/LaunchDaemons/smbd.plist
/usr/sbin/smbd
Note: We are going to replace smb in the next step, best backup the current copies of the above files before proceeding.
8. Open Terminal again...
Stop SMB...
sudo serveradmin stop smb
Replace samba with 10.4.8 version...
sudo cp ~/Desktop/smbd /usr/sbin/smbd
sudo cp ~/Desktop/smbd.plist /System/Library/LaunchDaemons/smbd.plist
9. Restart SMB and the process is complete...
sudo serveradmin start smb
Cheers,
Tim

No guest access for Windows clients

Since installing the 10.4.11 OS X Server update, Windows clients can no longer browse the list of shares. Guest access is allowed in the Windows service, and one of the shares does have Guest access enabled. I went so far as to allow R+W for the unknown and unprivileged groups.
The logs show the windows user account failing authentication, which shouldn't even be necessary since Guest access should give them explicit access anyway. The Windows client gets prompted for a user name and password, which does authenticate properly if an actual account is entered. For some reason, this client's IT department is adamant about allowing guest access. Any clues?

Hi,
I know it is a common issue, but the answer you link to is very old and for Windows NT4 and Windows 2000.
I should be possible to enable NAT on the VPN server as described here:
http://technet.microsoft.com/en-us/library/dd458971.aspx
But I cannot get it to Work.
Thomas Forsmark Soerensen

Durable subscriptions and windows clients

Hi,
I think I have found a potential problem.
Scenario
MQ: 3.x or 4.x
Clients: windows OS with Durable Subscriptions
Destinations: Topic
Problem:
Disconnect a windows client with a durable subscription (for example, pulling the network cable)
Try to reconnect, and you will get "Client ID already in use". Under unix, this happens only for a few secs and that's fine. Under Windows, you won't be able to reconnect for almost 10 minutes. That means that a windows client can't easily reconnect if it uses a durable subscription, and has to wait the server killing its socket.
The problem seems that the server socket stays ESTABLISHED (just do a netstat -an | grep -i ESTABLISHED on the server) for a longer time when the client is windows. So that is a windows socket problem (I just tried with a Simpel TCP Server and that's the same), but I think a JMS server should circumvent it
Possible solutions:
- MQ client overriding the connection if a client id is already in use AND the connection comes from the same IP. I think that should be the default!
- a configurable heartbeat between client and server
- Something like "imqcmd deactivate dur" could do the job. I haven't found a way to manually DISACTIVATE the connect, but only to destroy it (imqcmd destroy dur), which obviously isn't a viable option (possible msg loss)
- Java API to do the same thing
ciao,
uL

I think that the problem may be with the TTL on the sockets. Basically as far as I know unless there is a traffic on the connection there is no way to detect that the other end of a socket connection is gone. You may try enabling ping on the connection this may speed things up.
Tom

Windows Client log to the Mac Os X Server ?

Hello everybody
I would like to create a network with Mac OS X Server. I have Windows PC's that would also be in the network.
Does windows clients can connect to the Mac Server with a username and password ?
Thank you.

At the simplest, sure, Microsoft Windows clients can connect to OS X Server services with appropriate credentials. Mail and file sharing, for instance.
Beyond password-based authentication, a more advanced configuration is probably not as simple nor as easy as you might want. Windows clients really want to use Microsoft Active Directory here and Kerberos authentication probably won't get you where you want. (This assuming that you can get the Windows clients to accept OS X Server Kerberos authentication.)
The usual approach for single sign-on in heterogeneous environments is the so-called Magic Triangle configuration with both Microsoft Active Directory running on a Windows Server and Open Directory running on OS X Server. This involves the two domains communicating. It might be easier to get OS X clients operating off Windows Server, particularly with the use of profiles in more recent versions.
As an alternative to Windows Server, recent versions of the Samba server package include authentication services compatible with Active Directory, and you may be able to get your Windows clients to authenticate to that, and build that as part of a Magic Triangle configuration. You'd need to download and configure the Samba server, and get the Samba AD support working.
Related discussions and documentation here and here and maybe this thread. There are other discussions.

Wireless client can't get an IP but can associate with the Cisco 1200 AP

Hi!
Good day to everyone.
I guess i need some help with regards to a problem of mine.
I have a Cisco 1200 AP with IOS 12.3(2), the client is MS Win XP on an IBM notebook with an onboard intel wireless client.
the RADIUS server is a MS IAS and it is integrated with MS Active directory where I authenticate.
somehow the client can associate with WPA and TKIP however it won't receive an IP add after logging into domain. I have tried clearing out the TKIP and WPA and leave authentication open and guest mode on the config. this would be successful.
I also want to ask what does the "list_name" on the methods of authentication on EAP? Is this a RADIUS server's name or the AD server's name?
Attach is the configuration I made on the AP.
Thanks in advance,
Chris

I have this same issue, it seems the AP is not supplying the group key needed to complete the authentiction...so your being authenticated, but not fully with the AP. I have a sniffer of a good connect and a bad one, its got something to do with the key (if you look at the link status, you will probably see something like this beside security
TKIP, WEP, Key Absent
The Key Absent portion is bad. Its whats stopping us from getting fully "connected" with our AP's, but i have yet to figure out why.

Cisco Jabber for Windows Client SDK

Is there an SDK for Cisco Jabber for Windows client? I could only find the Web SDK. Are there no other SDKs that would let me control features of the Jabber Windows Client?

And in order to avoid TAPI limitation, they say they have started using Jabber which controls all phone functionalities through an Application User connected to the Call Manager.
Assuming they are referring to the normal Jabber for Windows/Mac/iOS/Android applications then this is wrong. Jabber - the client, not the IM&P servers which are part of the CUCM cluster (if you're familiar with Lync consider CUCM+IM&P servers a Front End Pool) - do not use an Application User at all. When a user starts Jabber, assuming SAML SSO is off, they supply an email address. This is used to find the servers via DNS SRV records, or the Mobile and Remote Access Expressway (roughly analogous to a Lync Edge pool) to tunnel through the firewall. After the email address they are prompted for their End User username and password. This is then used to access several APIs on the server, namely the User Data Service to discover what the user has. This would include what the user has configured/available to them. After this is done the Jabber client does one of three things with respect to phone functionality:
If the user has no phone devices provisioned for them - physical or software - it becomes an IM&P client only.
If the user has a software phone phone provisioned, it registers as that using SIP. In this way Jabber is the actual phone. This is called a CSF device for Jabber Windows/OS X.
If the user has a desk phone assigned to their End User account AND administrative policy is to default to desk phone control, it registers to CTI Manager on the CUCM server to control the user's physical phone.
A user can toggle between option two and three, if appropriately provisioned, but cannot have both simultaneously. In other words, Jabber is either controlling a physical phone over CTI or is a phone itself using SIP. The difference is where the audio/video media is sent from/to.
All of this happens using that human's End User credentials.
Now, if you wanted to have a server control the user's phone - either a physical one or Jabber - you would use the TSP as an interface to CTI Manager on the CUCM server and receive real-time events (e.g. the user went off-hook, the phone is ringing with this caller ID, etc.) and issue commands to that phone (e.g. make a call to X). This is done using an Application User account because the server would need to do this for multiple users simultaneously. If you also use the Super Provider concept, the CUCM administrator doesn't have to take the extra step of associating every phone to your Application User manually. Instead, you can simply issue CTI subscriptions to see any/all device activity you want.
This is all assuming you wanted to do the integration server-side to avoid having to update the Cisco TSP application on every user PC (which also limits your WPF application to machines capable of running the TSP) every time the CUCM administrator patches the servers. If you don't care about that, then you can do this all client-side on the user's PC, and have them supply their End User credentials.
Of course, you could also reconsider the Jabber SDK and just embed the make/receive call functionality directly into your application instead.

MacBookPro - Suddenly can't connect to Cisco WAP while Windows Users Can

Hi,
My partner and I, both consulants, use MBP's. At one of our client's sites, our MBP's suddenly stopped being able to connect to the wireless network there. We believe this started happening shortly after installing a regular security update last February.
The odd thing is, we can go to another building where there is another access point, same make and model, same SSID, which we can connect to with no problem.
Meanwhile, since we are the only Mac users, and are mere consultants, the local IT guys don't bother to check it out.
We get the "There was an error joining the Airport network "<network name>" error message. We have double checked and know we have the right WEP keys. I don't remember off hand the strength of the WEP, but it's pretty simple and straight forward, and must be the same as the other WAP since all the Windows users can go between locations without having to reconfigure.
I've been to the genius bar, and they haven't seen any reference to this any where in the KB or on any of the forums.
If anyone has any ideas, please let me know.
Thanks,
-ktb

My partner called Apple Support today after downloading a security update he hoped would address the problem (but to no avail). He managed to reach someone who knew something about the problem.
The support staffer indicated that there was a known issue connecting with some Linksys WAPs (and since Cisco now owns Linksys, they are probably using the same chip sets in some products). Even though the staffer acknowledged that the problem was caused by a security update, and thus was a software problem (confirmed by the fact that we can connect when we boot windows in Boot Camp and are able to connect), they said there was nothing they could do - not even offer a way to downrev our airport firmware.
This is the kind of support I expect from the Evil Empire in Redmond, not Steve and company. Feh - success breeds contempt.
MacBook Pro Mac OS X (10.3)

How many clients can associate to the AP?

Hi
I need know how many clients can associate for this AP model
AIR-CAP3502I-A-K9
AIR-LAP1131G-A-K9
I have 45 clients currently associated with each AP.
Thanks

I need know how many clients can associate for this AP model
Theoretically, you can have 1098 clients per WAP. However, in practice, this will depend entirely on the type of Wi-Fi traffic being pushed around.
Cisco recommends no more than 25 clients per WAP. But if you are just pushing emails, HTML around then this number can go as high as 35 clients per WAP. If you are pushing HD video, then the number goes down to around 8 clients per WAP.
I have 45 clients currently associated with each AP.
This is too much. Even for a 1131. Take note that, unlike the 3502, the 1131 only has FastEthernet data port. So with 45 clients connected to the 1131, you may have some bottleneck.

Windows 8 clients can't associate to Cisco 2125 controller

Similar Messages

Maybe you are looking for