Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Port 1434 is blocked somewhere along the line, which is used to resolve instance name to port number.</p> <p>If you specifiy a port number, instance name is ignored...</p> <p><a href="http://msdn.microsoft.com/en-us/library/ms181087.aspx" rel="nofollow noreferrer">SQL Server Browser service listens on port 1434</a></p> <blockquote> <p>Upon startup, <strong>SQL Server Browser starts and claims UDP port 1434</strong>. SQL Server Browser reads the registry, identifies all instances of SQL Server on the computer, and notes the ports and named pipes that they use. When a server has two or more network cards, SQL Server Browser returns the first enabled port it encounters for SQL Server. SQL Server Browser support [sic] ipv6 and ipv4.</p> <p>When SQL Server clients request SQL Server resources, <strong>the client network library sends a UDP message to the server using port 1434. SQL Server Browser responds</strong> with the TCP/IP port or named pipe of the requested instance. The network library on the client application then completes the connection by sending a request to the server using the port or named pipe of the desired instance.</p> </blockquote> <p>Edit, after comment:</p> <p>What is the local client setting default? It should be 1433 of course, but if not then just servername will not work.</p> <p>Launch "SQL Server Configuration Manager".. "SQL native client configuration".. "client protocols".. double click tcp/ip, the default port used by your local PC is there.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload