Connection Problem - LoadNetLibs()

  • We have an application running on serval Windows XP computers that connects to SQL Server 2000 which runs on Windows Server 2003.  However one particular computer cannot establish connection with the SQL server and throws the following error:

    [DBNETLIB][ConnectionOpen(LoadNetLibs()]

    We spent quite a lot of time to figure it out but failed. Can someone drop a hint as what could be causing this problem and how to solve it.

     

  • Tariq,

    Plz check it out! Is the system on which Sql server is installed is accessible to you or not??

    IS there is a proper network connection between systems..

    and one more thing , name of the server is correct or there is any mis-spell.

    Then let me know..

    Regards,

    Amit Gupta...

     

  • Hi Amit,

    • The system (W2K3) server is accessible.
    • Proper network connection is in place.
    • The user has administrative rights
    • The user is using Windows Authentication to access the database server.
    • Database name being used is correct.

    Regards

    Tariq

  • The Server and the Client must both be using the same  network communication protocol.  For example if the client is talking Named Pipes, the server must be listening on named pipes.  To verify this use the Server Network Utility on the SQL Server machine and the Client network utility on the client computer.

    Typicaly the server will list Named Pipes and then TCP/IP and the client will list TCP/IP and named pipes.  However their are other protocols that the client and server can use as well.

  • The Server and the Client must both be using the same  network communication protocol.  For example if the client is talking Named Pipes, the server must be listening on named pipes.  To verify this use the Server Network Utility on the SQL Server machine and the Client network utility on the client computer.

    Typicaly the server will list Named Pipes and then TCP/IP and the client will list TCP/IP and named pipes.  However their are other protocols that the client and server can use as well.

    Another possibility is that the Security context of the MS SQL Server process does not have Administration privilideges on the server or it does not have permission to open a tcp/ip socket.

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

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