Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The Status Quo:

There's a SQL Server (2005) database. On the same network, There's a user who connects a Visual FoxPro instance to said database via ODBC. This works, the user is happy, and everything is hunky dory.

Looming on the horizon:

The SS database is going to move to another network. There will be a firewall between it & the VFP user. This user does have access through the firewall via VPN, and a SQL account in the relocated database (no domain account on the new network).

The Question:

Will we be able to construct an ODBC connection string such that the VFP user can still use the SS back end? Anything special we need to do when setting it up? Anything special the user needs to do to connect?

If this belongs on SO rather than SF, let me know & I'll take it over there....

share|improve this question
up vote 1 down vote accepted

Yes, you will be able to construct an ODBC connection string such that the VFP user can still use the SS back end. No, nothing special is needed to set it up.

When he/she VPNs into the network the Sql Server will appear on the same network as the VFP user. Simply connect as normal.

share|improve this answer
Thanks. I'll come back and Accept your answer as soon as I've been able to prove it in my own environment. – RolandTumble Jul 15 '09 at 20:55

Depending on the setup, the SQL Server and the VPN user might not end up on the same network, and the firewall would probably block any broadcast regarding computer-names etc (NetBIOS).

Unless you have an AD-server that act as DNS, you might need to use IP-addressing instead of computer name (NetBIOS) in order to connect to the SQL Server, which might be a change you need to provide to the connection-string.

share|improve this answer

If there some firewall rules, you must allow 1433 port for default instance SQL, if you have named instanse you must look in Configuration Manager which dynamic ports uses in TCP/IP and allow this port on firewall.

share|improve this answer

Here's an article I wrote that goes into good detail about Sql Server instances and the ports that need to be opened up to allow remote access.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.