<?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"
	>
<channel>
	<title>Comments on: SMTP protocol error occurred</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/</link>
	<description></description>
	<pubDate>Fri, 27 Nov 2009 17:39:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: NedK</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/#comment-60346</link>
		<dc:creator>NedK</dc:creator>
		<pubDate>Thu, 26 Feb 2009 08:49:13 +0000</pubDate>
		<guid isPermaLink="false">#comment-60346</guid>
		<description>HI,

I too have run the Exch best practise and the only questionable concern is the network driver updates but as the main NIC is an on-board driver which is running the latest driver software but is over 2 years old. I'm reluctant to purchase a separate NIC. 

I have little doubt the problem only started occurring around the time I installed EXC SP2.

Strange though that after a few weeks of total SMTP mail failures I have now started receiving a few again as it was back in December but they are usually many hours behind. It also appears that a good proportion of the mails are sent during or shortly after a reboot then it hangs again.</description>
		<content:encoded><![CDATA[<p>HI,</p>
<p>I too have run the Exch best practise and the only questionable concern is the network driver updates but as the main NIC is an on-board driver which is running the latest driver software but is over 2 years old. I&#8217;m reluctant to purchase a separate NIC. </p>
<p>I have little doubt the problem only started occurring around the time I installed EXC SP2.</p>
<p>Strange though that after a few weeks of total SMTP mail failures I have now started receiving a few again as it was back in December but they are usually many hours behind. It also appears that a good proportion of the mails are sent during or shortly after a reboot then it hangs again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Technochic</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/#comment-60322</link>
		<dc:creator>Technochic</dc:creator>
		<pubDate>Wed, 25 Feb 2009 15:41:20 +0000</pubDate>
		<guid isPermaLink="false">#comment-60322</guid>
		<description>Definitely update your network card drivers, that's important. And starting with the front end servers is always the best practice with Exchange, although that usually relates to Exchange updates, still it doesn't hurt to start there. As far as the fix, you are correct in that the problem was introduced with server 2003 SP2 and the scalable networking pack, so if your servers do not have server 2003 SP2 then that is not what is causing your issues. If you do update to SP2 then apply all subsequent updates as well to keep this from becoming the problem. Since the Scalable Networking Pack with SP2 is not likely to be your probem I highly recommend you get on a support call with Microsoft about this.</description>
		<content:encoded><![CDATA[<p>Definitely update your network card drivers, that&#8217;s important. And starting with the front end servers is always the best practice with Exchange, although that usually relates to Exchange updates, still it doesn&#8217;t hurt to start there. As far as the fix, you are correct in that the problem was introduced with server 2003 SP2 and the scalable networking pack, so if your servers do not have server 2003 SP2 then that is not what is causing your issues. If you do update to SP2 then apply all subsequent updates as well to keep this from becoming the problem. Since the Scalable Networking Pack with SP2 is not likely to be your probem I highly recommend you get on a support call with Microsoft about this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exchstart</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/#comment-60306</link>
		<dc:creator>Exchstart</dc:creator>
		<pubDate>Wed, 25 Feb 2009 05:58:23 +0000</pubDate>
		<guid isPermaLink="false">#comment-60306</guid>
		<description>Hi Technochic,

                           I downlaoded the fix from the microsoft but not sure whether to install it on our server.In the article it's mentioned that this network compatibility problem occured in Server 2003 sp2 but we have server 2003 sp1 and exchaneg server 2003 sp2 in all our Front end and backend servers. So, do i need to install it in server 2003 sp1.

I have tried using Ex Best pratice analyser to check the issue and i got a warning in front end as our network card drivers are 2 years old and need to be upgraded.Can i do it in front end and check it, will there be any issues ?</description>
		<content:encoded><![CDATA[<p>Hi Technochic,</p>
<p>                           I downlaoded the fix from the microsoft but not sure whether to install it on our server.In the article it&#8217;s mentioned that this network compatibility problem occured in Server 2003 sp2 but we have server 2003 sp1 and exchaneg server 2003 sp2 in all our Front end and backend servers. So, do i need to install it in server 2003 sp1.</p>
<p>I have tried using Ex Best pratice analyser to check the issue and i got a warning in front end as our network card drivers are 2 years old and need to be upgraded.Can i do it in front end and check it, will there be any issues ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IT Knowledge Exchange Community Update for 02/12/09 - ITKE Community Blog</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/#comment-59883</link>
		<dc:creator>IT Knowledge Exchange Community Update for 02/12/09 - ITKE Community Blog</dc:creator>
		<pubDate>Thu, 12 Feb 2009 15:54:50 +0000</pubDate>
		<guid isPermaLink="false">#comment-59883</guid>
		<description>[...] Exchstart [...]</description>
		<content:encoded><![CDATA[<p>[...] Exchstart [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exchstart</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/#comment-59867</link>
		<dc:creator>Exchstart</dc:creator>
		<pubDate>Thu, 12 Feb 2009 06:38:08 +0000</pubDate>
		<guid isPermaLink="false">#comment-59867</guid>
		<description>Hi Robert,

                             Thanks for your support, i will try and get he solution as soon as possible.
Good Luck to you,

Thanks</description>
		<content:encoded><![CDATA[<p>Hi Robert,</p>
<p>                             Thanks for your support, i will try and get he solution as soon as possible.<br />
Good Luck to you,</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Stewart</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/#comment-59847</link>
		<dc:creator>Robert Stewart</dc:creator>
		<pubDate>Wed, 11 Feb 2009 15:03:04 +0000</pubDate>
		<guid isPermaLink="false">#comment-59847</guid>
		<description>Not off the top of my head, I'm sorry I'm really not an email guru, technochic seems to be, she has alot of helpful posts throughout this blog on email. 

My first response to this post was due to your problem was very similar to a problem I had with an exchange server, same issues being described, and mine was my exchange server was out of space! It was weird, if I rebooted it would buy me 48 hours of time before the queue locked up again.

Have you called Microsoft?? That would be my next step if Technochic cannot help. Again I'm sorry and I feel your pain, nothing like having faulty email program. Keep your head up someone has your answer.</description>
		<content:encoded><![CDATA[<p>Not off the top of my head, I&#8217;m sorry I&#8217;m really not an email guru, technochic seems to be, she has alot of helpful posts throughout this blog on email. </p>
<p>My first response to this post was due to your problem was very similar to a problem I had with an exchange server, same issues being described, and mine was my exchange server was out of space! It was weird, if I rebooted it would buy me 48 hours of time before the queue locked up again.</p>
<p>Have you called Microsoft?? That would be my next step if Technochic cannot help. Again I&#8217;m sorry and I feel your pain, nothing like having faulty email program. Keep your head up someone has your answer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exchstart</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/#comment-59837</link>
		<dc:creator>Exchstart</dc:creator>
		<pubDate>Wed, 11 Feb 2009 05:42:51 +0000</pubDate>
		<guid isPermaLink="false">#comment-59837</guid>
		<description>Hi Robert,

                         I have not tested the telnet thing when the mails got stuck, coz it happens in the working hours and users will suffer if they did not get mails, so i just restarted the server as soon as possible.
But any how i will try the telnet next time.

Could you tell what will be problem if the telnet does not work?

Thanks</description>
		<content:encoded><![CDATA[<p>Hi Robert,</p>
<p>                         I have not tested the telnet thing when the mails got stuck, coz it happens in the working hours and users will suffer if they did not get mails, so i just restarted the server as soon as possible.<br />
But any how i will try the telnet next time.</p>
<p>Could you tell what will be problem if the telnet does not work?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Stewart</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/#comment-59814</link>
		<dc:creator>Robert Stewart</dc:creator>
		<pubDate>Tue, 10 Feb 2009 15:55:23 +0000</pubDate>
		<guid isPermaLink="false">#comment-59814</guid>
		<description>Have you tried what the Knoweldge Base says regarding testing via telnet??

"For additional information that may help you resolve this problem, see Microsoft Knowledge Base article 153119, XFOR: Telnet to Port 25 to Test SMTP Communication."

I would try and test when email is piling up in that queue, just a thought and sorry you have not gotten anywhere with this problem, If you have problems with the telnet test it is probably the mail server setup.

Hope this helps</description>
		<content:encoded><![CDATA[<p>Have you tried what the Knoweldge Base says regarding testing via telnet??</p>
<p>&#8220;For additional information that may help you resolve this problem, see Microsoft Knowledge Base article 153119, XFOR: Telnet to Port 25 to Test SMTP Communication.&#8221;</p>
<p>I would try and test when email is piling up in that queue, just a thought and sorry you have not gotten anywhere with this problem, If you have problems with the telnet test it is probably the mail server setup.</p>
<p>Hope this helps</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NedK</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/#comment-59798</link>
		<dc:creator>NedK</dc:creator>
		<pubDate>Tue, 10 Feb 2009 10:27:11 +0000</pubDate>
		<guid isPermaLink="false">#comment-59798</guid>
		<description>Hi,

While the additional diagnostics might give a clue I find it difficult to believe it's a potential NIC card software/driver issue.

I run SBS which obviously runs a number of applications on the same server inc ISA. At no time do i suffer any other network interface issues it's only emails sent directly via the exchange server that I have a specific issue with. I can in fact quite happily send emails via works stations using POP3 via the SBS/exchange server, it's only SMTP that appears to have the issue.

I'm assuming people here are using email ISP's other than BT as I've been experiencing a number of  other email issues with their service for several months.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>While the additional diagnostics might give a clue I find it difficult to believe it&#8217;s a potential NIC card software/driver issue.</p>
<p>I run SBS which obviously runs a number of applications on the same server inc ISA. At no time do i suffer any other network interface issues it&#8217;s only emails sent directly via the exchange server that I have a specific issue with. I can in fact quite happily send emails via works stations using POP3 via the SBS/exchange server, it&#8217;s only SMTP that appears to have the issue.</p>
<p>I&#8217;m assuming people here are using email ISP&#8217;s other than BT as I&#8217;ve been experiencing a number of  other email issues with their service for several months.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exchstart</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/smtp-protocol-error-occurred/#comment-59769</link>
		<dc:creator>Exchstart</dc:creator>
		<pubDate>Mon, 09 Feb 2009 06:02:11 +0000</pubDate>
		<guid isPermaLink="false">#comment-59769</guid>
		<description>Hi guys,

                I enabled all the options in Diagnosting Logging and find the event id when the error occurs.
Its Event ID 7002 :Smtp Protocol and it says,

ID 7002 reads: This is an SMTP protocol warning log for virtual server ID 1, connection #1060 The remote host 65.168.34.131, responded to the SMTP command "rcpt" with "451 Requested action aborted:local error in processing". The full command sent was RCPT To:&#60;email address&#62;" This may cause the connection to fail.

I had a search on the MS forum and it says,

To resolve this error, try one or more of the following:

Make sure that the latest network card drivers and firmware are installed. 

Run any network diagnostics software that was supplied with the network cards to verify that the network cards are functioning correctly. 

If the network cards are configured to automatically detect the speed of the connected network, change the configuration to use a specific speed setting. 
For additional information that may help you resolve this problem, see Microsoft Knowledge Base article 153119, XFOR: Telnet to Port 25 to Test SMTP Communication.

Please let me know if you find some other solution for this problem.</description>
		<content:encoded><![CDATA[<p>Hi guys,</p>
<p>                I enabled all the options in Diagnosting Logging and find the event id when the error occurs.<br />
Its Event ID 7002 :Smtp Protocol and it says,</p>
<p>ID 7002 reads: This is an SMTP protocol warning log for virtual server ID 1, connection #1060 The remote host 65.168.34.131, responded to the SMTP command &#8220;rcpt&#8221; with &#8220;451 Requested action aborted:local error in processing&#8221;. The full command sent was RCPT To:&lt;email address&gt;&#8221; This may cause the connection to fail.</p>
<p>I had a search on the MS forum and it says,</p>
<p>To resolve this error, try one or more of the following:</p>
<p>Make sure that the latest network card drivers and firmware are installed. </p>
<p>Run any network diagnostics software that was supplied with the network cards to verify that the network cards are functioning correctly. </p>
<p>If the network cards are configured to automatically detect the speed of the connected network, change the configuration to use a specific speed setting.<br />
For additional information that may help you resolve this problem, see Microsoft Knowledge Base article 153119, XFOR: Telnet to Port 25 to Test SMTP Communication.</p>
<p>Please let me know if you find some other solution for this problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->