 




<?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 Serv 2k can send but can&#8217;t receive</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/exchange-serv-2k-can-send-but-cant-receive/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-serv-2k-can-send-but-cant-receive/</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 07:13:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: mhelal</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-serv-2k-can-send-but-cant-receive/#comment-42090</link>
		<dc:creator>mhelal</dc:creator>
		<pubDate>Mon, 24 Jan 2005 20:45:06 +0000</pubDate>
		<guid isPermaLink="false">#comment-42090</guid>
		<description><![CDATA[Hi petroleumman  and all

When I fist done the previous changes, it delayed the sending outside, but then it successfuly sent, but after a while it stopped sending at all, and return delivery failure messages to all domains I am trying to send to.

As you said, I pinged the domain for the mail servers I am sending to, and they are reachable, I send my ISP dns servers, and they reply back, and I removed any local dns servers, and restarted the server, and the problem persists, 

Will you or anyone gove more ideas to trouble shoot this one, thank you very much for your help, 

Manal]]></description>
		<content:encoded><![CDATA[<p>Hi petroleumman  and all</p>
<p>When I fist done the previous changes, it delayed the sending outside, but then it successfuly sent, but after a while it stopped sending at all, and return delivery failure messages to all domains I am trying to send to.</p>
<p>As you said, I pinged the domain for the mail servers I am sending to, and they are reachable, I send my ISP dns servers, and they reply back, and I removed any local dns servers, and restarted the server, and the problem persists, </p>
<p>Will you or anyone gove more ideas to trouble shoot this one, thank you very much for your help, </p>
<p>Manal</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: petroleumman</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-serv-2k-can-send-but-cant-receive/#comment-42091</link>
		<dc:creator>petroleumman</dc:creator>
		<pubDate>Fri, 31 Dec 2004 08:17:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-42091</guid>
		<description><![CDATA[Good Morning,

Under the &#039;Advanced Delivery&#039; tab - Configure External DNS, you want to list ONLY addresses to your external DNS hosts (where your public MX records reside). Do Not include ip&#039;s which point to your AD DNS source. You want to keep AD DNS and public DNS seperate. Be sure to include the addresses for redundant servers as well. Your ISP or DNS host will provide you a list of the primary and all secondary servers. Also, make sure you have an entry listed in the &#039;Fully Qualified Domain Name&#039; field as well. You can click the &#039;Check DNS&#039; button to confirm that your entry is valid.  

Exchange 2000 or 2003 does not require a reboot after changes but should you experience a lag in your delivery time after making changes, it dosen&#039;t hurt to stop and start the SMTP service to force a refresh or even reboot the entire server. 

If you still have latency issues and feel you have configured your server correctly,compare the delivery time between internal mail and external (internet mail). If your problem is with the internet mail only, ping the external DNS servers and check your response times. If your getting time outs or delayed response, contact your DNS host as they may be having an issue. 

Good Luck!  ]]></description>
		<content:encoded><![CDATA[<p>Good Morning,</p>
<p>Under the &#8216;Advanced Delivery&#8217; tab &#8211; Configure External DNS, you want to list ONLY addresses to your external DNS hosts (where your public MX records reside). Do Not include ip&#8217;s which point to your AD DNS source. You want to keep AD DNS and public DNS seperate. Be sure to include the addresses for redundant servers as well. Your ISP or DNS host will provide you a list of the primary and all secondary servers. Also, make sure you have an entry listed in the &#8216;Fully Qualified Domain Name&#8217; field as well. You can click the &#8216;Check DNS&#8217; button to confirm that your entry is valid.  </p>
<p>Exchange 2000 or 2003 does not require a reboot after changes but should you experience a lag in your delivery time after making changes, it dosen&#8217;t hurt to stop and start the SMTP service to force a refresh or even reboot the entire server. </p>
<p>If you still have latency issues and feel you have configured your server correctly,compare the delivery time between internal mail and external (internet mail). If your problem is with the internet mail only, ping the external DNS servers and check your response times. If your getting time outs or delayed response, contact your DNS host as they may be having an issue. </p>
<p>Good Luck!  </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mhelal</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-serv-2k-can-send-but-cant-receive/#comment-42092</link>
		<dc:creator>mhelal</dc:creator>
		<pubDate>Fri, 31 Dec 2004 00:01:46 +0000</pubDate>
		<guid isPermaLink="false">#comment-42092</guid>
		<description><![CDATA[no, it just took too long to send, I received email from the administrator@testdomain.com; I am still testing the remaining users, 

thank you again, 

]]></description>
		<content:encoded><![CDATA[<p>no, it just took too long to send, I received email from the <a href="mailto:administrator@testdomain.com">administrator@testdomain.com</a>; I am still testing the remaining users, </p>
<p>thank you again, </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mhelal</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-serv-2k-can-send-but-cant-receive/#comment-42093</link>
		<dc:creator>mhelal</dc:creator>
		<pubDate>Thu, 30 Dec 2004 23:39:22 +0000</pubDate>
		<guid isPermaLink="false">#comment-42093</guid>
		<description><![CDATA[Thank you so much, 

the first solution was already there, and the second solution solved the receiving problem, now I can receive on this server, but I couldn&#039;t remember the change that I have done, and disabled the sending now :) it sounds funny, 

I think I just added in the configure button (in the smtp virtual server properties - delivery tab, clicking on advanced, then clicking on configure), external dns addresses as given to us by the domain registration company + out local dns ips,

thanks you for your help, ]]></description>
		<content:encoded><![CDATA[<p>Thank you so much, </p>
<p>the first solution was already there, and the second solution solved the receiving problem, now I can receive on this server, but I couldn&#8217;t remember the change that I have done, and disabled the sending now <img src='http://itknowledgeexchange.techtarget.com/itanswers/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  it sounds funny, </p>
<p>I think I just added in the configure button (in the smtp virtual server properties &#8211; delivery tab, clicking on advanced, then clicking on configure), external dns addresses as given to us by the domain registration company + out local dns ips,</p>
<p>thanks you for your help, </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: petroleumman</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-serv-2k-can-send-but-cant-receive/#comment-42094</link>
		<dc:creator>petroleumman</dc:creator>
		<pubDate>Thu, 30 Dec 2004 15:06:35 +0000</pubDate>
		<guid isPermaLink="false">#comment-42094</guid>
		<description><![CDATA[Hi,

If you&#039;ve tried the above advice and assigned a recipient policy to the domain and still are getting your error, take a look at the Relay Restrictions tab (Exchange Systems Manager -&gt; Administrative Groups -&gt; Exchange Domain -&gt; Servers -&gt; Your Servername -&gt; Protocols -&gt; SMTP -&gt; Virtual Server) right click your virtual server and choose Properties, click the Access tab and click the Relay button. Make sure you have the &quot;Allow all computers which successfully authenticate to relay regardless of the list above.&quot; option checked. It is a good idea while your there to make sure you have the &quot;Only the List Below&quot; radio button checked under &quot;Select Which Computers may Relay Through This Virtual Server&quot; section and have your Exchange server&#039;s IP address listed and Access Granted displayed. This will lock your server down preventing it from being used as an open relay. This should resolve your problem.

Good Luck!]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>If you&#8217;ve tried the above advice and assigned a recipient policy to the domain and still are getting your error, take a look at the Relay Restrictions tab (Exchange Systems Manager -&gt; Administrative Groups -&gt; Exchange Domain -&gt; Servers -&gt; Your Servername -&gt; Protocols -&gt; SMTP -&gt; Virtual Server) right click your virtual server and choose Properties, click the Access tab and click the Relay button. Make sure you have the &#8220;Allow all computers which successfully authenticate to relay regardless of the list above.&#8221; option checked. It is a good idea while your there to make sure you have the &#8220;Only the List Below&#8221; radio button checked under &#8220;Select Which Computers may Relay Through This Virtual Server&#8221; section and have your Exchange server&#8217;s IP address listed and Access Granted displayed. This will lock your server down preventing it from being used as an open relay. This should resolve your problem.</p>
<p>Good Luck!</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 6/9 queries in 0.020 seconds using memcached
Object Caching 328/331 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-24 09:24:52 -->