>Thanks so much for the quick reply.
>Here is a breakdown of what you asked for.
>1. I'll start with the last question first, my
>organization breaks down like this. I have 2 Exchange
>Servers one is standard the new one is Enterprise. I have
>1 primary DC which isn't on the old exchange server but
>the old exchange server does act as a DC. The old
>server is running SP2 and the new Enterprise exchange
>server is running SP3. I would upgrade he old exchange
>server but its in a state right now where i don't really
>want to mess with it.
>2. I have sent you the Winroute information, and the
>app.evt info as well. I sent winroute info from both
>3. I do not receive any NDR's. The only NDR's i am
>receiving are delay messages.
>4. The emails that are queued are those that try and go
>between servers. I created 2 more accounts on the new
>server, when i mailed from A to B it worked fine when i
>mailed from B to C worked fine and from C to A worked
>as well. But from A to D or from D to B, they got stuck
>the opposite server queues. As well as with the "Server"-
>IS mails as well. Sending mail outside the organization
>works fine. Sending mail to the box's on the new server
>from outside does not work. This is mainly because we use
>a forwarder q-mail server which forwards all mail to the
>5. The names of the queues are as follows where the mail
>The properties page shows "the connection was dropped by
>the remote host.
>Any help you have with this issue is much appreciated.
>>Thank you for requesting support for Exchange 2000
>>To provide you with a more accurate answer, would you
>please help me
>>collect the following information? I appreciate your
>>1. Please check the Queue again.
>>Run Exchange System Manager and then expand the SMTP
>virtual server. Please
>>let me know which queue the email is in. In addition,
>please check the
>>property of the queue and let me know the exact
>>2. Please let me know what emails are queued. Does the
>problem occur when
>>you send emails to the internal users which are in the
>>Server? Does the problem occur when you send emails to
>ourside of your
>>Exchange Server? Let us try the following tests:
>>- Please create two Users on the new Exchange server: A
>and B. I assume
>>that you move User C from the old Exchange Server and
>there is another User
>>D on the old Exchange Server.
>>- Does the problem occur when you send from A to B? Does
>it happen when A
>>sends to himself?
>>- Does the problem occur when you send from A to C or
>from C to A?
>>- Does the problem happen when sending from A to D?
>>- Does it happen when sending from C to D?
>>- Does it happen when sending from D to A or C?
>>3. Please enable the Diagnostic Logging.
>>a. Open the Registry Editor
>>b. Navigate to the HKEY_LOCAL_MACHINE\System\Current
>>c. After copying down the values of all items in
>Diagnostics, set all items
>>(except for the default item) to a value of 7
>>d. In the Services applet, stop the Simple Mail
>>e. Restart the Microsoft Exchange Routing Engine Service
>>f. Start the Simple Mail Transport Protocol (SMTP)
>>Please send an email again, save the Application Log
>as .evt file and send
>>it to me for reference.
>>4. Do you receive any NDRs? If so, please save them
>to .msg files and send
>>them to me for reference.
>>5. In addition, I suggest you read the following
>>article which has the very detailed troubleshooting
>method on this issue.
>>Would you please let me know the testing results when
>>281800 XCON: Troubleshooting Message Failures in
>>6. I would appreciate it if you can describe your
>Exchange organizations in
>>more detail. For example, how many Exchange Servers are
>there? What are
>>their versions and service pack levels?
>>7. Please use WinRoute on the problematic Exchange
>to capture the
>>routing information. For more information, please refer
>to the following KB
>>281382 XCON: How to Use the WinRoute Tool
>>Please save the result to .rte file and send it to me
>>I am looking forward to your reply.
>>Microsoft Online Support Engineer
>>Get Secure! - www.microsoft.com/security
>>When responding to posts, please "Reply to Group" via
>>your newsreader so that others may learn and benefit
>>from your issue.
>>This posting is provided "AS IS" with no warranties, and
>confers no rights.