<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/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>Qdabra Active Directory Web Service</title><link>https://www.infopathdev.com:443/forums/57.aspx</link><description>Qdabra Active Directory Web Service enables showing all Microsoft Active Directory user details in InfoPath forms. It is available in Database Accelerator, WSSP and as a standalone tool.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Force the AD lookup to a specific DC</title><link>https://www.infopathdev.com:443/forums/thread/34106.aspx</link><pubDate>Tue, 11 Nov 2008 13:37:21 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:34106</guid><dc:creator>ErnestoM</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/34106.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=57&amp;PostID=34106</wfw:commentRss><description>&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;During installation of DBXL, WSSP and the AD Standalone tool you will be prompted to enter the LDAP path. The installer defaults this value to &lt;a&gt;LDAP://DC=domain&lt;/a&gt;. If you need to configure the&amp;nbsp;service later, find&amp;nbsp;the web.config file and change the LDAP Path by changing the value of the ActiveDirectoryPath key: &lt;em&gt;&lt;strong&gt;&amp;lt;add key=&amp;quot;ActiveDirectoryPath&amp;quot; value=&amp;quot;&lt;/strong&gt;&lt;/em&gt;&lt;a&gt;&lt;em&gt;&lt;strong&gt;LDAP://DC=domain&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;em&gt;&lt;strong&gt;&amp;quot; /&amp;gt; &lt;/strong&gt;&lt;/em&gt;More info on AD:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.infopathdev.com/files/folders/others/entry33946.aspx"&gt;http://www.infopathdev.com/files/folders/others/entry33946.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.infopathdev.com/files/folders/web_methods/entry30677.aspx"&gt;http://www.infopathdev.com/files/folders/web_methods/entry30677.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Hope this helps.&lt;/p&gt;</description></item><item><title>Re: Force the AD lookup to a specific DC</title><link>https://www.infopathdev.com:443/forums/thread/34031.aspx</link><pubDate>Sun, 09 Nov 2008 05:58:24 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:34031</guid><dc:creator>Clay Fox</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/34031.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=57&amp;PostID=34031</wfw:commentRss><description>&lt;p&gt;I do not think the AD Web Service has a setting for this unless you restricted the domain. You could contact Qdabra support directly and ask.&lt;/p&gt;
&lt;p&gt;However on the server where the web service is installed you may be able to set the DNS so that it prefers one DC over and another.&amp;nbsp; This is just a guess, but would be where I would look.&lt;/p&gt;</description></item><item><title>Force the AD lookup to a specific DC</title><link>https://www.infopathdev.com:443/forums/thread/33965.aspx</link><pubDate>Thu, 06 Nov 2008 20:26:49 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:33965</guid><dc:creator>ek38</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/33965.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=57&amp;PostID=33965</wfw:commentRss><description>&lt;p&gt;We have 2-3 domain controllers active in our organization.&amp;nbsp; Can we force the GetMyUserInfo to access a specific DC.&amp;nbsp; When we involked the call it was taking 15-20 seconds to return.&amp;nbsp; One of our theories is that the call was was accessing our DC in the&amp;nbsp;Texas facility which has a slow connection to corporate. &lt;/p&gt;</description></item></channel></rss>