Wireless Clients can't connect post WLC Upgrade to version 7.4.100.0

Upgraded WLC Flex 7500 controller to: 7.4.100.0
Previous WLC Controller version: 7.2.111.3
After the upgrade, all AP's reported back to the controller and looked like working. We have 50+ branch sites that connect back via Layer 2 to the main office. The main office SSID's were broadcasting and users could connect and get the proper IP's. Users that connected back through FlexConnect AP's couldn't obtain an IP address. The client would authenticate to the WLC and accept the SSID key, but would not get an IP address. I see with the 7.4.100.0 upgrade there are more options for DHCP for each interface, which we don't use interfaces for all sites as we did in the early days, now we make sure the flex connect tab has the vlan identifier in the tab and the traffic goes out the local firewall etc. Each remote site has a Linux based firewall and DHCP server.
Looking for any insight with the 7.4.100.0 upgrade that may cause clients to not connect and obtain an IP address.
We have since back dated our WLC Software to: 7.2.111.3 to allow things to work pre upgrade which everything worked fine.
Any suggestions would be great, we had to upgrade version 7.4.100.0 to support our AP 1602.
Thanks in advance.
Matt

Verify that you have an upgraded FUS image. Second, make sure your WLAN to vlan mapping on the FlexConnect AP's have the correct vlan mapping. I have seen these change to the default vlan mapping.
Sent from Cisco Technical Support iPhone App

Similar Messages

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.

How many sets of wireless headphones can I connect to my iPad at one time?

How many sets of wireless headphones can I connect to my iPad at one time?

Did you mean Bluetooth? One. Did you mean FM or infrared, driven from the 3.5mm output jack? Any number of them, assuming you use the same frequency to receive the stream.

HT1825 Can I connect post cinema displays to my G4 and how?

Can I connect post cinema displays to my G4 and how?

You can use newer monitors but there are different ways to connect.
It all depends on the video card installed in your computer. Different model cards had different ports. My G4 MDD has the ATI Radeon 9000 with one ADC port (abandoned technology) and one DVI port (useful technology). So we need to either see the description of your graphics card from System Profiler >Graphics/displays, a photo of the ports on your card, or both.
As long as you find a monitor that shares the kind of ports on your Mac, you will be fine. I have a 2008-vintage LCD monitor on that circa 2003 MDD of mine. The MDD shipped with an Apple DVI-to-VGA adaptor so I can connect any monitor with DVI or VGA ports.
There is an inconsistency in your equipment profile: No PowerMac can run OS 10.6. Please do "About this Mac" and verify your processor type and Mac OS version. Then you can edit your profile to avoid future confusion.

Mac10.x client can't connect to File Server on Windows2008 Failover Cluster

Installation of a cluster was made according to the document "Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster " http://technet.microsoft.com/en-us/library/cc731844.aspx.
My Mac OS X 10.5.2 and Mac OS X 10.4.11 clients be able to connect to a non-cluster file server on a Windows 2008 (the File Services role) and also to old file cluster on a Windows 2003.
Why Mac clients can't connect to Windows 2008 Failover Cluster?

Are you running a firewall on the Macs. If yes does it work with out the firewall? If it works with out the firewall that means you will have to create a custom ipf rule which includes the both the physical an virtual IP addresses of your cluster.

Some clients can't connect after 10.6.6 update - the see an error -43

Hi There,
I'm a designer so am not all that technical but have managed to setup and maintain OS X servers since 10.5.
I've just updated the server to 10.6.6 and now some of our clients can't connect - they get the following error:
"There was an error connecting to the server. Check the server name or IP address and try again.
If you are unable to resolve the problem contact your system administrator."
If I click OK to the error above on the client, I see another error which reads:
"The operation cannot be completed because one or more required items cannot be found.
(Error code -43)"
I've restarted the server and the clients but no luck.
The server is running the following services:
- AFP
- DNS
- Firewall
- NFS (although I don't remember setting this up - is this started with AFP?)
- Open Directory
I can ping the server and login via ARD so not sure why we see the first IP address error as mentioned above.
Any help or suggestions would be most welcome.
Regards
Ben

One question, is this when you hit "Connect to Server" or is this after you've established a connection and try to open/edit/save files?
Here is some general advice:
1) I assume your whole network is behind a router and that we are talking a small office environment (5-10 people) and not some large enterprise. If so the Firewall service can probably be disabled. As a matter of fact if your issue is that clients can't connect at all the firewall may actually be causing your problem.
2) NFS can almost certainly be disabled. Its generally only used for two reasons 1) The netboot service needs it. 2) You support unix/bsd clients. I can see from your list of services that netboot isn't something you're doing and I doubt that as a designer you would have much use for unix/bsd systems.

