Re: Exchange 2007 - conversation with [exchange2007] timed out while receiving the initial server greeting

I've not heard of too many nasty problems with SP2. But I have no knowledge of anything it contains that might fix your problem.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"Brian Searle" <spam@xxxxxxxxxxxxxx> wrote in message news:e$2TG1NMKHA.3992@xxxxxxxxxxxxxxxxxxxxxxx
If only I was that lucky!!

Seriously though, I feel that it will recur and I really don't like the idea of not knowing what actually fixes a problem.

I am researching the SP2 for Exchange 2007 at present. I have it downloaded ready for install, but will wait til I have had a real good look at the release notes before going ahead with that.

What is your opinion of installing the SP2? We already have the Server 2008 SP2 installed, so the pre-req's are there to begin with.

Thanks again

Brian


"Ed Crowley [MVP]" <curspice@xxxxxxxxxx> wrote in message news:u1sC4uNMKHA.1312@xxxxxxxxxxxxxxxxxxxxxxx
Good luck! Of course, what will probably happen is that it won't fail again so you'll assume that logging fixed it!
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.

"Brian Searle" <spam@xxxxxxxxxxxxxx> wrote in message news:eJuBApNMKHA.5192@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for the response. I have just enabled the verbose protocol logging, and disabled the scheduled service restart. I will have to wait and see if it stalls again. If it does, I will post results here.

Thanks for the tip also about the multiple newsgroup posting.


"Ed Crowley [MVP]" <curspice@xxxxxxxxxx> wrote in message news:%23B0TK1MMKHA.4964@xxxxxxxxxxxxxxxxxxxxxxx
Have you turned up protocol logging? Perhaps you might get some idea of what's going on and come up with a reproduceable sequence.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.

"Brian Searle" <spam@xxxxxxxxxxxxxx> wrote in message news:u366GuMMKHA.220@xxxxxxxxxxxxxxxxxxxxxxx
We have just transitioned from Exchange server 2003 to Exchange server 2007 in our environment.

The process had a few hiccups along the way, but is is running. Our LAN clients connect and receive email. Our "Outlook Anywhere" clients connect without issue. OWA is accessible and functions fine.

The one issue we have is that we seem to get a lockup of the Microsoft Exchange Transport service. The service does not stop, according to Task Manager and the Services console. But our upstream SMTP gateway reports that "conversation with [exchange2007] timed out while receiving the initial server greeting". The SMTP gateway continues to queue the email and defer delivery. The only way to restart email flow is to restart the Microsoft Exchange Transport service and force delivery again from the SMTP gateway.

The configuration is a NetboxBlue firewall/SMTP gateway at the network boundary and the Exchange Server 2007 behind that. The NetboxBlue performs spam and virus filtering, before forwarding the email to the Exchange 2007 server. The logging in the Netbox confirms that inbound emails are received, and queued for deferred delivery. This has been happening since we went live on the Exchange 2007 server. We encountered nothing like this with the previous Exchange 2003 server.

I have browsed for possible answers on the web. I have already disabled the TCP auto-tuning on the 2008 Server where Exchange 2007 is installed. I have aslo increased the receive connector timeout value up to first 15 minutes, and now 20 minutes. The email delivery can go for days without issue, and then totally stop flow in and outbound. I have temporarily worked around this by scheduling a restart of the Microsoft Exchange Transport service once each day. But there has to be a better way to really fix this.

Other possible causes I have seen that might be related to this issue include firmware version of routers and firewalls., antivirus or internet security software, Intrusion prevention system settings. We have the latest firmware available, I have tested with the AVG antivirus and anti-spam disabled, and the IPS settings on the Netbox are set to allow the TLS through.

Has anybody else encountered this?? Does anybody else have any clues as to the cause/

Many thanks in advance

Brian








.

Loading