[BB] Rick James
[H]ard Dawg
- Joined
- Apr 4, 2004
- Messages
- 2,810
So we have Server 1 (SVR1) which is currently hosting our email AND is our domain controller. I've set up a new server which will act as our domain controller and file storage and lets call it SVR2.
Right now SVR1 is our domain controller, email, VPN server and file server.
I'm taking SVR2 and making it our new domain controller, VPN server and file server leaving SVR1 just for mail.
SVR1 right now is staticed with our public IP static'd into it. When I static SVR2 and give SVR1 a private ip address (10.0.0.2 for example) what needs to be done in exchange when I make these switches? Exchange doesn't need to be running on a box with a public IP does it?
The make matter worse, the company wants SVR2 to act as a router, which is no big deal but as we all know having Windows act as your router isn't the best scenario.
What I'd like to do is get everything behind a router, forward traffic to the appropriate servers and be done with it.
But the powers that be don't want that. So, if SVR1 (Exchange Server) is behind SVR2 which will be handing out private addresses, what will need to be done on the Exchange Server to keep getting email?
**Edit. Also forgot to add we are running Win2k3 64bit servers and the public IP address that we have might be changing....So the public IP on SVR2 will be different from the one that SVR1 had.
Right now SVR1 is our domain controller, email, VPN server and file server.
I'm taking SVR2 and making it our new domain controller, VPN server and file server leaving SVR1 just for mail.
SVR1 right now is staticed with our public IP static'd into it. When I static SVR2 and give SVR1 a private ip address (10.0.0.2 for example) what needs to be done in exchange when I make these switches? Exchange doesn't need to be running on a box with a public IP does it?
The make matter worse, the company wants SVR2 to act as a router, which is no big deal but as we all know having Windows act as your router isn't the best scenario.
What I'd like to do is get everything behind a router, forward traffic to the appropriate servers and be done with it.
But the powers that be don't want that. So, if SVR1 (Exchange Server) is behind SVR2 which will be handing out private addresses, what will need to be done on the Exchange Server to keep getting email?
**Edit. Also forgot to add we are running Win2k3 64bit servers and the public IP address that we have might be changing....So the public IP on SVR2 will be different from the one that SVR1 had.