Direct Federation Desktop Sharing Issue

Hello All,

I am facing the issue with direct federation which is 2 different organizations, IM and presence is fine but issue happening with Application And Desktop sharing, however PPT/Whiteboard and poll is running fine.

Interestingly , all things working with other federated partner ; means for another partner application sharing and desktop sharing is working .

In this case have checked with NW team they saying that all required ports are open, and i believ that is true as 1 federated partner is working fine but other not.

What could be the case and getting ICEx4000320 ICE error code in case of problamatic federated partner.

Looking for the reply asap.

Thanks,

Ankur

June 11th, 2014 4:39pm

If you can completely communicate with another federated partner, and only IM/P with the second, I'd imagine your settings are fine.  Can the other partner confirm they can chat with other partners using desktop sharing?

You could try to test their ports from your edge with the Lync Edge Testing Tool perhaps: http://www.mylynclab.com/2014/02/lync-edge-testing-suite-part-1-lync.html

Here is the ICE decode for your reference:

Free Windows Admin Tool Kit Click here and download it now
June 11th, 2014 5:27pm

For your issue, check below links

http://blogs.technet.com/b/nettracer/archive/2013/01/18/desktop-sharing-fails-between-federated-contacts-running-lync-2010-clients.aspx

http://jamesosw.wordpress.com/2011/12/23/desktop-sharing-failed-to-established/

June 12th, 2014 5:56pm

Thank you for this info , however getting the same as per the shared link...

http://jamesosw.wordpress.com/2011/12/23/desktop-sharing-failed-to-established/

but in our case dont have any firewall as traffic is passing through TMG and public IP's assisgned on TMG external NIC and from there the NAT/firewall rules being defined to access edge services...

Any info would be helpful....


Free Windows Admin Tool Kit Click here and download it now
June 25th, 2014 3:19pm

It still seems odd that you can communicate fully with one partner and not another.  Are there other partners out there that you can test with?
June 25th, 2014 3:32pm

Hi Anthony,

Have been tested with MS also, when i am on internal network its failing with MS and if i am on internet working fine with MS. Looks like that taking some different route when i am on internet.

But with my federated partner i am not able to share desktop/program on both ways means that either i am on internet/internal network.

So this is very weird and found some NAT rules not is place on TMG towards AV DMZ IP.

Will do the correction in the night today to test, however would like to know as all traffic is passing to TMG and then edge ; means TMG is using for web services as well as lync edge service and this arch should work?

Many Thanks,

Ankur Singhal

Free Windows Admin Tool Kit Click here and download it now
June 26th, 2014 10:07am

If you can't share with MS while on the internal network, check your ports again.  Here's the handy poster: http://www.microsoft.com/en-us/download/details.aspx?id=39968   Specifically access from Internal clients to your edge server's internal interface on port TCP/443 and UDP/3478.

For the TMG, did you publish the A/V edge using web publishing rules or just normal firewall rules?  Even though it listens on port 443, it's not HTTPs.

I'd take a look at the Port testing tool again:   http://www.mylynclab.com/2014/02/lync-edge-testing-suite-part-1-lync.html  I imagine you've got an issue with your TMG config if you're using it to publish your edge.

June 26th, 2014 10:21am

Thanks Anthony,  going to do changes tonight on TMg and hoping for the good... will update.

Thank you once again, however when i am internet how come able to share my desktop at that time it will not hit to edge? is my understanding is correct.

-Ankur

Free Windows Admin Tool Kit Click here and download it now
June 26th, 2014 11:55am

When it's just peer-to peer, it will try to directly connect, possibly avoiding the edge.
June 26th, 2014 12:33pm

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

Other recent topics Other recent topics