I cannot connect an instance of SSMS 2014 installed on my computer with an 2014 instance installed on a (remote) server. Both computers are on the same domain, and I am using NT authentication. All SQL installs referenced here are Developer 64 bit edition (we are just starting up with it).
On my (local) computer, I have both SQL 2008 installed (default instance) and SQL 2014 (named instance), along with SSMS and other client tools for both versions. OS on my computer is Windows 8.1 Enterprise.
The (remote) server is running Windows Server 2012 R2 Standard, with SQL 2014 installed (default instance). It is configured for NT authentication only, and is configured to allow remote access. The SQL Server Browser service is running on all referenced servers (as well as on my computer). As per the SQL Server Configuration Manager utility, "Control Protocols" are enabled for Shared Memory, TCP/IP, and Named Pipes. (Default instance port is 1433.)
Using SSMS 2008 on my laptop, I can connect to both local instances (2008 and 2014), and existing remote 2008 instances. I cannot connect to 2014 on the remote server. (SQL 2014 is currently only installed on my computer and the one server.)
Using SSMS 2014 on my laptop, I can connect to both local instances (2008 and 2014), and existing remote 2008 instances. I cannot connect to 2014 on the new instance.
I can remote-desktop to the remote server, and I can run SSMS on that local desktop and access the instance. (I am local admin on the box, and have SysAdmin rights on SQL.) I can “ping” the server. It is a virtual instance--Hyper V, I believe, but I have no access to that level of our infrastructure.
When I try to connect to the remote server (dev-db1) via SSMS 2008 or 2014, I get the following message:
---------------------------
Cannot connect to dev-db1.
Additional information:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 – No such host is known.) (Microsoft SQL Server, Error: 11001)
No such host is known
---------------------------
The fun part: everyone else on the team is able to connect to the 2014 instance, using SSMSes 2008, 2012, and 2014. I know little of firewalls, but this fact would seem to indicate that they are properly configured. Perhaps a firewall setting on my computer?…except I haven’t messed with it, and it looks like a totally default (corporate) setup.
This is a new laptop, prepped and distributed by "corporate IT". It has been demonstrably flaky in a few cases, and I half-suspect some files or drivers may not have been installed. Any help would be greatly appreciated!