If you are not able to access the remote SQL Server, please ask your admin to make sure all these happen.Ī firewall on the SQL Server machine (or anywhere between client and server) could block SQL connection request. If the target SQL instance is a named instance, you also need to make sure SQL Browser is running on the target machine. %ProgramFile%Microsoft SQL Server/MSSQLxx.xxx/MSSQL/Log The location of errorlog file is usually under: You can open errorlog file to see if the server is successfully listening on any of the protocol. Once you enabled protocols in SCM, please make sure restart the SQL Server. For remote connection, NP and/or TCP protocols must be enabled. SQL Server supports Shared Memory, Named Pipes, and TCP protocols (and VIA which needs special hardware and is rarely used). You can use SQL Server Configuration Manager (SCM) to enable protocols on the server machine. You need to make sure the target SQL Server is running and is listening on appropriate protocols. "Cannot Generate SSPI Context" error message, Poisoned DNS Wrong DNS entry could cause of all sorts of connectivity issue later. The correctness of DNS configuration on the network is vital to SQL connection. Windows firewall does not block ping (ECHO) packet by default. It's possible the target machine is behind a firewall and the firewall blocks the packets sent by ping, though. If you are not able to ping your target machine, it has high chance that either the network is broken or the target machine is not running. (type your local and remote machine name and IP address multiple times)īe careful to see any mismatch on the returned results. (use -4 and -6 for IPv4 and IPv6 specifically) The first thing to trouble shoot SQL connectivity issues is to make sure the network we rely on is workable and stable. For remote connection, a stable network is required. You might be able to make local connection without a working network, but that's a special case. Usually, customers see connectivity issue in their applications, but it would be great if you can follow the steps below to eliminate issues one by one and post a question on Here comes a proposal based on my experience.īasically, when you failed to connect to your SQL Server, the issue could be: I guess it would be helpful if we can put some guidance on how to resolve connectivity issues. We have been seeing and trying to resolve SQL connectivity issue all the time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |