I have two machines. One is setup for 2012 SQL server development, another is setup for 2014On the 2012 box in SSMS, I can connect to a SQL 2005 server via Webserver1\Webserver1On the 2014 box in SSMS, I can only connect to that same server by specifying the Server with the port Webserver1\WebServer1, 2007If I try without the port. I get an error 'A network-relate or instance-specific error occurred while stabling a connection. The server was not found or was not accessible.... (provider: SQL Network interfaces, error 26- error locating server/instance specified)I was told the servers were clustered and that the name is an alias.Following instructions based on a google search, when I run Portquery with "Portquery.exe -n WebServer1 -p UDP -e 2007" ResultsUDP port 1434 (ms-sql-m service): LISTENING or FILTEREDSending SQL Server query to UDP port 1434...UDP port 1434 (ms-sql-m service): FILTERED"Portquery.exe -n WebServer1 -p UDP -e 2007" I get (unknown server: Listening or FilteredResultsUDP port 2700 (unknown service): LISTENING or FILTEREDThis does not make sense to me since the results for the port 1434 check look more promising than the check on port 2007. But the only way I can connect is with port 2007 added. Using 1434 says "No connection could be made because the target machine actively refused it"Thoughts?
↧