SQL Server 2012, especially when using a named instance, changes the way us old SQL Server veterans manage connectivity to the server. We are so used to relying on port 1433 for SQL Server that setting up a new SQL Server 2012 database server might give us some fits. I have one software engineering team that just did this recently. Our dev and test environments are in Windows Azure, and then our production environment is in a specialized data center on the east coast of the U.S. To make a long story short, we are using Azure's point-to-site VPN so that none of the servers can have any contact from the outside world. The only way to get to them is to VPN in. Then, the servers respond to pings, and it's as if they are on the LAN. It works great – except connecting SQL Management Studio to a new Windows Server 2012 box running SQL Server 2012 wouldn't work. All the old tricks of using SQL Configuration Manager and enabling TCP/IP yielded no fruit. And opening port 1433 on the firewall yielded no fruit as well.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

Articles,Computer Tutorials,SQL Server 2012