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,038 of 19,505    |
|    Bruno Campanini to All    |
|    Re: Unable to connect Client to SQL Serv    |
|    11 Mar 14 13:37:10    |
      From: brunocam@libero.it              Erland Sommarskog was thinking very hard :              > 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.       With "SERVER,192.168.1.204" I get Error 87 and Error 0       With "SERVER,tcp" the same 87 and 0       >       > Also try to make the connection from the command line with SQLCMD. It should       > give the same error, but you never know.       Command line SQLCMD from where?... not from Dos Prompt.       And what sintax?              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