Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Conneting sql from a remote computer 1
- Thread starter duartevds
- Start date
-
1
- #2
Olaf Doschke
Programmer
It's not just a client-side configuration, at home in your 2012 Server you'll have to allow access to the SQL Server Service via firewall rule.
1. On the server (OS) itself, you need to allow remote connections
2. In SQL Server Configuration Manager you need to enable TCP/IP
3. In the server firewall, you need to allow traffic on port 1433 on a standard instance and additionally on 1434 on a named instance. And there we go for very delicate opening of the connection towards public, not just a domain or private network location.
You may also need assistance from your ISP with their specific cable modem settings and firewall etc.
Overall it's less of a risk and easier, if you'd use Azure or similar in the cloud and not your own server.
Before you go for SQL Server, you should test using VPN and seeing your server as a file server, that already has enough initial hurdles.
And test this from home to home for example with a notebook only in the internet via WLAN, not joined to your server domain or workgroup, then you can see whether that'll also work with an internet connection from anywhere, as you actually route at least via your isp and not just via your router.
Bye, Olaf.
Olaf Doschke Software Engineering
1. On the server (OS) itself, you need to allow remote connections
2. In SQL Server Configuration Manager you need to enable TCP/IP
3. In the server firewall, you need to allow traffic on port 1433 on a standard instance and additionally on 1434 on a named instance. And there we go for very delicate opening of the connection towards public, not just a domain or private network location.
You may also need assistance from your ISP with their specific cable modem settings and firewall etc.
Overall it's less of a risk and easier, if you'd use Azure or similar in the cloud and not your own server.
Before you go for SQL Server, you should test using VPN and seeing your server as a file server, that already has enough initial hurdles.
And test this from home to home for example with a notebook only in the internet via WLAN, not joined to your server domain or workgroup, then you can see whether that'll also work with an internet connection from anywhere, as you actually route at least via your isp and not just via your router.
Bye, Olaf.
Olaf Doschke Software Engineering
- Moderator
- #3
- Status
Similar threads
- Locked
- Question
