From: esquel@sommarskog.se   
      
   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   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)