XSAN client can't connect due to 'duplicate registration'

I'm trying to connect a client machine to an Xsan server, but whenever I try to type in the registration number and save it, it comes back saying "Error while writing settings(duplicate registration)"
We were using this computer on the Xsan before with this same registration number, but we had to reinstall the OS, and now it won't accept the registration number.
None of the other machines are using the number, I went through the configuration files on all of the different machines and found no reference to this number. I'm not sure where to go from here.
Anyone know how to solve this issue?

The Xsan SN is kept locally, and so if you reinstalled it should clear it up. Perhaps trying to add it using Xsan admin on another computer would work.
Or if you tried another Xsan SN temporarily, it might solve your problem.
Log in to the ADC (developer.apple.com) and get a free account. Try the developer SN for Xsan.

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.

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.

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

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.

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.

10.5: VPN clients can't connect to each other

Hey all,
I've got a bit of an odd problem. Got my VPN server setup and working fine on 10.5.4. Clients can connect in, mount file shares, etc. However, if we have multiple clients connected in via VPN, they can't connect to each other. They can't ping each other or anything. I've checked firewalls, etc, on the client machines, and everything looks fine.
Machines within the network can ping and connect to them both, it's just when they're trying to connect to one another that the problem occurs. Any ideas why this might be, and any possible solutions?
Thanks in advance,
Paul

OS X Server / VPN /The L2TP-VPN server did not respond

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 7 client can't connect to Server 2008 R2 Print Server VM (ESXi 5.5)

I have an issue today that is driving me bonkers.
I recently came on-board to a company in my area as the system administrator and this network has everything and the kitchen sink wrong with the network layout, probably the worst I've seen and I'm slowly but surely fixing it day by day.....
Well today I decided I was going to spin up another VM from a template and make a Print Server, seems harmless right? --- I thought so too, added all of the printers to the server and did test pages, all was dandy, but then I tried to add the printers to
clients and other server and the real fun has begun, I'm truly perplexed now...
I added a VM to my esxi 5.5 cluster at work that is a 2008 R2 server with only print management on it. I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via
DNS. I can test printers directly from the print server successfully printing out test pages however whenever I try to map printers you know from the directory in 'devices and printers' from any of the Windows 7 clients or any of the other 2003/2008 servers
I get the classical "Windows cannot connect please check the network connection and make sure sure the printer is turned on". I disabled the windows firewall and I made the point to print GPO set to disabled and still no luck. Again I can print to
all of the printers internally inside of the VM (so I know it communicating to all of the printers), I just can't connect to the printers listed in the directory on any of external desktop/client, it's like so annoying. spent about 6 hours until my brain just
couldn't think anymore, was about to go BS on the VM.
The only thing I can think of, as I was driving home, is that there is a GPO on one of the DC that has a desginated print server policy set. But prior to last week the forest leve was 2000 and now it's 2003. I just don't know Server 2000 enough to know if GPO's
worked in the same way they do in 2003.
Right now printers are connected to other servers in a ad hoc mentality it seems, there has never been a true print server.
Anyone ever have this problem before?
I'm truly puzzled...

Hi Mid.Hudson-IT,
Before we begin ,we should ensure we have configured the printer server correctly .
Here is a link for reference of configuring the printer server .
Print server role: Configuring a print server
https://technet.microsoft.com/en-us/library/cc775791(v=ws.10).aspx
"I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via DNS"
From this sentence ,I can`t figure out whether you have tried to ping the server both with the IP adress and name adress from the client ?
If we can ping the print server from the client,we can ensure the connection to the printer server is good .
Then we can try to install the printer driver directly to have a check .In the adress bar of Windows Explorer ,input "\\server name \the printer name"
If we cannot ping the print server ,we should troubleshoot the network issue firstly.
We also can check the event viewer for more information to troubleshoot this issue .
Best regards

Error when trying to install oracle client (can't connect to X11 error)

Hi guys,
I need help to install Oracle Client 10g. I am quite a novice so I am totally hopeless when it comes to difficult or linux-kind-of-terms.
I can't use GUI at all, so everything got to be done through putty.exe
my local pc (where the putty is, IP 192.168.8.194) -> linux red hat 4 IP 192.168.8.31 (where the oracle client should be!)
when I run the runIntaller I receieved error mentioning about DISPLAY variable haven't set yet.
I did set it trhough putty as follow
DISPLAY=192.168.8.194:0.0
export DISPLAY
no luck...I still hit an error that eventho this time the error is like below;
=============================================================================
Can't connect to X11 window server using '192.168.8.194:0.0' as the value of the DISPLAY variable.
192.168.8.194:0.0
192.168.8.194:0.0
OUI-10025:Unable to start an interactive install session because of the following error:Can't connect to X11 window server using '192.168.8.194:0.0' as the value of the DISPLAY variable. The DISPLAY environment variable should be set to <hostname or IP address>:<screen>, where the <screen> is usually '0.0'.
- Make sure that client users are authorized to connect to the X Server.
OUI-10027:To enable client users to access the X Server, open an xterm, dtterm or xconsole as the user that started the session and type the following command:
% xhost +
To test that the DISPLAY environment variable is set correctly, run a X11 based program that comes with the native operating system such as 'xclock':
% <full path to xclock... see below>
If you are not able to run xclock successfully, please refer to your PC-X Server or OS vendor for further assistance.
Typical path for 'xclock': '/usr/X11R6/bin/xclock'
==============================================================================
When I run the xclock using GUI I can see it pop up on my screen, but when I run xclock trhough putty, I see that it just went blank...is that right because I am using putty or what?
Can you guys please help? Everyone that had this problem like find the solution real easy...I just so frustrated because this setting is just not working, and I have no idea what to check. Do I need extra library or something to install this?
Please remember that I can use GUI in my test server but I can't use any GUI at all when I am implementing this.
Thanks thanks thanks.
Daniel -

Hi-
You are right. putty is just a simple console without X11 in it. how come it didn't even cross my mind?
Thanks for the reply. I solved it by using third party software called xdeep, from what I got from internet looks like this and the software you were talking about hold the same purpose. This xdeep is pretty easy to configure and in just few seconds I can launch the installer! Gee...!
For those guys that having the same problem as me then find xdeep software from google and browse on the configure webpage. I found a step by step configuration setting from the internet too and it's real easy.
Daniel -

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.

Client can not connect to Server installed window server 2008 and using 8.8

HI all!
I have a problem when Client log in to server that installed window server 2008.It can not connect to this server even when restart and key in IP or Server name,...
I try disable Firewall of window 2008 in server machine and client can connect to server. But when i disable firewall, it's mean i can not use Remote desktop or terminal service..
Now, how i can do in order to solve this problem.
Thanks!

Hi,
Take a look at the admin guide (Page 75, 119, 159):
[http://service.sap.com/~sapidb/011000358700000150922010E.zip]
If you installed a firewall on the license service computer, make sure that the firewall is not set to port 30000; otherwise, the license service cannot work.
If you are using Port X, make sure that you open Port X and Port (X+1) in the firewall. For example, if you are using port 10000, make sure to also open port 10001.
The default communication port is 1143.
The default port of the SAP Business One license server is 30000 for license communication and 30001 for the license naming service

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

XSAN client can't connect due to 'duplicate registration'

Similar Messages

Maybe you are looking for