HT5569 my computer no longer finds my iPhone wirelessly, I can only connect to my phone as a hotspot by connecting with the cable

My computer no longer find my iPhone wirelessly, I can pnly connect to my personal hotspot my using the cable.

There may be something in the following "Troubleshooting Personal Hotspot" that will help: http://support.apple.com/kb/TS2756

External outlook clients can't connect to Exchange 2013

Currently running server 2012 r2 and exchange 2013 sp1...
Internally everything works fine, clients can also connect externally to owa/ecp. However when using an outlook client they are unable to connect. This is my first experience with exchange 2013 so I am at a loss. What steps should I be following to get this
working properly? Or if anyone has some suggestions to get more information I can do that as well.
Thanks!
Connecting from a mobile-phone using mail.mail.com works fine.
We are using a self-signed certificate for testing purposes..

Testing Outlook connectivity.
The Outlook connectivity test failed.
Additional Details
Elapsed Time: 941 ms.
Test Steps
Testing RPC over HTTP connectivity to server mail.mail.com
RPC over HTTP connectivity failed.
Additional Details
Elapsed Time: 941 ms.
Test Steps
Attempting to resolve the host name mail.mail.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: xxx.xxx.xx.x
Elapsed Time: 535 ms.
Testing TCP port 443 on host mail.mail.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 176 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 229 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.mail.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=mail.mail.com, Issuer: CN=mail.mail.com.
Elapsed Time: 154 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name mail.mail.com was found in the Certificate Subject Common name.
Elapsed Time: 0 ms.
Certificate trust is being validated.
Certificate trust validation failed.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.mail.com
A certificate chain couldn't be constructed for the certificate.
Tell me more about this issue and how to resolve it
Additional Details
The certificate chain didn't end in a trusted root. Root = CN=mail.mail.com
Elapsed Time: 33 ms.

Outlook client can't connect in but OWA works

You need to make sure your OutlookAnywhere and AutoDiscover settings are setup properly along with Split-DNS. OutlookAnywhere and Split-DNS are vital for future-proofing your Exchange configuration and making it work properly now, regardless if you use Exchange 2007, 2010, or 2013. For Exchange 2013, OutlookAnywhere is a requirement and Split-DNS is Best Practice. If you are on Exchange 2007 or 2010, and you do not have OutlookAnywhere enabled, enable OutlookAnywhere and follow this guide.You should always use NTLM over Basic authentication, as Basic sends the username and password in the clear, and NTLM is Windows Authentication. On Exchange 2013, you also have a new option called Negotiate, which is recommended. As you follow this guide, you will set the ClientAuthenticationMethod (Internal and External if on Exchange 2013) to NTLM...

Outlook client can't connect in configured outlook on workstation but OWA works.
This topic first appeared in the Spiceworks Community

How many wireless devices can be connected at once to an airport extreme?

How many wireless devices can be connected to an airport extreem at one time? I have 4 iphones and 2 ipads, a goolge chrome and 4 wired devices.

Any AirPort Extreme produced since 2008 will support up to 50 wireless devices and 150+ wired devices simultaneously, so this should accommodate most users in most homes.

I can't connect to the new downloaded version of Skype, as my old one is in the way, and don't know how to get rid of it.

I can't connect to the new downloaded version of Skype, as my old one is in the way, and I can't get rid of it. what do I do?

We'll need more details.
What happens when you drag the old version to the Trash?

Some wireless clients can't discover or connection to local wired systems

Hi,
I've just upgraded my home wireless from an NetComm NB5540 + modem to a LinkSys X3000.
Internet access works fine for all devices, but some wireless devices can't "see" my Win7 desktop system that's on a wired connections to the router.
I've tried three devices...
Galaxy Note phone (running ICS 4.0.4) can discover and connect to file shares on my desktop system without any problems.
Asus Transformer Prime tablet (running JellyBean 4.1.1) can see the router on the local network, but can't see my desktop. Even if I manually type in the IP address it can't connect to it
Likewise my old WinXP laptop can see the router but can't see or connect to any other devices.
Any suggestions welcome.
Hugh
ps. I tried connecting the NetComm router with just Wifi configured to one of the ethernet ports on the X3000, so I've got two Wifi networks running in parallel. If I connect to this second WiFi network with any of the above devices then they can all discover and connect to my desktop system on the wired connection to the X3000.

Just to test network connectivity, why don't you ping the wired client from the wireless devices that are not able access it? Do post your results so we can further analyze this scenario. By the way, when you cascaded another access point (using the NetComm router) to the X3000, was it via LAN- LAN? Was the X3000 still the DHCP server for the wireless clients?

