Merge 2 networks problem with Exchange 2003

Hello I'm in kind of a situation here.

I've 2 Networks that I'm going to join.
Network 1 consists of a SBS server with Exchange for domain A.
Network 2 consists of several servers 2003 R2 including also an Exchange Server installed on the GC
(I know not the best solution and it might even make the solution to my question harder a company called *** first letter is H and last is a B did that for us oh and the middle letter is next to the P)

Physically those 2 networks are now connected by LAN.

All the data is in place and all user accounts / computers are in place except for one thing: Email.

The exchange server in network 2 will be responsible for all email.
(Email is now being deliverd in network 1 to an IP directly pointing to the SBS server!) <== Not Secure!

What is the best way to go?

I thought installing a second NIC on the Exchange server and assign it the same IP as in network 1 would do the trick.
But I'm a bit scared if this will work. Because my DC will become multihomed.
I've enabled DNS to listen only on the internal IP so that should be ok.
I love this solution because it will enable me to switch mail server without having to wait for DNS to update.

Has anyone experience with this kind of setup? or has a much better Idea on how to proceed?

Thanks for Reading!!!

LVL 9
trenesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

czcdctCommented:
The problem is the fact that one of these is an SBS environment and you have already established the new forest.
Given the number of users involved you can either look at the MailMig (Mail Migration) (http://www.msexchange.org/tutorials/Exchange-Migration-Wizard.html) or just exmerge out to PST files and then into your new AD Forest and Exchange Server.
Don't, whatever you do, go multihoming DCs or anything else. Routing is for routers, not application or directory servers.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SembeeCommented:
What is the end goal here? To ditch the SBS server?
If so I would be looking to pull the content out.

If you just want the two networks to co-exist then put them on the same subnet, and manually assign IP address for the SBS Server. Turn off the SBS Server's DHCP server as well.

Simon.
0
trenesAuthor Commented:
Yes , the goal is to ditch the sbs server.
Normally I would pull the emails out (I already have done that)
Normally I would change DNS and be done with it.
But I'm looking for a solution where I dont have to change DNS and wait 48 hours for mail to arrive, because that is not acceptable.

So I thought of a shortcut by connecting the second NIC on the DC in network 2 to the adsl router (installed as a bridge for a subnet of /31) on network 1.

cheers,
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

SembeeCommented:
Unless your domain registrar is working to standards set in 1990s, most DNS changes I make on MX records bite very quickly.
Another option would be to put a second MX record in that points at the primary server or a dynamic DNS address so that the changes take effect very quickly.
There is no need to put the configuration of the network and the servers at risk simply due to a few DNS issues.

Simon.
0
trenesAuthor Commented:
Your first sentence tells it all. We have a registrar that we need to fax and then its fingers crossed when they have the time to make a change. Its xs4all in the Netherlands that is also our ISP the other connection is from KPN.

It is really pretty straightforward but that ISP makes things very complicated.

0
SembeeCommented:
We have one of those sorts of ISPs in the UK called Demon Internet. If I get a client on them the first thing I do is remove the domain name from their control. They rebuild their DNS changes once a day, and will not budge on that policy. I have had clients down for days because they will not change. It is unacceptable.

I would get the domain name off them first, get under your control with a control panel etc. Then look at making the switch.

Simon.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.