Getting a really strange issue at the moment. We have 2 HP LaserJet M3035's in the main part of our office. People use these for scanning to email etc through the day. For the last few weeks for only a few minutes every couple of hours the printers will hang trying to establish a connection to the exchange server. Same issue is occurring when i try to email sql job reports from another server. About 3 or 4 connections under the edgetransport process open from the exchange server to the SQL server but the email never arrives. The tracking logs show no record of the email existing and the SMTP protocol logs show no activity during this time either. I set up a script to send myself an email every 5 minutes last night and there was 14 noticable breaks where no emails were received and there is no activity in the SMTP logs. Does anyone have any idea what is happening? Friskee

On Tue, 5 Mar 2013 00:29:09 +0000, Friskeee wrote: > > >Getting a really strange issue at the moment. > >We have 2 HP LaserJet M3035's in the main part of our office. People use these for scanning to email etc through the day. For the last few weeks for only a few minutes every couple of hours the printers will hang trying to establish a connection to the exchange server. Same issue is occurring when i try to email sql job reports from another server. About 3 or 4 connections under the edgetransport process open from the exchange server to the SQL server but the email never arrives. The tracking logs show no record of the email existing and the SMTP protocol logs show no activity during this time either. > >I set up a script to send myself an email every 5 minutes last night and there was 14 noticable breaks where no emails were received and there is no activity in the SMTP logs. > > > > > >Does anyone have any idea what is happening? If the transport service hasn't stopped then you'll have to resort to using a network monitor (e.g. wireshark) to capture the network traffic for SMTP. If the network monitor doesn't show the connection then you can look to your network for the problem. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Found an article which said to set the MaxAcknowledgementDelay on the receive connector to 0 http://paulroman.pras.ro/2012/04/applications-are-unable-to-send-emails.html So i ran "C:\Windows\system32>Set-ReceiveConnector "ConnectorName" -MaxAcknowledgementDelay 00:00:00" I was getting Tarpit messages in the protocol logs and they have now stopped and mail seems to be flowing fine. If this does fix the issue what I can't understand is why this has happened now and never befor. Friskee

On Tue, 5 Mar 2013 05:58:25 +0000, Friskeee wrote: > > >Found an article which said to set the MaxAcknowledgementDelay on the receive connector to 0 > >http://paulroman.pras.ro/2012/04/applications-are-unable-to-send-emails.html > >So i ran "C:\Windows\system32>Set-ReceiveConnector "ConnectorName" -MaxAcknowledgementDelay 00:00:00" > >I was getting Tarpit messages in the protocol logs and they have now stopped and mail seems to be flowing fine. But you said ". . . and the SMTP protocol logs show no activity . . ..". If you'd have divuldged that information you would have received a better answer. >If this does fix the issue what I can't understand is why this has happened now and never befor. A better question to ask is why the SMTP client software assumes that it will never have to deal with a transient error! --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

This hasn't fixed the error. My test emails have stopped flowing and now I can't get a response from my exchange server on port 25 at all.Friskee

On Wed, 6 Mar 2013 00:47:43 +0000, Friskeee wrote: >This hasn't fixed the error. My test emails have stopped flowing and now I can't get a response from my exchange server on port 25 at all. What is it you're trying to acomplish? I don't think the "-MaxAcknowledgementDelay" is adjusting what you think it is. You should put it back to 00:00:30. http://technet.microsoft.com/en-us/library/hh529935(v=exchg.141).aspx If it's the delay in response to commands, you should be adjusting "-TarpitInterval" to 00:00:00. Either way, those parameters should have no effect on your ability to connect to the receive connector. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I was trying to eliminate the tarpitting as the cause of the issue. The issue sounded like was caused by back pressure but there are no back pressure events in the event log. It just accepts connection for X amount of time and then stops for Y amount of time.Friskee

I was trying to eliminate the tarpitting as the cause of the issue. The issue sounded like was caused by back pressure but there are no back pressure events in the event log. It just accepts connection for X amount of time and then stops for Y amount of time.Friskee

Turned out to be the AV. Had disabled it before but it needed to be uninstalled.Friskee