Windows XP client can't connect to AirPort Extreme AP with WEP enabled.

Hello,
I have big problem with Mac Mini AirPort Extreme working in AP mode with Windows XP client.
Some time ago, AP refuse to connect Windows XP clients (notebook) when WEP is enabled (40/128 bit, same problem), while before that, everything work perfect.
On other hand, iPhone can connect using WEP without an problem.
When WEP is turned off, XP client can connect but this is not acceptable for me.
I must notice that friend of mine have absolute SAME PROBLEM which rise almost at same time few months ago. They have Mac Mini and XP notebook (different then mine) which can not connect with WEP turned on, while his iPod touch work!
I guess that this happened due AirPort Firmware upgrade included in some of Apple software update.
Does anybody have similar problem or know the solution?
My AirPort Card Information:
Wireless Card Type: AirPort Extreme (0x168C, 0x86)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 1.4.16.2
Current Wireless Network: Mac mini
Wireless Channel: 11
Tnx in advance.

mikikg, Welcome to the discussion area!
Sorry but this is a known issue.
The only solution is to get a real wireless router instead of using your Mac mini as a base station.

Lync 2010 Mobile client can't connect to the server. it may be busy or temporarily unavailable

I have the following issue after renewed the Lync internal and external certificates, Lync Mobile client get the following message when try to connect from internal or external network "can't connect to the server. it may be busy or temporarily
unavailable"
PS I tried a lot of solutions from different articles, but the same result.
presented below my environment:
Two Lync 2010 frontend servers with one pool.
Two edges server.
HW load balancer.
Log from Lync connectivity analyzer.
User Name: [email protected]
Logging test parameters:
SIP Uri: [email protected]
Discovery Type: Automatic Discovery
Network access: NetworkAccessExternal
Selected client: ApplicationLyncMobile2010
Starting Lync server autodiscovery
Please wait; this test may take several minutes to complete...
Starting automatic discovery for secure (HTTPS) internal channel
Sending HTTP request to
https://lyncdiscoverinternal.xxx.com/[email protected]
Exception encountered while sending an HTTP request to
https://lyncdiscoverinternal.xxx.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to
connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:443
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:443
For troubleshooting, try using a browser to open the server discovery URL
https://lyncdiscoverinternal.xxx.com/[email protected]
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden
by its access permissions 192.168.89.25:443
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for secured internal channel against
https://lyncdiscoverinternal.xxx.com/
Starting automatic discovery for unsecure (HTTP) internal channel
Sending HTTP request to
http://lyncdiscoverinternal.xxx.com/[email protected]
Exception encountered while sending an HTTP request to
http://lyncdiscoverinternal.xxx.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to
connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:80
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:80
For troubleshooting, try using a browser to open the server discovery URL
http://lyncdiscoverinternal.xxx.com/[email protected]
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden
by its access permissions 192.168.89.25:80
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for unsecured internal channel against
http://lyncdiscoverinternal.xxx.com/
Starting automatic discovery for secure (HTTPS) external channel
Sending HTTP request to
https://lyncdiscover.xxx.com/[email protected]
Exception encountered while sending an HTTP request to
https://lyncdiscover.xxx.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect
to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:443
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:443
For troubleshooting, try using a browser to open the server discovery URL
https://lyncdiscover.xxx.com/[email protected]
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden
by its access permissions 192.168.89.25:443
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for secured external channel against
https://lyncdiscover.xxx.com/
Starting automatic discovery for unsecure (HTTP) external channel
Sending HTTP request to
http://lyncdiscover.xxx.com/[email protected]
Exception encountered while sending an HTTP request to
http://lyncdiscover.xxx.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect
to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:80
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:80
For troubleshooting, try using a browser to open the server discovery URL
http://lyncdiscover.xxx.com/[email protected]
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden
by its access permissions 192.168.89.25:80
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for unsecured external channel against
http://lyncdiscover.xxx.com/
None, AutoInternalSecureD, AutoInternalUnsecureD, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST,
MobilityMCXInternalLMXCheckGET, MobilityMCXInternalLMXCheckPOST, MobilityMCXExternalLMXCheckGET, MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
Automatic discovery of the Lync server failed. Please verify the server requirements at
http://go.microsoft.com/fwlink/?LinkId=278998 . Lync mobile apps do not require automatic discovery. You could enter the server FQDN manually and test connectivity again.
Microsoft Lync Connectivity Analyzer cannot analyze deployment readiness until a discovery test has completed successfully.

