February 9, 2017 at 11:45 am
I'm almost certain the solution is simple, but I've looked through documentation and various help topics the last few days and haven't been able to find anything speaking to this specific issue. I am an entry level DBA coming from a research background, and don't have much experience setting up server connections.
My small company has a SQL Server Express stored on a local Windows Server that I'm using to develop and test a database to eventually clone in a Microsoft Azure host environment to handle our .NET membership site. I have configured the SQL Server and Windows Server to allow remote access through the firewall, and it connects fine on my work computer and my laptop when I am using my workplace's WiFi internet (both are accessed through SQL Server Authentication). However, when I take my laptop home and try to connect, I get the standard Error 26: Locating Server/Instance Specified.
I imagine there must be some further configuration of the firewall that I'm missing to allow access from outside the work network, but I can't find anything that speaks to this specific need. I believe whatever is causing it has also caused the connection issues I've had bridging the SQL server to our non-production website that's hosted externally.
Any help would be greatly appreciated!
Mike
February 9, 2017 at 12:00 pm
Couple possibilities.
First, I'd bet that your workplace firewall (not the firewall in Windows, this would be your workplace router / firewall) isn't configured to allow the SQL port through (1433.) That being said, I would strongly, strongly, strongly advise against just opening / forwarding that port, or any other port, to your SQL server. That's just begging for someone with nefarious purposes to come waltzing in.
Quite likely this is also why your external website is unable to access SQL as well.
Now, possibly, your network people may be able to configure the firewall to allow the connection between the web server and your SQL instance and be confident that it's reasonably secure. That's up to you and them to decide.
As for accessing the SQL remotely yourself from home, I'd lean towards working with your network guys to either set up a VPN between you and the office that allows 1433, or some sort of remote desktop solution that you can connect to from home and then access the SQL instance.
April 6, 2017 at 7:48 am
mvimont - Thursday, February 9, 2017 11:45 AMI'm almost certain the solution is simple, but I've looked through documentation and various help topics the last few days and haven't been able to find anything speaking to this specific issue. I am an entry level DBA coming from a research background, and don't have much experience setting up server connections.My small company has a SQL Server Express stored on a local Windows Server that I'm using to develop and test a database to eventually clone in a Microsoft Azure host environment to handle our .NET membership site. I have configured the SQL Server and Windows Server to allow remote access through the firewall, and it connects fine on my work computer and my laptop when I am using my workplace's WiFi internet (both are accessed through SQL Server Authentication). However, when I take my laptop home and try to connect, I get the standard Error 26: Locating Server/Instance Specified.
I imagine there must be some further configuration of the firewall that I'm missing to allow access from outside the work network, but I can't find anything that speaks to this specific need. I believe whatever is causing it has also caused the connection issues I've had bridging the SQL server to our non-production website that's hosted externally.
Any help would be greatly appreciated!
Mike
opening up TCP 1433 to the world and his wife will not end well for you.
Look into a VPN configuration to provide secure remote access to your sql server
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 6, 2017 at 7:57 am
jasona.work: Sorry! Completely lost track of time since posting this. Thank you, that was 100% the issue! Network Admin type issues have definitely been the hardest to parse out coming form research, fortunately I finally got the OK to set up an Azure server/DB so was able to circumvent the issue.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply