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

We are upgrading from sql server 2005 to sql server 2008 and windows server 2008 R2.

New server is behind a firewall, we have 30 or so windows XP machines, that will require the port 1433 to be open, because they are old Windows applications that require a direct connection.

Previously the old sql server was on two network, one of which was a private network, and we had a vpn server that would put each of these client machines on that private network. This setup is no longer available for us.

Is there a way to tunnel all these client machines so that we do not have to punch holes in the firewall?

share|improve this question
You guys decided to tear down the VPN server. How does this mean the setup is no longer available to you? Just put the server up again. – gparent Jan 30 '13 at 20:43
Otherwise, if you can't put the VPN back up, there's nothing wrong in opening ports that need to be opened. – gparent Jan 30 '13 at 20:44
The new server is at a new server farm location, we were told we are not going to get a second server to act as a vpn. – Max Marchevsky Jan 30 '13 at 20:58

You have two options, both of which you have eliminated: tunnel through a VPN or poke a hole in the firewall. So no, without knowing a lot more about your application and network infrastructure, there is no other option.

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.