• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 425
  • Last Modified:

How to Sync over a WAN

Hi

I have a SQL server as part of my local domain and wish to have another server (standalone server) in a remote location with syncronisation, between the sql server and standalone server.
I thought i'd be able to insert an additional network card in the sql server and use this for vpn'ing onto the standalone server running RRAS. The problem is when the card is active, it gets assigned an IP from DHCP of the LAN and then my local users are complaining they cant access the sql software.

Is there a better way around this?

Thanks
0
teknite
Asked:
teknite
  • 3
  • 2
1 Solution
 
tismetooCommented:
A couple of options:

Allocate a static IP address to the network card, but you will need to take off the "register this connections address in DNS" to avoid the same issue with the clients. You can do this on a DHCP allocation, but the DHCP server ( depending on what is allocating the addresses ) may register the IP address in DNS regardless.

Use another connection mechanism such as IPSec VPN, which would allow the server to communicate on the original IP address. But I guess you don't have the hardware otherwise you wouldn't be using RRAS.
0
 
tekniteAuthor Commented:
Thanks. Our SBS box is DHCP'ing to the network, which is our DC.
Should we allocate the address as part of the LAN range or an IP address as part of the remote site?
0
 
tismetooCommented:
I presume you only have a single subnet at the SQL server site - in which case it should be a local IP address. You then have to sort out how the 2 sites connect - unless you can do that already.

Once that is done you will be advised to add a route to the remote site to send the traffic out of the static IP interface, which will ensure the comms are going out of the correct interface locally.

Incidentally, why do you need a second network card - that is not clear at the moment? If IP routing is working correctly you should not need it, unless you want to seperate the traffic for performance or secruity reasons.
0
 
tekniteAuthor Commented:
Yes thats right we have a single subnet. my thoughts were to have the sql server vpn'ing to the 2nd site with RRAS being run on the member server.
My thoughts of a 2nd card were to route traffic through that card and keep it seperate form the network.

Are these good practices or should i be doing something else? All i know is that the sync sofware can only sync via vpn over the WAN.
0
 
tismetooCommented:
If you can isolate the traffic from your primary LAN on a second card, with VLANs or a seperate port on your firewall, then it would be a good way of isolating the traffic. If you can't isolate the traffic in that way then I suspect you are going to cause yourself more headaches than you need - with routing and firewall configuration for a seperate subnet on the same physical LAN segment.

The other way of looking at this is if RRAS is installed on the remote server, it will only be able to talk to your SQL server anyway, assuming your firewall is managing sessions correctly with NAT. Whether it does this from the same IP address or from a different IP address will probably not make much difference. I would be inclined to stick with the single interface card, unless you can isolate the traffic with VLAN or a seperate zone on your firewall.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now