Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 19,034 of 19,505    |
|    Bruno Campanini to All    |
|    Re: Unable to connect Client to SQL Serv    |
|    11 Mar 14 01:21:12    |
      From: brunocam@libero.it              Erland Sommarskog laid this down on his screen :       > 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?              With a wrong server name I got:              Connection failed:       SQL State: '08001'       SQL Error: -1       [Microsoft][ODBC Driver 11 for SQL Server]SQL Server Network       Interfaces: Error Locating Server/Instance Specified       [xFFFFFFFF]       Connection failed:       SQL State: 'HYT00'       SQL Server Error: 0       [Microsoft][ODBC Driver 11 for SQL Server]Login timedout expired              > Are you using Windows authentication or SQL authentication?       SQL Authentication on the default instance MSSQLSERVER              > Sorry for all the question, but troubleshooting connectivity problems on       > a distance with a minimum of information is tedious.       - 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!              Bruno              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca