DBNETLIB General Network Error

From: ronbo42 (ronbo42_at_discussions.microsoft.com)
Date: 01/04/05

  • Next message: Ken Schaefer: "Re: Not associated with a trusted SQL Server connection.?"
    Date: Tue, 4 Jan 2005 14:37:02 -0800
    
    

    Hello.

    I'm not sure if I'm posting in the correct forum, but I'll ask the question
    just the same.

    I have a SQL 2000 (SP3) ERP running on a W2003 server. I'm in the process of
    upgrading my NT4 domain so currently running in mixed-mode (One W2003 DC and
    an NT4 BDC). My clients can access the database just fine, but when
    completing certain transactions, they get a [DBNETLIB](ConnectionRead
    (WrapperRead()).]General Network Error. I also recieve a Connection Failure
    error at times. I have set up ODBC under Named Pipes and TCP/IP with the same
    effects. I'm logging in using SQL Server Authentication.

    My ERP support team says this is a SQL 2K/AD error that I have to fix and it
    is not their applications fault. Any clues on what is causing this? My NT
    clients seem to be having less of these issues than my XP/2K clients.


  • Next message: Ken Schaefer: "Re: Not associated with a trusted SQL Server connection.?"

    Relevant Pages

    • RE: Can win9x clients connect to new 2003 domain
      ... Windows Server 2003 via NTLM. ... is best if all Windows 95 and Windows 98 clients install the DSClient. ... data on the new DC's and still access files on the NT4 domain?? ... This posting is provided "AS IS" with no warranties, ...
      (microsoft.public.windows.server.migration)
    • Re: Fallback to NT4 - Clients wont talk to Domain
      ... You will have to take the WinXP machines and make them a WORKGROUP member, ... > route for converting our NT4 domain to Active Directory. ... > an easy way to move all the clients back to the NT4 domain ... if we did find a way to rejoin the NT4 ...
      (microsoft.public.win2000.active_directory)
    • Re: Windows XP Pro Client login to Windows NT4 Server (PDC)
      ... It is something of a miracle that W2k clients are fine ... XP clients in an NT4 domain are a little more ... > On trying to connect a Windows XP pro client to a Windows ... > this be reason for the error message. ...
      (microsoft.public.windowsxp.security_admin)
    • Re: Fallback to NT4 - Clients wont talk to Domain
      ... > We have been experimenting in the lab with the UPGRADE ... > route for converting our NT4 domain to Active Directory. ... and it's a "feature" because this lets the news clients get ...
      (microsoft.public.win2000.active_directory)