Hi There,

We have found out that when taking "Configuration Information" (you know: Ctrl + Right Click Lync icon beside of the clock) from the Lync client it is for some users one of the Lync front end servers, and for other users it could be the pool's FQDN. But then, after some day, it could be also the FE's FQDN for those who had pool's FQDN.

When I look the tracing logs I noticed the following line:

SIP/2.0 301 Redirect request to Home Server

This happening after the client has negotiated with the pool's FQDN at first.

I would like to know more about this as it seems that our Live Meeting clients are unable to handle this kind issue.

We have HLB in use because of the legacy clients.

 

So is it so, that when the HLB direct the connection into the correct home server or the FE where the focus service has seen the user session at last time, there are no troubles. But when it by some reason direct you into different FE of the pool, that server redirect the session into correct server and bypass the HLB?

I have tested this with the Live Meeting client so, that I have added the FE's IP address and pool's FQDN into host file. This way I have by passed the HLB and the Live Meeting has been working fine. If I add IP from some other FE server, the LM wont working.

Also, is there way to check from the server what is user's session home server?

--

Petri

Do you mean there is a lync standard server and a ocs pool coexisting in the your deployment?

Lync Enterprise and OCS enterprise are coexisting. And about the "Connected Lync Server" we got the third variant on the Connection Information :(

1. pools fqdn: pool.child.forest.com

2. pools FE: fe1.child.forest.com

3. sip domain: sip.company.com

What shall be the valid? Or are they all valid?

--

Petri

Petri,

I encountered similar issue last week. After consulting with my good friend Kevin Peters a.k.a. "the ocsguy", turned that upon first sign-in, Lync client will cash some parameters, including Home Server. The moment first (home) server becomes available, Lync client will attempt to sing-in to it, no matter what the real home server is.

The only way to resolve this would be to exit Lync and bomb the user's (Lync) profile found in C:\Users\USERNAME\AppData\Local\Microsoft\Communicator and sign in again.

 

Drago

I am facing similar issue. Did you find a resolution to this?

I know this article is extremely old but did you ever find the cause of this?