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

I have a testing environment that I would like my team members to access just to develop on. It is not linked to any other server system or network, however it is open to the Internet. What I would like to know is it possible to make the SQL Server public so that my team members can connect to an run code?

Currently it is not possible for them to VPN.


Windows 2008 Server

SQL Server 2012

share|improve this question
This will allow anyone to attempt to log into the SQL Server instance. This includes people who will attempt to break into the SQL Server instance. – mrdenny May 1 '12 at 2:44
Why can't they VPN? The 2008 server can be used as a VPN server if that's what you need. – Chris McKeown May 1 '12 at 7:32
I haven't set up VPN on this server. Which leads to my next question. I have the server role setup but the client are unable to connect, even internally. They get error 807. Any thoughts? – Brandon Wilson May 1 '12 at 11:30
^ Start a new question for your VPN issues so they get the proper attention from the right folks. – JohnThePro May 3 '12 at 14:22
up vote 3 down vote accepted

Simply make the port 1433 available for through your router. Should be all you need. Well, that's the minimum you need, but it answers your question. :)

  1. Hole in router/firewall for 1433.
  2. Port forwarded in router to push traffic on 1433 to [IP of SQL Server]
  3. Exception in Windows Firewall to allow traffic to port 1433 (TCP).
  4. Confirmation that SQL is configured to allow connections by TCP/IP.
share|improve this answer

I would recommend using a non-standard port, something other than 1433. See Configure a Server to Listen on a Specific TCP Port. Port 1433 is subject to constant brute force attack scans from bots trying for weak sa passwords.

share|improve this answer
You can configure something like 1334 which is memorable, but less likely to be subject to brute force attacks. – kafka May 1 '12 at 8:00
To simplify things have the firewall port forward from a non-standard port. Same result and no changes needed on the SQL Server. – John Gardeniers May 1 '12 at 8:08

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.