February 14, 2014 at 4:32 am
Hi all!
In SQL server 2008R2 it was always the same items, that had to be corrected, if you could not connect to the server:
Enable 'Named pibes'
Enable 'TCP/IP'
Set sql browser start to automatic
set firewall to allow connection through the relevant ports (1433), if in doubt, disable firewall and antivirus
After that, it was allways succes.
It seems like, that SQL2012 has more possibilities of failure to connect.
What to look fore?
Best regards
Edvard Korsbæk
February 14, 2014 at 4:38 am
what error you are getting while connecting to 2012 instance.
February 14, 2014 at 4:45 am
Error message attached
Best regards
Edvard Korsbæk
February 14, 2014 at 4:47 am
is it a virtual server or a physical server ?
try this
The problem might be firewall, but more specifically the firewall rule for SQL SERVER.
The custom rule could be pointed to the prior version of SQL Server.
Try this, open Windows Firewall>Advanced setting. Find the SQL Server Rule (it may have a custom name). Right-Click and go to properties, then Programs and Services Tab. If Programs-This program is selected, you should browse for the proper version of sqlserver.exe.
February 14, 2014 at 5:24 am
Thanks!
It is placed on a Windows server 2008 R2 standard, and I am not totally sure (Placed at a customer, and I have remote desktop connection to it), but it seems like its a WMware server.
Concerning the firewall, we simply disabled it as a try to solve the problem.
Best regards
Edvard Korsbæk
February 14, 2014 at 6:29 am
From the IP in the screenshot, it looks like you're trying to enable external connections directly to SQL over port 1433 (e.g. over the internet rather than just LAN). This is potentially lethal from a security standpoint, especially as you've mentioned disabling firewalls.
It's difficult to give specific advice as it will depend on the network setup of the hosting location, but generally speaking, there will (hopefully) be a real firewall above the Windows firewall that's blocking this and it would need to be configured to forward the port through to your SQL Server with a white-list of external IPs from which access is allowed. SQL Server is not a hardened service that would be advisable to expose to the internet at large. If there's no firewall above the machine/VM, you can do all of this with the Windows firewall.
If this is a non-default instance, you also need to consider UDP port 1434. This isn't a basic topic and the wrong setup could seriously put your data at risk, so I'd recommend getting advice from the network administrators of your hosting location/customer...
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply