Clients can't connect after IP change

Changed the IP address from 192.168.1.1 to 192.168.8.1.
I have 100's of clients (school) and now none of the clients can connect.
Switching back to the old IP works fine.
What needs to be updated so the clients can connect to the new IP?
Any help greatly appreciated!
Mac Mini OS X Lion Server

The mac server is handling DNS. Where would I make the change?
The IP change due to poor planning on behalf of the school. They have in essence run out of IP addresses on the original address scheme so I had to create new addresses.

Similar Messages

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.

Report Builder Can't Connect after IP Change

I can write the queries that I need to but continually run into issues with SRS and its Report Builder
Someone moved the report server onto another LAN and it has a new IP. All the reports can still connect to the data source and so work just fine.
When I launch Report Builder 2 from the Report Server/Report itself, it pops up that "connection failed" and follows up with "Unable to connect to the server that is specified in the URL"
Basically I need to configure it to point to itself I guess but that seems to not be happening. The changes were already in the report manager when I went to check them. I have no idea how long it's been this way.
I've attached a pic to show the successful connection to report server, but bad from report builder. Also the configuration of the report server.
I found posts related to proxy but that can't possibly help b/c the thing is looking for an IP that doesn't exist! It's own has changed.

Hi Kirkee,
According to your description, after someone moved the report server to another LAN and a new IP, all the reports can still connect to the data source and work fine. When you launch Report Builder 2 from report manager or report, you got the error message.
The error message "Connection failed. Unable to connect to the server specified URL <Report Server URL>" means we are not able to connect to the Report Server. We can follow these steps to troubleshoot the issue:
Open the Web Services URL (known as Report Server URL) in the Internet Explorer (IE). Make sure it is able to open it.
Try to use IP to access the Report Server from the Report Builder.
Run the Report Builder under the domain account (Press key SHIFT and then right click the Report Builder, click 'Run as different user').
Check the Reporting Services error logs (by default, it can be found from C:\Program Files\Microsoft SQL Server\<SQL Server Instance>\Reporting Services\LogFiles).
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu

Can't connect after password change

roommate claims we were hacked and he changed the password to a WEP but now i can't connect. it basically comes down to a "connection timeout" every time i try. i've changed and updated all the proper areas in network preferences and keychain access but nothing works. and even though the password is in keychain access and it asks me if it can allow its use, it will then still ask me for the password in window.
any ideas? i realize this is vague but not sure where to go from here. oh, and also the network wifi comes and goes even though i'm sitting next to the router. i tried another router and it's all the same complete with vanishing wifi so i'm assuming it's something with my computer. but then i also have a G4 desktop and it won't connect either.
i was using open DNS but have deleted that info in the preferences as in the past, that sometimes causes problems when connecting to new networks for the first time.
so could it still be a DNS issue or possible keychain access or something i'm not even thinking of?
(and dumb question, but does it matter in a WEP password if the letters are caps or not? tried it both ways but anything i can eliminate as a cause at this point would be great.)
thanks very much

When someone maliciously accessed your network, he may have changed other AirPort settings too, so I would verify everything is as it should be. Your roommate could also have changed something beyond implementing WEP encryption, either intentionally or not.
You might also see if you can isolate the cause to your computers by creating a new network "location" for them.
I don't believe OpenDNS is the problem. If your AirPort network becomes unavailable at random intervals, that problem must be solved before anything else will work.
... does it matter in a WEP password if the letters are caps or not?
Yes. WEP passwords are case-sensitive.

Safari can't connect after latest Lion update

Just updated my software and now safari can't connect to websites. It connects for a bit then after awhile it will no longer connect. Firefox and Chrome are connecting fine so this is a safari only issue with the latest update.
Safari Version 5.1.5 (7534.55.3)
Quiting safari and restarting works for a little while then eventually 'can't connect to server' eventually appears. I'm going back to firefox until this is resolved.

