Named Pipes connectivity problem

  • Hello Everyone,

    I am searching information about Named pipes, connectivity problems, security issues. Anybody knows good articles about that?

    What I don't really understand, since I am not a network guy , is why, when using the named pipes protocol, I can't connect to a server but using TCP/IP I can?

    Also, what is the relation with the fact that issuing the comand NET VIEW \\server and receiving error 5 (acces denied) has an impact on the named pipes protocol since it does not on the TCP/IP protocole?

    Another point that is not clear for me is how can I see, using the named pipes protocol, which protocol stack is used underneath (TCP/IP, NetBeui, NwLink)?

    Best regards,

    Carl

  • Can you post the error message you receiced when trying to connect to the SQL Server with named pipe?

    Did you try to connect MSDE, Named instance or virtual SQL Server instance?

    Which version od MDAC do you have in the machine that you had trouble to connect? Do everyone have same issue or does it happen to some machines? Is named pipe network libarary enabled in SQL Server?

    See Microsoft KB 827422 for trouble-shooting connectivity problems.

     

  • Hello Allen,

    First of all, let me say that the problem is not happening here at our site, it is one of our client that have this problem.

    Here is the error received (it is in french):

    SQL Server n'existe pas ou l'accès est refusé.

       at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)

       at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)

       at System.Data.SqlClient.SqlConnection.Open()

       at dtbmsq_Connection_c.OnConnect(dtbmsq_Connection_c* ) in q:\ogl20051\src\database\dtbmsq\dtbmsq_connection_c.cpp:line 225

    The translation in english would be something similar to: "SQL Server does not exists or acces is denied".

    Tried to connect to a named instance.

    the version of MDAC is: 2.8.

    The problem seem to happen to all the machines.

    I will ask the question to the client to see if the Named pipes protocol is enabled in the network server library utility.

    I will llok at the KB 827422.

    Thank's Allan.

    Carl

     

     

  • Hello Allen,

    found the article id: 101150 more interesting...

    http://support.microsoft.com/default.aspx?scid=kb;en-us;101150

    It goes deeper and help me understand my case completely.

    Best regards,

    Carl

     

  • ... In fact not completely.

    There is a last thing I would found very usefull to learn:

    How to distinguish which protocol stack is used underneath (TCP/IP, NetBeui or NwLink) when the Named Pipes net-library is used?

    Is there a way?

    Regards,

    Carl

     

     

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply