Home > Lync Error > Lync Federation Error 504

Lync Federation Error 504

Contents

If you want to have the least compatibility problems with other organizations federating with you, it may be worth your time to install the root certificates for some of the more We only see presence offline and cannot initiate IM. Please let me know if this message pops in any other scenarios. Also... check over here

Currently points to port 561 (and not 5061),AND points to lyncacccess.domain.nl (but again your certificate CN is sip.domain.nl) Drago http://www.lynclog.com Edited by Drago TotevMVP Saturday, February 11, 2012 1:14 PM Marked I'll keep writing as much as I can, you keep reading! If you access this article, you will be able to find links for other topologies and their port requirements. That’s because the ROOT cert is not installed on the edge server. see here

Microsoft Lync Error Id 504 (source Id 239)

Thanks Reply to this comment Greig Sheridan 30th January, 2012 at 22:12 Hi B, No, sorry, I'd actually forgotten to revisit that one. Reply to this comment Jenny 18th December, 2014 at 19:43 reference error ID 450 (source ID 239) a message was not delivered and got this error. Federation is enabled and as far as I can see all DNS records are in place.

This definitely looks cert related. Starting Google Earth on Citrix XenDesktop 5.6 vir... Signing into Lync 2013 client presents the warning... This can be done quite easily in most cases by just hitting up the vendor's website with https:// using Internet Explorer on your edge server and "Automatic Root Certificates Update" will

Try logging out of Lync and logging back in, or try again later.” 1) This is usually a media issue. Lync Error Id 403 Source Id 239 The timeout was the result of the request getting to the edge server and then not being able to go any farther. Did the remote peer accept our certificate? this website It's an OCS edge but everything (appears) to be configured correctly.

And by root certificate i mean the CA the company has accuired their certificate; Comodo, Baltimore Cyber Trust, Go Daddy etc. This began to make sense as the problematic organization could see the globe indicating the contact was a federated partner but was unable to message or see presence information. Troubleshooting information is available online, including best practices for using Lync.TestWhen contacting your support team, reference error ID 1 (source ID 0). Post to Cancel %d bloggers like this: It Worked In The Lab… Lync 2010 - Federation Fails (Reference Error ID 504, Source ID 239) Microsoft Lync 2010, Microsoft OCS 2007 R2

Lync Error Id 403 Source Id 239

Thanks a lot, I'll definitely check that next time I run into problems. More about the author The user was receiving IM, but was unable to send them: Once again, the issue was related to port 5061. Microsoft Lync Error Id 504 (source Id 239) Reversing VMware View Optimization Guide for Windo... Test-csfederatedpartner I'll check the messages.

By using @EventZero, of course. check my blog Make sure all certificates CN's match the FQDN it is talking to, make sure 5061 TCP is open both directions, etc. Upon further investigation with logging on the edge server and using snooper, I found this: It turns out that this destination domain is configured with a go-daddy certificate (YUCK!!!) Since Windows Let me know how you get on! - G. Reply to this comment B 1st February, 2012 at 19:19 Thank you Greig, I enabled logging in the clients and found this

Check the routing at each step as well as running port query or telnet to verify ports in both directions. VMware vSphere virtual machines constantly runs a ... The protocol workloads poster (http://www.microsoft.com/download/en/details.aspx?id=6797) is a brilliant resource here, as are the edge reference topology articles on TechNet (http://technet.microsoft.com/en-us/library/gg412898.aspx?ppud=4). this content We are using a SIP trunk.

While sending IM, the error we got this time was ID 504. The trace show TLS errors: Text: The connection was closed before TLS negotiation completed. A quick debugging session with the logging tool on the front end server of the user who is unable to send or see presence information will show the following: TL_INFO(TF_PROTOCOL) [0]0C88.14F4::04/24/2013-22:53:16.498.0000358e

Don’t forget that Lync Server has ports requirement so that federation can work correctly.

Microsoft Customer Support Microsoft Community Forums Technet Menu Sign in Search for: Skip to content Home Library Wiki Learn Gallery Downloads Support Forums Blogs TechNet Products Products Windows Windows Server System Microsoft Customer Support Microsoft Community Forums UC Lobby Unable to resolve DNS SRV Record - 404 Not Found and 504 Server time-out ★★★★★★★★★★★★★★★ August 7, 2014September 24, 2015 by Carlos F. I made sure only my SIP Stack was selected and clicked "Analyze" I followed the path listed in the "Output File" field and grabbed the text file that was created.  Once the The other parties I tested with can federate with other companies so I didn't look into their side.

Reply to this comment Greig Sheridan 26th March, 2012 at 20:46 Tracing the SIP flow should give you some indication as to what's going on, but without that and some more Using PowerCLI to create new role and assign servi... Leave a Reply Cancel reply Enter your comment here... have a peek at these guys Everything is working fine, only federation is not working one way.

Unable to send instant messages or view presence i... we were able to communicate with users only if they started conversation. is not greyed out, but nothing happens. And if you can, make sure the port's open as well.

Eric February 8, 2012 Hey Randy, my public DNS SRV is set up correctly but I'm still receiving this error…I also get it when I run Test-CsFederatedPartner but all other partners thanks . Now go check your Archiving server. :-p “This message was not delivered to because the address is outside of your organization and is not federated with your company, or the And the test of federation to this external domain works So in summary, the error was two things, port 5060 outbound was being blocked, and the edge server did not have

However it didn't work for us. Madison (Madtown) Engineer Information Technology Consulting Search: HomeAbout MeMentoring Videos Posts Comments Exchange Exchange 2010 PowerShell Active Directory Migration Office 365 Uncategorized PKI Outlook Azure ← My advice to all 2013grads…. The best bet is to setup another environment you have control of (if you can) or work with someone who will log from their side as well and just dig in. Reply to this comment Greig Sheridan 15th March, 2012 at 17:16 Hi Bileps!