New IMS connector acts differently from old

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: George (anonymous_at_discussions.microsoft.com)
Date: 05/27/04 

Date: Thu, 27 May 2004 12:42:27 -0700

Hello there.

I have one Exchange server (5.5 w/ SP4) in my site.
We'll call it exchOLD. I've installed a second Exchange
server (exchNEW) with the intention of replacing the old
one with the new one (different server name).

I've managed (as per the Ed Crowely method) to move all
mailboxes, folders, connectors, etc from exchOLD to
exchNEW and am now ready to soon decommision exchOLD ...
except for one thing: the IMS connector.

Currently, outbound Internet email (from MAPI clients)
doesn't actual touch the IMS queue ... it sent out by our
Headoffice's Exchange server (in a different site). This
is due to way the cost of the routes are setup (ie. it
costs 3 hops thru our IMS but 2 thru our Headoffice
IMS). The Headoffice IMS also receives our inbound (from
the Internet) email and passes it onto our Exchange
Server. This is the way we want it to work (our Exchange
Server doesn't have to poke thru the firewall).

Further, we have a couple of Unix boxes that connect
directly to our Exchange server (exchOLD) via SMTP to
send outbound Internet email. This also works fine.

The problem:

I've configured a new IMS connector on exchNEW and copied
over all the settings from the old IMS connector
(exchOLD). I've also set its cost to 3. Unfortunately,
when our Unix boxes SMTP to exchNEW, the email remains
stuck in the outbound queue, rather than bypassing it and
heading on out thru our Headoffice site (like it does
when using exchOLD).

I've re-calcd the routing, started and stopped both IMS
connectors, waited a couple of days for things to settle
down but:

- when SMTPing directly to exchNEW, mail gets stuck in
the queue whereas SMTPing to exchOLD, mail gets sent.

I can't remove exchOLD->IMS Connector until exchNEW->IMS
Connector is working.

Any ideas?

Thanks,
George.

Relevant Pages

  • OWA... Cant get it to work.
    ... Do you install iis together with the exchange server in ... with the Microsoft Outlook Web Access components that are ... Microsoft Exchange Server ...
    (microsoft.public.exchange.misc)
  • RE: Catchall not working, EXTERNALLY?
    ... Exchange server 2003 supports multiple clients, such as OWA, MAPI ... Microsoft CSS Online Newsgroup Support ... When I open the connection (over internet) to my exchange account, ...
    (microsoft.public.windows.server.sbs)
  • RE: Catchall not working, EXTERNALLY?
    ... Microsoft CSS Online Newsgroup Support ... but we will start using the exchange server fully ... When I open the connection (over internet) to my exchange account, ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 SBS #4.4.7 NDR TO OUR SERVER
    ... SP1/SP2 can be applied all exchange 2003 server. ... This newsgroup only focuses on SBS technical issues. ... Pack 2) when looking at the properties of the exchange server in system ... I can send you the SMTP log but there is no entry for the incoming ...
    (microsoft.public.windows.server.sbs)
  • [NT] Vulnerability in Exchange Server 2003 Could Lead to Privilege Escalation (MS04-002)
    ... Access on Windows 2000 and Windows Server 2003, ... back-end Exchange 2003 servers that are running Windows Server 2003. ... Kerberos authentication is used as the HTTP authentication ... Windows Server 2003 server that also functions as an Exchange Server 2003 ...
    (Securiteam)