 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Exchange 2k3 and AD Communication failure</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/exchange-2k3-and-ad-communication-failure/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-2k3-and-ad-communication-failure/</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 05:05:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: amehsys</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-2k3-and-ad-communication-failure/#comment-43908</link>
		<dc:creator>amehsys</dc:creator>
		<pubDate>Thu, 03 May 2007 07:47:44 +0000</pubDate>
		<guid isPermaLink="false">#comment-43908</guid>
		<description><![CDATA[Dear all,
it&#039;s  resolved. There were issues with the Broadcom Network cards on the Dell servers and Dell happily ignore the fact that there&#039;s a problem.

We had to change the cards. 

]]></description>
		<content:encoded><![CDATA[<p>Dear all,<br />
it&#8217;s  resolved. There were issues with the Broadcom Network cards on the Dell servers and Dell happily ignore the fact that there&#8217;s a problem.</p>
<p>We had to change the cards. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bigfella</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-2k3-and-ad-communication-failure/#comment-43909</link>
		<dc:creator>bigfella</dc:creator>
		<pubDate>Thu, 26 Apr 2007 05:01:41 +0000</pubDate>
		<guid isPermaLink="false">#comment-43909</guid>
		<description><![CDATA[Looking at the errors specfied in the MS article, I would suggest looking at the following: Using the Exchange server manager MMC check the properties of the exchange server (at the server level) on the &quot;Directory Access&quot; tab and ensure that the &quot;Automatically discover servers&quot; option is set, it may be that this option has been disabled and de-commissioned server(s) have been manually specified have been set causing the errors described.]]></description>
		<content:encoded><![CDATA[<p>Looking at the errors specfied in the MS article, I would suggest looking at the following: Using the Exchange server manager MMC check the properties of the exchange server (at the server level) on the &#8220;Directory Access&#8221; tab and ensure that the &#8220;Automatically discover servers&#8221; option is set, it may be that this option has been disabled and de-commissioned server(s) have been manually specified have been set causing the errors described.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.026 seconds using memcached
Object Caching 281/287 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-22 10:23:43 -->