<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Setting Up and Troubleshooting LDAPS Authentication in Forefront TMG 2010</title><link>http://blogs.technet.com/b/keithab/archive/2012/02/29/setting-up-and-troubleshooting-ldaps-authentication-in-forefront-tmg-2010.aspx</link><description>Lightweight Directory Access Protocol over SSL (LDAPS) is used in Forefront Threat Management Gateway (TMG) when the decision has been made not to join TMG to the Active Directory domain. LDAP is a protocol used to read and write to Active Directory and</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Setting Up and Troubleshooting LDAPS Authentication in Forefront TMG 2010</title><link>http://blogs.technet.com/b/keithab/archive/2012/02/29/setting-up-and-troubleshooting-ldaps-authentication-in-forefront-tmg-2010.aspx#3570128</link><pubDate>Wed, 01 May 2013 08:27:25 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3570128</guid><dc:creator>yargray</dc:creator><description>&lt;p&gt;Unfortunately I am having similar problems as described above. &amp;nbsp;We get the &amp;quot; LDAP server not responding&amp;quot; alert quite regularly, but in our case all functionality appears to be fine and the LDP test described in this blog is fine too. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Any suggestions on finding the root cause for this would be much appreciated! &amp;nbsp;Alternatively, if this is some kind of &amp;quot;false&amp;quot; alert, is it safe to override it in SCOM?&lt;/p&gt;
&lt;p&gt;Many thanks,&lt;/p&gt;
&lt;p&gt;G&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3570128" width="1" height="1"&gt;</description></item><item><title>re: Setting Up and Troubleshooting LDAPS Authentication in Forefront TMG 2010</title><link>http://blogs.technet.com/b/keithab/archive/2012/02/29/setting-up-and-troubleshooting-ldaps-authentication-in-forefront-tmg-2010.aspx#3558916</link><pubDate>Fri, 15 Mar 2013 13:59:53 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3558916</guid><dc:creator>Karsten Hedemann</dc:creator><description>&lt;p&gt;As jr_suisse I&amp;#39;m experiencing exactly the same issue. I have found nothing wrong in the network and TMG is configured correctly. It&amp;#39;s the same on two different domains.&lt;/p&gt;
&lt;p&gt;I have been looking at timeout settings etc., but haven&amp;#39;t had luck to figure out what was wrong.&lt;/p&gt;
&lt;p&gt;And as the warnings comes in the Application Event Log, the user (if logged in) experience a timeout until the Event Log &amp;#39;Description: The connection to the LDAP server x.domain.local was restored&amp;#39; is logged.&lt;/p&gt;
&lt;p&gt;If a user is about to logon, they can also experience long login times and the same Event Log is logged, and Again when &amp;#39;Description: The connection to the LDAP server x.domain.local was restored&amp;#39; is logged the session may even be signed in and the user can browse the SharePoint site, or the timeout was so long that the user need to login Again.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3558916" width="1" height="1"&gt;</description></item><item><title>re: Setting Up and Troubleshooting LDAPS Authentication in Forefront TMG 2010</title><link>http://blogs.technet.com/b/keithab/archive/2012/02/29/setting-up-and-troubleshooting-ldaps-authentication-in-forefront-tmg-2010.aspx#3494380</link><pubDate>Wed, 25 Apr 2012 07:54:37 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3494380</guid><dc:creator>jr_suisse</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Very good post. I&amp;#39;ve implemented it on my TMG NLB. Normally it works fine. But in the last time when i have checked the log i saw the following Alert Information: &lt;/p&gt;
&lt;p&gt;&amp;quot;The LDAP server x.domain.local did not respond. If the server is physically reachable and a secure (SSL) connection is required, this event may be caused by failure of the SSL handshake.This event may also occur when the credentials used to connect to the LDAP server to verify the status and change the password of an account are rejected by the server &amp;quot;&lt;/p&gt;
&lt;p&gt;After a few minutes i have the following Alert Information:&lt;/p&gt;
&lt;p&gt;&amp;quot;Description: The connection to the LDAP server x.domain.local was restored.&amp;quot;&lt;/p&gt;
&lt;p&gt;I can&amp;#39;t understand why it happens. I checked the FW between the TMG&amp;#39;s and the DC. I checked the DC, everything semms to work. Also the Certificatas are ok. Wiht the LDP.exe Toll i can successful create a connection. Analysing the network trace with wireshark shows me, that there are no ssl handshake or tcp problems. Have you ever seen this? Do you have any ideas? I&amp;#39;m searching for a solutinos since weeks but I can&amp;#39;t find anything. Thank you&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3494380" width="1" height="1"&gt;</description></item></channel></rss>