Linc Davis
Currently Being Moderated Re: Safari can't connect after latest Lion update
Apr 2, 2012 5:35 AM (in response to rtorca)
Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins and log in as Guest. For instructions, launch the System Preferences application, select Help from the menu bar, and enter “Set up a guest account” (without the quotes) in the search box.
While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem(s)?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
Note: If you’ve activated “Find My Mac” or FileVault in Mac OS X 10.7 or later, then you can’t enable the Guest account. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. The instructions provided by Apple are as follows:
Be sure your Mac is shut down.
Press the power button.
Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem(s)?
After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2.
Hi I have the same sort of problems I carried out the two tests and the problem appears to only be in my profile not in guest profile. Is there a cure?

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.

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.

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

Lion Server: iOS 5 clients can't connect to Address Card Server

I have set up shared accounts on the server for Calendar and Address Book (family) sharing. Although I can add and use the Address Book shared account on OS X Lion clients, I can't get this to work on iOS 5 clients (iPhone nor iPad). I keep on getting "CardDAV account verification failed".
Calendar sharing works just fine on both OS X and iOS5 clients
Let me briefly describe my setup and observations:
Server:
Running Lion Server 10.7.2 on Mac Mini (server)
Using SSL connections with keys generated during set-up of the server
Portforwarding in router (ao) for 8008 and 8843 (iCal and Address Book)
Created shared accounts on server for Calendar ("sharedcalendar") and Address Book ("sharedcontacts")
In the DNS server I created services in my primary zone for "_caldavs._tcp." and "_carddavs._tcp." both on port 8443
OS X Client (Calendar)
Created additional CalDAV account in preferences (user "sharedcalendar")
Left the server settings untouched (server path, port "auto" and using SSL but not Kerberos)
Created in "sharedcalendar" different calendars and reminder lists for the family members which each can access from their OS X client
This account is now set-up through Profile Manager (tried this with Address Book as well but didn't make any difference)
iOS 5 Client (Calendar)
Once tested on standalone and got this working I'm now using the Profile Manager to push the definition of the shared account to all clients
Hostname with port 8443 (default)
Left Principal URL blank since it was optional
User "shared calendar" with the appropriate password
Ticked "Use SSL"
OS X client (Address Book)
Created additional CardDAV account in preferences (user "sharedcontacts").
Left the server settings untouched (port 443 using SSL)
iOS 5 client (Address Book)
In the settings add a CardDAV account (server, user "sharedcontacts", password, description).
First error message "Cannot connect Using SSL. Do you want to try setting up the account without SSL?". When I press continue I get the error "CardDAV account verification failed"
If I then save the account details still and edit the account I can access the "advanced settings". When I change to SSL I have tried port 0 (default value), 8443 (the one that's listed in the documentation) and 8843 (which is used by default if you try to set up the
account in Profile Manager). All to no avail, including Profile Manager
Observations:
Lion Server app nicely lists both Calendar and Address Book Server as active (plus Profile Manager, File Server, Web server and Wiki server)
When I access my server home page, Calendar is listed in addition to other services (Mail | Calendar | Change Password | Profile Manager) but not Address Book. Is this normal behaviour? i.e. can't Address Book entries be changed through a web interface?
Address Book on OS X client uses 443 for SSL but does not require me to define port 8443 for secure iCal or Address Book server communications
Lion Server Profile Manager specifies port 8843 as port for SSL communication. I only saw 8443 listed in documentation
The response "can't connect .." or "account verification failed" happens very quick which make me think either the verification doesn't even leave the iPad or there is something wrong in the SSL connection
Since iCal set-up works nicely using the same ports I am puzzled why it doesn't work for Address Book
Your solutions or suggestions how to investigate are most welcome,
Erik

Thanks for joining the discussion.
Although port 8443 is mosten quoted as correct port for CalDAV and CardDAV, port 8843 can be found both on Apple's website and other places:
see Technical Note 1649 to find port 8443 listed for iCal and port 8843 for Address Book
Mac OS X Lion Server for Dummies (sic) lists port 8843 on pages 236 and 238 but port 8443 in many other places
when you want to push iCal and Address Book information with Profile Manager, Profile Manager lists port 8443 for iCal but port 8843 for Address Book as default:
So I hope you understand I'm somewhat puzzled.
I did get the Address Book working for my Lion desktops with the all the necessary certificates as far as I know, just not for the iOS devices (iPhone and IpPad). iCal sharing from Lion Server works fine on both Lion and iOS devices.

Windows Vista won't connect after security change

I have an AirPort Extreme base station, to which we connect using an iMac, PowerBook G4 and a Windows Vista laptop. I used to have it set to WEP, but changed it to WPA for the increased security. After the change, my PowerBook and iMac are connecting just fine, but my wife's Vista machine has been nothing but headaches. It will sometimes connect, after a bit of fighting with it, but not reliably or quickly. At the moment, it says that it is connected with local and internet access, but I can't actually access anything on the internet, and diagnosing the problem in Vista reports that a wireless network cannot be found (despite the fact that it simultaneously reports that it is connected to one).
I know squat about Windows -- I'm a Mac guy. Anybody know how to help me fix this?
Thanks in advance!

No answers, but the problem seems to have disappeared. Man, I'm starting to realize how fortunate I am to have been using Macs for the last 23 years. I think Vista is going to be a very good thing for Apple! There's nothing like actually using Vista to make one want to flee screaming and never look back...

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.

Mail service on, SMTP on, but clients can't connect -- please help a novice

Hi all,
We use 10.4 Server on a G5 Xserve. A few days ago we had a problem with our server being used for spam. That was fixed quickly enough, but the problem is: while being fixed, the mail queue accumulated more and more mail, and it wasn't going out. The "retry" button didn't work. Repairing the database didn't work.
To make a long story shorter, after reading different things here and on the web, I managed to delete all the messages in the queue. All the users are still there. But now, when I turn the mail service back on, everyone gets a "can't connect" error.
I've used the terminal before, but I've always been following directions; I don't know what to type or why. But if someone with patience can help, I can follow directions, and would really appreciate the help. Right now I'm dead in the water.

OK, I've already admitted that I know nothing about this, so I'm sure this will give some people some laughs. That's OK, so the only thing I've changed was the name of the company. I have more peace of mind knowing I'm not showing who's got problems. The other thing is that I don't know when my part of the history begins. Maybe it's all me, but I don't remember doing anything even remotely close to changing IPs. So here it is:
1 telnet mail.abcde.com 110
2 telnet mail.abcde.com 110
3 telnet mail.abcde.com 110
4 sudo /etc/squirrelmail/config/conf.pl
5 grep swupd /etc/swupd/com.apple.server.swupdate.plist > ~/Desktop/
6 update_list.txt
7 grep swupd /etc/swupd/com.apple.server.swupdate.plist > ~/Desktop/
8 update_list.txt
9 grep swupd /etc/swupd/com.apple.server.swupdate.plist > ~/Desktop/update_list.txt
10 softwareupdate
11 man changeip
12 changeip
13 exit
14 changeip -checkhostname
15 sudo changeip
16 changeip -checkhostname
17 sudo changeip -checkhostname
18 man changeip
19 sudo changeip -gethostname
20 sudo changeip -gethostname
21 sudo changeip
22 /usr/sbin/changeip /LDAPv3/127.0.0.1 10.10.10.3 10.10.10.3 mail.abcde.org mail.abcde.org
23 sudo changeip -checkhostname
24 sudo /usr/sbin/changeip /LDAPv3/127.0.0.1 10.10.10.3 10.10.10.3 mail.abcde.org mail.abcde.org
25 changeip -checkhostname
26 sudo changeip -checkhostname
27 sudo rm -rf /usr/share/swupd/html/061-4590/
28 sudo rm -rf /usr/share/swupd/html/061-4589/
29 sudo rm -rf /usr/share/swupd/html/061-4589
30 sudo rm -rf /usr/share/swupd/html/061-4590/
31 sudo rm -rf /usr/share/swupd/html/061-4590/
32 sudo rm -rf /usr/share/swupd/html/061-2089/
33 grep swupd /etc/swupd/com.apple.server.swupdate.plist > ~/Desktop/update_list.txt
34 sudo mkdir /usr/sieve
35 sudo mkdir /usr/sieve
36 sudo pico /etc/services
37 netstat -an | grep 2000
38 telnet localhost 2000
39 sudo mkdir -p /usr/sieve
40 sudo mkdir -p /usr/sieve
41 sudo chown cyrusimap /usr/sieve
42 sudo chgrp wheel /usr/sieve
43 cd
44 pwd
45 ls
46 cd /usr
47 ls
48 ls -l
49 exit
50 sudo pico /etc/services
51 telnet localhost 2000
52 netstat
53 netstat -an | grep 2000
54 exit
55 changeip
56 sudo changeip
57 changeip -checkhostname
58 sudo changeip -checkhostname
59 exit
60 sudo ls -al /var/spool/imap/user/diradmin
61 sudo ls -al /var/spool/imap/user/kbentley
62 sudo /usr/share/mailman/bin/check_perms -f
63 su root
64 su root
65 su root
66 su root
67 su root
68 fsck -f
69 fsck
70 sudo fsck -f
71 sudo fsck /?
72 fsck /help
73 fsck \help
74 pwd
75 ..
76 12345
77 sudo /System/Library/CoreServices/Finder.app/
78 sudo /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
79 su root
80 su root
81 sudo -u cyrusimap
82 su cyrus
83 su cyrus
84 su cyrus
85 su cyrus
86 su cyrus
87 cyrus
88 sudo cyrus
89 su cyrus
90 su cyrus
91 su cyrus /usr/bin/cyrus/bin/reconstruct -r -f /var/spool/imap/bbills
92 postfix reload
93 sudo postfix reload
94 sudo postfix reload
95 ls -l /var/spool/imap/user/bbills
96 history

WPA2-enterprise WIFI can't connect after upgrading to 6.1 or higher

Hi. Please help.
We have a campus wifi with two ssids: one open for everyone and one closed with wpa2-enterprise (PEAP) security for staff. All iphones and ipads works just fine on ios version 6.01 but they can't connect to secured wifi network after updating to ios ver 6.1 and higher (tried 6.1.2). They still able to connect to open wlan ssid. Our WIFI equipment is: Extremenetworks WM3600 controllers and AP4600/AP4511 access points running WM5.4.1. WMM enabled.
WM3600 controller use Windows2008 r2 NPS server + active directory for authorization (selfsigned certificates is 2048 bit length).
WM3600 wlan staff configuration settings:
wlan Staff
description TOGU staff network
ssid STAFF
vlan 238
bridging-mode tunnel
encryption-type tkip-ccmp
authentication-type eap
no answer-broadcast-probes
protected-mgmt-frames optional
radius vlan-assignment
no motorola-extensions symbol-load-information
use aaa-policy Domain_aaa
Here is the log from iphone configuration utility with connection error:
Feb 20 17:18:00 kernel[0] <Debug>: en0::IO80211Interface::postMessage bssid changed
Feb 20 17:18:00 Preferences[132] <Warning>: -[VPNConnectionStore reloadVPN]: The active VPN configuration has changed from to (null)
Feb 20 17:18:00 Preferences[132] <Warning>: -[VPNBundleController _vpnConfigurationChanged:] (0x1edbea10:<VPNBundleController: 0x1edbea10>): _serviceCount(0), serviceCount(0), toggleInRootMenu(0), RootMenuItem(1)
Feb 20 17:18:00 wifid[14] <Error>: WiFi:[383033880.387575]: Failed to associate with STAFF: -3900
Hope to get any help.

Yes. We tried to reboot iphone(s), tried also with ipads 6.1. We tried to reset network settings.
We tried to add wifi profile to clean new iphone using iphone configuration utility.
Wireless supplier can't help - they told it is an ios issue and I think this is true because all
ipads/iphones works just fine on ios5 or 6.0.1 but can't connect on 6.1

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

Clients can't connect after IP change

Similar Messages

Maybe you are looking for