I have run those 2 commands and the output from both look ok to the
untrained eye!
 
I have enabled protocol logging on the send and receive connectors to
verbose but I am only getting log files in the SmtpReceive directory.
 
There is nothing in the queues on the Exchange 2003 servers and the log
files are showing the odd smtp communication between the 2 servers
similar to:
2010-08-25 14:06:31 192.168.1.13 192.168.1.3 EHLO -
2010-08-25 14:06:31 192.168.1.13 192.168.1.3 x-exps -
2010-08-25 14:06:31 192.168.1.13 192.168.1.3 x-link2state -
2010-08-25 14:06:31 192.168.1.13 192.168.1.3 MAIL -
2010-08-25 14:06:31 192.168.1.13 192.168.1.3 RCPT -
2010-08-25 14:06:31 192.168.1.13 192.168.1.3 xexch50 -
2010-08-25 14:06:31 192.168.1.13 192.168.1.3 BDAT -
2010-08-25 14:06:31 192.168.1.13 192.168.1.3 QUIT -
 
Regards
 
Andy


________________________________

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: 25 August 2010 14:28
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010 no longer sends email



Get-RoutingGroupConnector | fl

Get-Queue | fl

You also should look at the transport connection logs on the 2010 server
and the queues and smtp logs on the 2003 server(s).

Regards,

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

From: Andy Lawrence [mailto:and...@ansltd.info] 
Sent: Wednesday, August 25, 2010 7:30 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2010 no longer sends email

Hello All (again),

I'm not having much luck with Exchange 20101! Not only does it stop
responding a couple of times a week (see earlier post) but now it has
decided that it doesn't want to send emails.

We have Exchange 2003 and aded a fully patched Exchange 2010 server (vm)
about 2 weeks ago. Since yesterday afternoon people with mailboxes on
the 2010 server send emails but they never get to the recipient. This
includes internal and external emails. 

For some of the emails they sent yesterday they got NDR along the lines
of...

"Delivery is delayed to these recipients or groups:

Anthony Bloke (a.bl...@ourdomain.co.uk)

Subject: FW: should we move to Google Apps

This message hasn't been delivered yet. Delivery will continue to be
attempted.

The server will keep trying to deliver this message for the next 1 days,
19 hours and 57 minutes. You'll be notified if the message can't be
delivered by that time."

The send connector is still there with an address space of * an a cost
of 1. The source server is correct. I have tried deleting the connector
and recreating it.

If I use the queue viewer it does not show anything waiting.

The mail flow troubleshooter doesn't highlight anything either.

The routing log viewer does not even show the send connector on the send
conector tab.

Wireshark does not show any outgoing smtp comunications from the server
/ connector

The server was sending emails successfully and it looks like the problem
started sometime after I restarted the Information store (due to the
problem of the store.exe process taking up all the cpu) Since then I
have rebooted the server as well to see if that helped but it doesn't.

There are 2 other send connectors showing which are the ones on the
Exchange 2003 server. I have renamed them to verify this. On the
Exchange 2010 server they do not have a source server mentioned. 

Andy

 This message has been scanned for viruses by BlackSpider MailControl
<http://www.blackspider.com/> 



Click here
<https://www.mailcontrol.com/sr/hg2hdSptSE3TndxI!oX7UslqkbOixnGdHLHZcali
IYclw0htojMvNpSzZ4DbXEUd4ET7fH0U7WObYw94u+b0NQ==>  to report this email
as spam.

Reply via email to