We have being running a single Exchange 2000 server, hosting its own mail domain, without problems for some time. It has been the only server in the organisation.
MX records for the mail domain point only to this E2K server. It relays outbound smtp via a smarthost (UNIX). We recently installed a clustered Exchange 2003 server and 2 front end servers into the organisation. All servers are in the one, default Routing Group. The E2K server is the master. The E2K3 cluster plus 2 front end serves are members. The problem is that when a mailbox is moved from the E2K server to the E2K3 cluster, SMTP mail for that mailbox from outside the organisation is not delivered to the mailbox. What has happened is that the E2K server has created an SMTP queue for delivery to the E2K3 cluster but messages are being rejected. This is confirmed by the Event Log message - Event Id 4000 - The connection was dropped by the remote host On the E2K3 cluster I have explicitly allowed the E2K server to relay though the E2K3 SMTP virtual server but it made no difference. Forcing the relevant queue on the E2K server still fails to have the relevant messages accepted by the E2K3 cluster. The issue of message routing within an organisation in such an apparently simple scenario as ours does not appear to have merited much discussion in any of the obvious sources so I would imagine there is a simple fix that I have overlooked ? Thanks. Alastair Morrison IT Services Strathclyde University UK --------------------------------------------- [EMAIL PROTECTED] Strathclyde University Glasgow UK _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
