Question : Communication between 2 remote Servers

Hi All,

We have 5 remote sites, we are using Backup Exec 2010 for backup services. One of the web server is in web farm have 2 NIC one for internet facing and one for internal facing. Problem we are having is communication between web server and backup server. Backup server is residing in remote site i.e. site A with the network of 10.60.10.0 and IP for web server is:

Internet facing: 192.168.1.1/24
Gateway:192.168.1.254
Public DNS

Internal Facing:192.168.11.1/24
No gateway
Internal DNS

From the backup server I can ping 192.168.1.1 but not 192.168.11.1, also from the web server I cannot ping backup server. But when I ping it is resolving the IP for backup server. Also from backup server internal IP is resolving the name(IP) when I ping i.e. ping web1.

So far I tried to add route as:

Route add 192.168.1.0 255.255.255.0 192.168.1.254

Route add 192.168.11.0 255.255.255.0 192.168.11.254  but no luck

Can any one please advice how can I make communication in both servers? Only thing I can think off is using two gateways via Routing and remote Access???

PS: Web server is Windows 2003, Backup server is Windows 2008

Your help will be highly appreciated.

Regards

Sohail

Answer : Communication between 2 remote Servers

Sure.
Floating static routes for the VPN endpoints and floating default routes with route-maps

For IPSEC VPN are you talking about mobile users or site-site VPN? Assuming you mean site-site VPN:

ip route 192.168.0.0 255.255.0.0 <wan A next hop>
ip route a.b.c.d 255.255.255.255 <wan A next hop>  <=== this is the remote peer IP address
ip route 192.168.0.0 255.255.0.0 <wan B next hop> 100
ip route a.b.c.d 255.255.255.255 <wan A next hop> 100  <== same routes with higher cost for failover

ip route 0.0.0.0 0.0.0.0 <wan B next hop>
ip route 0.0.0.0 0.0.0.0 <wan A next hop> 100

Since you can only have 1 default gateway on the router, it's going to be a little more difficult to serve mobile VPN clients due to not knowing their public IP addresses, and your primary default will be to ISPB.
Here's a way around that:

ip route 0.0.0.0 0.0.0.0 <wan A next hop> <== default to A will allow remote users to connect VPN
ip route 0.0.0.0 0.0.0.0 <wan B next hop> 100

access-list 101 deny ip <local network> <imask> 192.168.0.0 0.0.255.255  
access-list 101 permit ip <local networ> <imask> any

route-map ISPB permit 10
 match ip address 101
 set ip default next-hop <WAN B Next hop ip>

interface xxx
 descript inside LAN interface
 ip policy route-map ISPB


If WANB is down, route-map traffic will automatically take the default out the other ISP