darrell667
asked on
NIC Config for SBS & Exchange Server
I currently have SBS 2003 running along with Exchange Server 2003, however the Exchange server is only providing local email services because we have an external service hosting our domain. My goal is to host our own domain email in house with the Exchange server.
My thoughts are this: please let me know if I am going in the right direction here.
SonicWall TZ170 with a Public IP address and running DHCP and VPN services and plugged into the switch.
Two network cards on the server:
The first one is active and has a local IP address and plugged into the switch
The second is inactive, but I would like to provide it with a Public IP address and run it directly to the SonicWall
If this sounds like the correct way to set it up for this purpose, how do I configure it so the second NIC supports only the Exchange server and all the local network traffic and Internet continue on the first NIC, and do I need to further configure anything like the ISA or RRAS for this to work?
My thoughts are this: please let me know if I am going in the right direction here.
SonicWall TZ170 with a Public IP address and running DHCP and VPN services and plugged into the switch.
Two network cards on the server:
The first one is active and has a local IP address and plugged into the switch
The second is inactive, but I would like to provide it with a Public IP address and run it directly to the SonicWall
If this sounds like the correct way to set it up for this purpose, how do I configure it so the second NIC supports only the Exchange server and all the local network traffic and Internet continue on the first NIC, and do I need to further configure anything like the ISA or RRAS for this to work?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
FYI, I just reread your overview above, and thought I'd point out a couple of things you want to be sure of doing.
You should not run DHCP or VPN on your SonicWall (at least not at first... if you want to move the VPN there you can, but the native SBS VPN works quite well).
You also do not want to plug the SonicWall into the switch... that should only have your LAN side NIC and workstations attached. Otherwise you compromise the advantage of having two NICs in your SBS which creates a second firewall via RRAS.
It's always best to set up and configure SBS according to proven methods such as thouse outlined in the documents I linked above (as well as what you'll find at http://sbsurl.com/techguide). That way you can be sure that everything is working before you make any changes to suit your particular environment. In most cases you won't need to change a thing... but if you do need to, at least you'll be able to troubleshoot easier if something goes awry.
Jeff
TechSoEasy
You should not run DHCP or VPN on your SonicWall (at least not at first... if you want to move the VPN there you can, but the native SBS VPN works quite well).
You also do not want to plug the SonicWall into the switch... that should only have your LAN side NIC and workstations attached. Otherwise you compromise the advantage of having two NICs in your SBS which creates a second firewall via RRAS.
It's always best to set up and configure SBS according to proven methods such as thouse outlined in the documents I linked above (as well as what you'll find at http://sbsurl.com/techguide). That way you can be sure that everything is working before you make any changes to suit your particular environment. In most cases you won't need to change a thing... but if you do need to, at least you'll be able to troubleshoot easier if something goes awry.
Jeff
TechSoEasy
ASKER