Lync Client 2013 Connexion Failing (new and some users can't connect to Lync Client)

Hello all,

 

I have a complete Lync 2013 topology in production : 1 principal site (where the lync server and his dedicated AD are installed) and 4 remote sites (all the remote sites have its SBA).

However, we always had Lync Client connexion problems : some users on a same PC can connect to the client but others cant, and I dont know why (neither how to troubleshoot this).

I tried with Lync Connectivity Analyzer, even its for mobility client I guess, and the behavior is the same : users who cant connect to Lync display the same message :

-          You didnt get signed in. It might be your sign-in address or logon credentials, so try those again. If that doesnt work, contact your support team. On Lync Clients (while Im sure of the IDs, Ive tried with a new account and is the same).

-          Server discovery failed for secured  channel against https://WSLSFE01.oli-pc.local/Autodiscover/AutodiscoverService.svc/root

The credentials were not authorized by the server. Please verify your login credentials and try again. On Microsoft Lync Connectivity Analyzer

Incredibly, I tried the same with another account and it works good! (an account in the same OU in the same AD of the same domain).

The account seems to be activated on the Lync Server :

 

PS C:\Users\administrateur.OLI-PC> Get-CsUser -Identity "Dorianne Duluc"

Identity                : CN=Dorianne

                          DULUC,OU=CMA16,OU=OLI-PC,DC=OLI-PC,DC=local

VoicePolicy             :

VoiceRoutingPolicy      :

ConferencingPolicy      :

PresencePolicy          :

DialPlan                :

LocationPolicy          :

ClientPolicy            :

ClientVersionPolicy     :

ArchivingPolicy         :

ExchangeArchivingPolicy : Uninitialized

PinPolicy               :

ExternalAccessPolicy    :

MobilityPolicy          :

PersistentChatPolicy    :

UserServicesPolicy      :

HostedVoiceMail         :

HostedVoicemailPolicy   :

HostingProvider         : SRV:

RegistrarPool           : wslsfe01.oli-pc.local

Enabled                 : True

SipAddress              : sip:d.duluc@uh-threethree.fr

LineURI                 : tel:2085

EnterpriseVoiceEnabled  : True

ExUmEnabled             : True

HomeServer              : CN=Lc Services,CN=Microsoft,CN=1:1,CN=Pools,CN=RTC Se

                          rvice,CN=Services,CN=Configuration,DC=OLI-PC,DC=local

DisplayName             : Dorianne DULUC

SamAccountName          : dduluc

 

 

And this one can connect to Lync :

 

PS C:\Users\administrateur.OLI-PC> Get-CsUser -Identity "Jean Cartier"

Identity                : CN=CARTIER

                          Jean,OU=CMA16,OU=OLI-PC,DC=OLI-PC,DC=local

VoicePolicy             :

VoiceRoutingPolicy      :

ConferencingPolicy      :

PresencePolicy          :

DialPlan                :

LocationPolicy          :

ClientPolicy            :

ClientVersionPolicy     :

ArchivingPolicy         :

ExchangeArchivingPolicy : Uninitialized

PinPolicy               :

ExternalAccessPolicy    :

MobilityPolicy          :

PersistentChatPolicy    :

UserServicesPolicy      :

HostedVoiceMail         :

HostedVoicemailPolicy   :

HostingProvider         : SRV:

RegistrarPool           : wslsfe01.oli-pc.local

Enabled                 : True

SipAddress              : sip:j.cartier@uh-threethree.fr

LineURI                 : tel:2034

EnterpriseVoiceEnabled  : True

ExUmEnabled             : True

HomeServer              : CN=Lc Services,CN=Microsoft,CN=1:1,CN=Pools,CN=RTC Se

                          rvice,CN=Services,CN=Configuration,DC=OLI-PC,DC=local

DisplayName             : Jean CARTIER

SamAccountName          : jcartier

 

 

 

I think its a problem about certificates, but Im not sure

               

I compared the attributes (proxyaddresses, samAccountName) of two AD accounts (one who can connect to Lync, and other one who cant) and they follow the same logic of values

I can ping the Lync Server fqdn from client PC.

This is the DNS configuration with all the DNZ zones indicated in best practices :

Global server zone:

Name

Type

State

_msdcs.uh33.local

Main server integrated with Active Directory

Running

_sipinternaltls._tcp.uh-threethree.fr

Main server integrated with Active Directory

Running

uh33.local

Main server integrated with Active Directory

Running

autodiscover.uh-threethree.fr

Main server integrated with Active Directory

Running

sip.uh-threethree.fr

Main server integrated with Active Directory

Running

ucupdates-r2.uh-threethree.fr

Main server integrated with Active Directory

Running

                _sipinternaltls._tcp.uh-threethree.fr

Name

Type

Data

Timestamp

(same as parent folder)

Name Server (NS)

vador.uh33.local.

static

(same as parent folder)

Name Server (NS)

cleopatre.uh33.local.

static

(same as parent folder)

Name Server (NS)

cesar.uh33.local.

static

(same as parent folder)

Source of name (SOA)

[4], cesar.uh33.local., hostmaster.uh33.local.

static

(same as parent folder)

Location of service (SRV)

[0][0][5061] sip.uh-threethree.fr.

static

 

Does anyone meet similar problem and help me please ?

Thank you

September 10th, 2015 2:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics