Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 552
  • Last Modified:

Lync 2010 Client Install "Cannot sign in Server Temporarily Unavailable"

We have been able to install to machine that are external to our network but the users have an AD account and they have logged into Lync client without issue. However, we have a few that throw the Cannot Sign in Server Temporarily Unavailable.
We have done the manual configuration for External/Internal and the same error.
Also, noted the TCP selection is grayed out.
Anyone see this before and know of a fix?

Thank you  very much
0
kryanC
Asked:
kryanC
  • 5
  • 4
2 Solutions
 
davorinCommented:
I would try to (temporarily) disable firewall on problematic computers. Also make attention on firewalls and web filtering components of antivirus.
0
 
kryanCAuthor Commented:
Thanks but we have made sure firewall is not active on the machine. We also had the client connect to an open network without any firewalls and disabled all anitvirus settings.
We get the exact same issue.
Could there be a GPO that the user is unaware their company has pushed that may be causing an issue?

Again, thank you for any and everything you can give.
0
 
davorinCommented:
To role out the network as the cause of the problems - have you tried to connect another computer that connects correctly from elsewhere to the same network as the problematic computer is?

At the end of this link you have the list ports that are needed by Lync client:
http://www.mimanu.com/2011/02/microsoft-lync-server-and-client-2010.html
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
kryanCAuthor Commented:
We have had the user test from an outside network with the exact same issues. I keep coming back to maybe something or security setting on their machines but have no idea what to look for or where.
I am currently trying to see if we can get a known good device over to them to test from inside their network to verify once more that they are not blocking anything.
We had sent their network team all the ports before and the made the adjustment then. That is why we had the user attempt from outside the network to verify it was more likely something on the machine.

Thoughts?
Thanks
0
 
davorinCommented:
Are you saying that:
- users in local network, that do part of the domain, can connect to lync inside AND outside of the network.
- users in remote network can not connect to lync, even if they try to connect from different networks

What about certificates? Do the problematic computers trust certificates installed on Lync?
Have you tried to run lync connectivity tests?
https://testconnectivity.microsoft.com/
0
 
kryanCAuthor Commented:
Yes, you are correct with only a note that only a few users from one company are unable to connect external via their personal networks and business network.

I was able to note that they use Symantec Protection on these machines and am trying to get a test with it disable but they are 250 miles away and their company requires it.

Again, we still see that their TCP option is always grayed out despite making Registry change to enable it. I bring this up just because ours and other client boxes have it available.

Also, other clients throughout the world have no issue with auto-discover and tested on client for manual without issues.

Not sure if they trust the Certs thought will check for sure.

Thanks again be back ASAP
0
 
kryanCAuthor Commented:
Well, after changing registry, re-installing Lync, and a million other items, I loaded Lync 2013 and it works perfect. Believe the root cause is something with the client Symantec End Point but could never disable it or change any of the rules they have.
Thanks to everyone who tried to help.
0
 
davorinCommented:
I have not noticed your previous post, but I'm glad that you have solved your problem finally.
0
 
kryanCAuthor Commented:
The Lync 2013 client works perfect. Not 100% sure on why other than client machine and Symantec
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now