Link to home
Start Free TrialLog in
Avatar of manav08
manav08Flag for Australia

asked on

Setting up seperate ADSL connection for Exchange 2010

Hi Experts,

Here's the Present Scenario -

I have a client who have an ADSL 2+ Connection which they use in their office. We are using a snapgear firewall which is connected to the ADSL bridged modem (all the configuration is shown in the attachment). Now the problem ATM seems to be that they send and recieve a lot of emails each day which basically clogs up the internet making it really slow and unusable.
Server is running Windows Server 2008 R2 with Exchange 2010 and only has one Network Card configured at the moment.

Proposal -

We have proposed to the customer that they get a seperare new ADSL connection purely for their sending and recieveing emails (i.e. EXCHANGE 2010) and for every thing else like (RRAS VPN, Incoming Website IIS Traffic, Internet Browsing for staff) we use the existing ADSL connection.

What I want to be able to do now is configure a secondary network card on the server with IP of say 192.168.1.11 and have it set purely for Exchange 2010.
Recieving Emails - This shouldn't be hard as we can change our MX records to point to the new WAN IP and all incoming emails will flow through the new ADSL connection.
Sending Emails - I wanna know how do I configure this. I wanna be able to say in Exchange 2010 somewhere that send emails through the secondary network card. Obviously on this new network card I will be setting up the default gateway as 192.168.1.254. How do I configure all this?? And does my plan sound easy enough to implement.

I hope the picture attached explains everything, but if any questions, please let me know.
Image--2-.jpg
Avatar of shauncroucher
shauncroucher
Flag of United Kingdom of Great Britain and Northern Ireland image

The problem is that Exchange if using DNS to send mail will just send out default gateway. You could commission a smarthost to receive all outbound mail from Exchange 2010 however, and set this to use .11 to relay on?

Shaun
Avatar of Chelcone
Chelcone

I personaly would keep it simple.

Add another ADSL onto the network directly into the network switch. Give this ADSL router a Static IP address and ensure that no other computer has this router set as the default gateway. On your server go onto the network settings and (im assuming you use static IP on the server) change the default gateway to the new ADSL on both cards. if you seperate the functions of the two network cards then you will loose the security you get from having two cards if one dies. Simpaly changing the default gateway wont effect the inbound traffic but it will effect the outbound which im assuming is where your main problem is.

Chelcone
You can't do that. You will find RRAS VPN will not work, it can't maintain a TCP session with a default gateway set to another WAN connection!

Shaun
Avatar of manav08

ASKER

Hi Shauncroucher,

I was aware of the fact that you cannot choose the default gateway to send out on for Exchange 2003 but thought there might be a possibility in Exchange 2010. Sorry, I am still very new to Exchange 2010 so you might need to explain to me what you mean by "You could commission a smarthost to receive all outbound mail from Exchange 2010 however, and set this to use .11 to relay on? " and how to configure it.

Chelcone,

My problem is both incoming and outgoing emails. They send and recieve a lot of brochures, flyers, pictures etc. and recieve a lot as well.
SOLUTION
Avatar of shauncroucher
shauncroucher
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of manav08

ASKER

So You suggest that I do the following -

1. Install XP or something with IIS 6.0.
2. Add SMTP relay service on it
3. Use Smart Host to relay messages via this new machine.

Sounds a bit complicated. Is this the only option I have??
Its my bed time now so I will mos likely reply in about 10 hrs from now.
Yes, it's an option thats all, someone may have a better way of doing this, but I'm not aware of any way to split the SMTP traffic and send to another IP address (non default gateway) without using a smarthost option.

Shaun
Avatar of manav08

ASKER

Shauncroucher,

For starters, I wonder if having 2 network cards configured with different DEFALT gateway on the same server will cause any issues with other stuff running on the server OR as long as you have your network binding order setup correctly it should all work???
if you use a different subnet for the second card you wouldnt need to set a default gateway on the second card, seeing as you plan to use the adsl line as a dedicated email line, simply set this 'network' with a different subnet.

shaun
Avatar of manav08

ASKER

SO what you are saying is that I cannot have the same SUBNET and different gateways on the 2 NICs on the server?
OR
Are you suggesting that I do not have a default gateway at all on the second NIC?
i would put the smarthost on a seperate subnet with default gateway, then server nic will have ip in same subnet as smarthost, no default gateway, that way the routing table should take care of all traffic to and from the smarthost.

shaun
Avatar of manav08

ASKER

Hi shauncroucher,

Thanks a lot for your input. It makes sense.
I still wanna investigate if this can be done without the use of smarthost configuration or else I will have to buy an operating system license to run this configuration in a virtual HYPER-V R2 environment. Will get back to you soon.
You need a router that supports WAN load balancing, and Policy Based Routing.

Where you can have the two WAN links connected to the Device, and you will set a policy for all SMTP outgoing traffic to go through one link, and all other traffic through the another.

And it should be helpful with many other features, in addition that I think it's going to be cheaper that buying new PC.

Regards,
Keep it simple -

Install the new  ADSL with NAT and set its private IP address to an unused IP address within the local subnet - for example 192.168.1.254.

Change the DHCP server settings to issue the new gateway 192.168.1.254, but keep the current static IP settings including the gateway on the server as is.

All users will start using the new GW for web browsing, and the server will continue using the current connection  
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial