For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

mikeshimkus_111's avatar
mikeshimkus_111
Historic F5 Account
Feb 26, 2015

Hi, can you give us more detail about your deployment? Which Lync services are you using? If you have Lync Edge services running, the clients should not have a route to the internal Lync servers; they should be forced to connect through the Edge as if they were external clients.

 

Chase_Abbott's avatar
Chase_Abbott
Icon for Admin rankAdmin
Feb 26, 2015
Unless they have internal and external names defined for the Lync pools against the client. If that's the case the client shouldn't need to connect to edge services or reverse proxy as the FE Pool will handle all of that traffic. However, if the client is connected prior to VPN tunnel and they don't allow the client split-tunnel, the client would fail until reconnected to the internal address space. At that time, for 2010 at least, it would try to use 5061 for the internal client port by default. Not the best setup but is supported by MSFT. And per Mr. Shimkus, we would need to know more about the deployment specifics.