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!!!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
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,
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.
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.
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.
Business Accounts
Answer for Membership
by: czcdctPosted on 2007-03-27 at 11:44:53ID: 18802417
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
Don't, whatever you do, go multihoming DCs or anything else. Routing is for routers, not application or directory servers.