Hi
Is that Port 443 opened? check the fire wall.
is that external Lync clients are logging in with out any issues.
by seeing the Log it is unable to connect on port 443
Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made
to access a socket in a way forbidden by its access permissions 192.168.89.25:443
For troubleshooting the Mobility issues follows this
http://blogs.technet.com/b/nexthop/archive/2012/02/21/troubleshooting-external-lync-mobility-connectivity-issues-step-by-step.aspx
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

Wireless Network - can't connect!!

Lenovo N 3000 running Windows Vista Business
Product 0769A64
I can't connect to wireless internet. Am at the end of my tether and hope it's something simple!
This is what's happening so far...
Using Access Connections, I can use the wireless radio to find the network I want. It's a public wireless connection (in a library). It has signal strength of 60%. This has been more than fine for me in the past. Everyone else is using it so why can't I!?!?!
When I try to connect through Access Connections, I get the following message:
Unable to connect to the selected wireless network. You may need to configure your system to support the authentication method that is in use. Do you want to configure now?
I click Yes, (don't really know what I'm doing at this point so just OK out of that window)
Then it tries to connect. It then goes through Applying wireless settings - OK, then when it says 'waiting for association, it fails.
If I connect through networks, I can connect to the local network only, but not the internet.
What I've tried to fix it (don't even know if any of this is relevant...):
Made sure it's automatically setting IP address.
Switched off Windows Firewall
Boot in safe mode.
Checked the network adapter and it is working properly and has up to date drivers.
In Control Panel- Network connections, under Wireless Network Connections, I've disabled/enabled TCP/IPv6 and TCP/IPv4 in various combinations.
Thought I may as well let the cat have a go at fixing it after all that lot.
Run command prompt as administrator.
ipconfig /release shows: No operation can be performed on Wireless Network connection while
it has its media disconnected
ipconfig /all shows:
Host Name..............Default-PC
Primary Dns Suffix.....:
Node type..............Hybrid
IP Routing Enabled.....No
WINS Proxy Enabled.....No
Ethernet adapter Local Area Connection
Media State............Media Disconnected
Connection-specific DNS Suffix..:
Description............Intel(R) PRO/Wireless 3945ABG Network Connection
Physical Address.......:00-1B-38-0c-25-E2
Autoconfiguration Enabled....Yes
Wireless LAN adapter Wireless Network Connection:
Media State............Media Disconnected
Connection-specific DNS Suffix...:
Description............isatap.(453E23F5-D966-4B89-B53C-A4E3D9CF0071)
DCHP enabled...........Yes
Autoconfiguration enabled...Yes
Then a load of stuff about Tunnel adapters - *6, *7 and *9 are discomnnected. Apparently.
Tried to run PC Doctor on the network card and it passed the following tests:
PCI Express Status Test
Wireless Connectivity Test
Wireless signal Strength Test
Network Link Test
But it couldn't run the :
TCP/IP Network Communication Test
Any help at all would be incredibly gratefully received!!
Thanks, Claire.

I just purchased a Thinkpad from Lenovo with the Intel 5100 AGN wireless card in it. I kept losing my connection to the Internet. I searched on the web for a solution and tried a number of the suggestions, one of which solved one problem (access connections was turning off the wireless radio during inactivity to "save power"), but the problems persisted, even after I let Windows manage the connections.
The first symptom I noticed was that Windows could not find any networks. The next one I noticed was that the signal strength would drop very low. I even saw that when the laptop was 2 feet away from the router.
I finally came to the point where I was suspecting the Intel 5100 AGN itself. I have 2 other computers that use my wireless router and they have no problems, and people have come over with laptops and have not had any problems.
The router I have is D-Link Di-624 Xtreme-G. It seems to work just fine. I reconfigured the router to not use its Super-G mode. That appears to have eliminated the problem. It is still too early to be sure since the problem is intermittent, but it has stayed connected for a day now (whereas I used to lose the connection frequently in any given day).
I can't say for sure if the problem is with the 5100 AGN card, but I suspect it is. Given that I have never had this kind of problem with other computers (with varying cards) but only with this new one, the culprit seems to be the Intel 5100 AGN.
There are a lot of posts on the web about this very problem and no one seems to have found the answer.
I may have fixed the problem within my home by reconfiguring the router, but I can't do that for other routers (eg in a coffee shop). Other people have "solved" the problem by buying a new router (an expensive solution). The real fix has to be in the 5100 AGN itself, either a better driver (I have the latest version 12.1.0.14), or some card configuration (or else somehow replace it with a better wireless card).

Wireless Clients can't connect post WLC Upgrade to version 7.4.100.0

Similar Messages

Maybe you are looking for