Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Erland Sommarskog Newsgroups: comp.databases.ms-sqlserver Subject: Re: Unable to connect Client to SQL Server Date: Mon, 10 Mar 2014 21:04:04 +0100 Organization: Erland Sommarskog Lines: 32 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Injection-Info: mx05.eternal-september.org; posting-host="fd3d6d0229f14a752f017d8f9903addd"; logging-data="9099"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18rVU+plWBrTxJ2Ynr9aOkF" User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) Cancel-Lock: sha1:IK23mLld7OfEqIZpcUma+hIjRnE= Xref: csiph.com comp.databases.ms-sqlserver:1713 Bruno Campanini (brunocam@libero.it) writes: > Erland Sommarskog has brought this to us : >> What error message do you get? > > Connection failed: > SQL State: '08001' > SQL Error: 5 > [Microsoft][Driver 11 for SQL Server]Named Pipes Provider:Could non > open a connection to SQL Server [5]. > Connection failed: > SQL State: 'HYT00' > QSL Server Error: 0 > [Microsoft][ODBC Driver 11 for SQL Server]Login timedout expired > > From that I am unable to uderstand/get any useful information. > Well, at least then I know that it is a connectivity problem and not a strict authorisation problem. Could you try changing the server name to something absolutely wrong and see if you get the same error message, or a different one? Are you using Windows authentication or SQL authentication? Sorry for all the question, but troubleshooting connectivity problems on a distance with a minimum of information is tedious. -- Erland Sommarskog, Stockholm, esquel@sommarskog.se