HQ - Static IP needed

Your remote clients will need some sort of access to the HQ LAN. There are lots of ways... The cheapest (and slowest) would be a direct dial-in connection. VPN over DSL/Cable is probably most common and most cost-effective. A dedicated WAN would be ideal but is likely cost prohibitive.

For VPN access, you will need to get a static IP from your HQ ISP. The static IP will be assigned to the router. You will be able to keep your private IP scheme on the LAN. If at all possible, try to stick with one ISP for all of your locations--you will get better VPN performance if you do.

This may not be a good DIY project if you are not intimately familiar with this sort of thing.

Tom

"pat" wrote:

Pat,

Depends on how you are connected to the Internet.

1. Do you have a static WAN IP address? If you don't know, ask you ISP. If so, have your remotes point to that address.

If you don't have a static, they will charge anywhere from $10-50 per month to get one.

OR

You can get a free Dynamic IP address from various sources, my current fav being DynDNS.com, but there are others, No-IP.com, tzo.com, hundreds more, search Google for Dynamic DNS.

1. Change your router to point all traffic on TCP port 34200, the default for HQ Server, to route to the database server machine's static, internal IP address.

1. Setup HQ Client to connect to the static WAN IP or the dynamic name used in the Dynamic IP setup that you choose.