Cannot send to one of my domains (NDR 4.4.7)

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Stu Hamilton (stu_at_discussions.microsoft.com)
Date: 06/24/04 

Date: Thu, 24 Jun 2004 08:17:40 -0700

I have two Domains (A&B) in a trusted enviroment over a
slow WAN. Both
originally had exchange servers. I have recently moved
Domain B over to a Web based solution and got rid of
their Exchange box. Now, when ever I try to email them
from Domain A, I get NDR's (4.4.7). Domain B can email
Domain A fine.
I have tried putting an MX record into DNS ... with no
luck. I even tried creating a Connector inside exchange,
again no luck.
I know I am missing something simple ... but cannot think
what .. please help

Thanks ... Stu ;-)

Relevant Pages

  • Re: SBS2k -> SBS03 Upgrade Problems
    ... I have had no luck at all ... ... Thought of renaming and pulling off of the media in ... > did Exchange. ... > installation/upgrade ... ...
    (microsoft.public.windows.server.sbs)
  • Problem connecting to Exchange 2000 server with Outlook 2002
    ... that will help me troubleshoot and authentication problem. ... made on the server where Exchange is installed and only logs for WMI ... with no luck. ...
    (microsoft.public.outlook.general)
  • Re: CreateMailbox
    ... Thank you for your continued help and support Siegfried...but I'm still ... I've been trying again, pretty much all day, and am having no luck at all. ... Exchange Management ... > If you want a smart answer, ask a smart question ...
    (microsoft.public.exchange2000.development)
  • IMS queues when Outlook client sends email but sends fine with OWA???
    ... No luck. ... installed/moved the IMS to the nt4. ... telnet remotely to my exchange port 25 in the w2k side and sent out an email using the HELO transaction. ... The NT4 is a backup. ...
    (microsoft.public.cert.exam.mcse)
  • Re: HELP!!! RPC OVER HTTP OULOOK PROBLEM
    ... > completing all these steps I am still unable to get into outlook from ... It works fine internally but no luck from the outside. ... Make sure you have access to the network and the exchange ... > Unable to contact the MS exchange server. ...
    (microsoft.public.windowsxp.accessibility)