Problem with 2 exchange servers for a single domain on the same subnet
Guys,
I have a small client, who recently split the business into 2 parts. Both businesses are physically located in the same premises, both have an SBS2003 r2 server. file and print services are used by each business on their respective SBS server. some network devices are still shared, and thus all users are on the same subnet. Currently server1 has a problem with SMTP traffic, and is using POP connectors to an external ISP to pull down mail. All users currently use the Exchange 2003 server on Server1.
both businesses share the use of a single external domain mybusiness.com.au, and I have set up similar, but different internal domains for the SBS server mybusiness.local and mybus.local.
I moved the 2nd business users to Server2, and this worked for external mail. however, they were unable to send internal mail between Exchange server1 and Exchange Server2, and the shared devices routed mail through server1, where it queued until they failed.
lookiing for thoughts on how to set this up correctly? any ideas?
I have a small client, who recently split the business into 2 parts. Both businesses are physically located in the same premises, both have an SBS2003 r2 server. file and print services are used by each business on their respective SBS server. some network devices are still shared, and thus all users are on the same subnet. Currently server1 has a problem with SMTP traffic, and is using POP connectors to an external ISP to pull down mail. All users currently use the Exchange 2003 server on Server1.
both businesses share the use of a single external domain mybusiness.com.au, and I have set up similar, but different internal domains for the SBS server mybusiness.local and mybus.local.
I moved the 2nd business users to Server2, and this worked for external mail. however, they were unable to send internal mail between Exchange server1 and Exchange Server2, and the shared devices routed mail through server1, where it queued until they failed.
lookiing for thoughts on how to set this up correctly? any ideas?
Would your smtp connector router outgoing emails as well as "internal"?? I think sending from Ex1 to Ex2 would classified as external as its on a different domain?
The SMTP connector that I mentioned is just for routing the internal email.You need to add a dummy email address @mybus.local and forward all the email to the mybus.local exchange organisation.
Sending from ex1 -ex1 would be classified and internal because you not using any public IP addresses.You are just redirecting the email.
Sending from ex1 -ex1 would be classified and internal because you not using any public IP addresses.You are just redirecting the email.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hey Jeff,
I'd normally do it like that, however there were / are cost constraints. Remote access isnt' as critical to the business as the separation of files / data. thus it wasn't really an option. The Shared Device is a multi function printer - that is used as a network printer, however the critical function is to scan and email large documents internally, then to external users.
So the issue really in the routing of these most times large emails internally, and internal mail generally. I'll check out the sites you mentioned, thanks.
I'd normally do it like that, however there were / are cost constraints. Remote access isnt' as critical to the business as the separation of files / data. thus it wasn't really an option. The Shared Device is a multi function printer - that is used as a network printer, however the critical function is to scan and email large documents internally, then to external users.
So the issue really in the routing of these most times large emails internally, and internal mail generally. I'll check out the sites you mentioned, thanks.
Cost constraints? They split up a company and each part cannot afford their own Internet access? Because basically that plus an additional $100 for a switch and router are the only additional costs found in my suggestion. And if the current Internet Access Provider offers additional IP's then there's not even much cost there!
If document distribution is via email then the MFC doesn't need to be a shared device. Once you properly configure SMTP Name Space sharing you attach the MFC to one of the domains and the will be able to email whatever they want to the other.
But you can't do the SMTP Namespace Sharing at all if each Exchange Server doesn't have it's own public IP address.
Jeff
TechSoEasy
If document distribution is via email then the MFC doesn't need to be a shared device. Once you properly configure SMTP Name Space sharing you attach the MFC to one of the domains and the will be able to email whatever they want to the other.
But you can't do the SMTP Namespace Sharing at all if each Exchange Server doesn't have it's own public IP address.
Jeff
TechSoEasy
Just because the client chose to not implement the suggested solution does not make it any less correct for the proposed scenario given in the original question.
I would recommend that the question be closed with http:#19563168 selected as the correct response.
Jeff
TechSoEasy
I would recommend that the question be closed with http:#19563168 selected as the correct response.
Jeff
TechSoEasy
ASKER
Jeff,
apologies. i concurr. points should go to you.
apologies. i concurr. points should go to you.
naughton,
Thanks for following up. I realize that you haven't asked many questions here before, so no worries.
Jeff
TechSoEasy
Thanks for following up. I realize that you haven't asked many questions here before, so no worries.
Jeff
TechSoEasy
Let me know if I didn't make the things clear enough for you.