Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #1715
| From | Erland Sommarskog <esquel@sommarskog.se> |
|---|---|
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | Re: Unable to connect Client to SQL Server |
| Date | 2014-03-11 08:51 +0000 |
| Organization | Erland Sommarskog |
| Message-ID | <XnsA2ED645E08739Yazorman@127.0.0.1> (permalink) |
| References | <lfit86$thr$1@speranza.aioe.org> <XnsA2EC5B95F23F9Yazorman@127.0.0.1> <lfl1cr$e5b$1@speranza.aioe.org> <XnsA2ECD650A5C8DYazorman@127.0.0.1> <lflktn$1ek$1@speranza.aioe.org> |
Bruno Campanini (brunocam@libero.it) writes: > - TCP/IP enabled > - FILESTREAM enabled > - Allow remote connection to the server > - SQL Server Services are running > - SQL Server Browser is running > - SQL Server Agent stopped (it doesn't start!) > - Firewall disabled on Server and Client > > It seems all is ok, but it's three days I try to connect a Client, > without any success! > The error message talks about named pipes, and the error code is 5, which usually means "Access is denied". There could be two reason it is trying TCP/IP: TCP/IP is not enabled on the client, or it using named pipes as a fallback when TCP/IP fails. You could try enabling Named Pipes on the sarver, but I don't really recommend it. Instead try specifying the server as SERVER,tcp to force TCP/IP to see what error message we get this time. Also try to make the connection from the command line with SQLCMD. It should give the same error, but you never know. -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Next in thread | Find similar
Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-10 00:24 +0100
Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-10 08:00 +0000
Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-10 19:47 +0100
Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-10 21:04 +0100
Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-11 01:21 +0100
Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-11 08:51 +0000
Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-11 13:37 +0100
Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-11 21:01 +0100
Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-12 15:02 +0100
Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-12 15:30 +0000
Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-12 17:10 +0100
Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-12 17:46 +0100
Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-12 21:16 +0100
Re: Unable to connect Client to SQL Server Bruno Campanini <brunocam@libero.it> - 2014-03-12 21:45 +0100
Re: Unable to connect Client to SQL Server Erland Sommarskog <esquel@sommarskog.se> - 2014-03-12 23:20 +0100
csiph-web