Home > Ask the Microsoft Exchange Experts > Archive: Lee Benjamin -- Deployment and Migration Questions & Answers > Exchange rerouting and configuration issues
Ask The Exchange Expert: Questions & Answers
EMAIL THIS

Exchange rerouting and configuration issues

Lee Benjamin EXPERT RESPONSE FROM: Lee Benjamin

Pose a Question
Other Exchange Categories
Meet all Exchange Experts
Become an Expert for this site


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


>
QUESTION POSED ON: 24 March 2004
I have completed the my migration from Exchange 5.5 to Exchange 2000 and have finished almost everything except for the rerouting of outgoing internet e-mail and the removal of the last 5.5 server.

I was told by someone much more knowledgable than I that I could get around installing an SMTP Connector in Exchange 2000 by simply configuring the Default SMTP Virtual server's external DNS addresses to point to my ISP's DNS servers. Which is the way I had it setup on my Exchange 5.5 server. Are there any potential problems with doing it this way?

I also wanted to ask about the removal of the Exchange 5.5 IMS connector. According to knowledgebase article Q316886, all I have to do to reroute the outgoing mail is to delete the IMS and then make sure that the connection agreement in the ADC replicates the change. This seems a bit simple to me. Does this mean that with the IMS gone my Exchange 2000 server will automatically know to look at the Default SMTP Virtual server for outgoing delivery.


>
EXPERT RESPONSE
Yes, you could get away without an SMTP Connector in your Exchange 2000 (or 2003) environment. The SMTP Virtual Server provides the base functionality you need to send and receive SMTP messages. However, without an SMTP Connector, each Exchange server would send messages directly to the Internet. By installing a first SMTP Connector, the Link State Routing Table tells each other server that there is a 'specified' route out of the system to the Internet. The SMTP Virtual Servers on each Exchange server will no longer send directly to the Internet. From a routing point of view, this is probably what you want. You will also find that you have more control over an SMTP Connector if needed. This simplifies your second question. When the IMS is gone, there will only be one path out from your Exchange system to the Internet, through your new SMTP Connector. You could also make the cost of your IMS higher than the SMTP Connector as a first step, thereby preserving the ability to revert if necessary.


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


RELATED CONTENT
Archive: Lee Benjamin -- Deployment and Migration
Exploring Exchange 2003 features
Exchange 2003 migration best practices
Importing e-mails without third-party software
Importing distribution lists
Exchange 5.5 moving methods
Exchange Server 2000/2003 migration worries
Ghost e-mails
POP3 problems
Moving Exchange Server
Migrating the Exchange server to a new domain

Microsoft Exchange Server 5.5
Migrating mailboxes from Exchange Server 5.5 to Windows SBS 2003
Remove Exchange 5.5 servers from a mixed mode Exchange environment
Solve server problems with the Exchange Troubleshooting Assistant tool
Best approaches for upgrading Exchange 5.5 to Exchange 2000 or 2003
Sharing free/busy calendar information between disparate Exchange 5.5 and Exchange 2003 organizations
Can we install another instance of Exchange Server on a second domain controller?
Connecting an Exchange 5.5 server to a new domain controller
Duplicating Exchange 5.5 Global Address views in Exchange Server 2003
Importing an Exchange 5.5 Global Address List into Exchange 2003 Active Directory
Is it safe to upgrade directly from Exchange 5.5 to Exchange Server 2003?
Microsoft Exchange Server 5.5 Research

Microsoft Exchange 2000 Server
Error 1053: Exchange System Attendant service could not start
Solve server problems with the Exchange Troubleshooting Assistant tool
Move mailboxes to Exchange 2007 after Windows upgrade
Third-party tools that modify NDRs for oversized email
IP address changes for an Exchange 2000 recovery server
Exchange Server 2003 tips and tricks -- 7 tips in 7 minutes
How to enable Exchange Server public folder logging
Deciphering an 0xc103798a Exchange Server setup error code
Exchange Server error message: 'A non-delivery report with a status code of 5.4.0 was generated for recipient'
New Exchange Server installation not receiving SMTP or POP3 email
Microsoft Exchange 2000 Server Research

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
E2K  (SearchExchange.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary



Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice

HomeNewsTopicsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT Downloads
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 2004 - 2008, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts