Sporadic Connection Timeout

anonymous_at_discussions.microsoft.com
Date: 07/10/04

  • Next message: User: "Re: ADO on MDAC 2.8"
    Date: Sat, 10 Jul 2004 12:03:21 -0700
    
    

    The problem is solved.

    I noticed that I could not access the shares on
    the SQL Server machine (although from some clients
    I could). Logon server could not be located.

    This sent me back to the newly-demoted PDC
    (now BDC). It was confused as to whether it
    was a BDC or PDC (demotion had not been entirely
    clean). So, I had a situation where I
    had 2 PDCs on the network. Once I successfully
    demoted it, connection could be made via
    ODBC using any network library available.

    --john

    >-----Original Message-----
    >The network consists of 3 servers: a BDC, a PDC
    >and a stand-alone server. There are about 30 client
    >workstations (some Win98, some WinXP Pro).
    >
    >SQL Server 7.0 is running on the stand-alone, which is
    >running Win2k.
    >
    >The stand-alone server was brought up and SQL Server 7.0
    >installed approx. 6 months ago. Previously, SQL Server was
    >running on the BDC for 4 years. The BDC and PDC are both
    >WinNT SP6, but the current PDC is to be retired and
    >the BDC to be upgraded to Win2K Active Directory.
    >
    >The systems have been operating well for 6 months.
    >
    >Promoted the BDC to PDC. Did this yesterday. No changes to
    >the stand-alone (SQL Server) machine.
    >
    >Network logins are fine; can browse network resources
    fine.
    >
    >As of today, intermittently, some machines connecting to
    >SQL Server via ODBC system DSN receive connection time-
    out.
    >SQL Server set to "unlimited". (Connection is via
    >SQL Server login, not Windows authentication.)
    >
    >Network libraries loaded on SQL Server include TCP/IP,
    >Named Pipes and Multiprotocol.
    >
    >When ODBC connection times out, attempting again, it
    >sometimes then works fine. Other times, you need to
    >change the client connection method to TCP/IP, and
    >ensuring port is set to 1433, it then works fine, but
    >login to database is slow (indicates a potential
    >name resolution problem, which I will be looking at as
    >well).
    >
    >This all was working, and the ODBC connections have
    >been unmodified for a minimum of 6 months.
    >
    >Because the servers all can ping each other, browse
    >each other, etc., it does not seem to be a security
    >issue.
    >
    >I will be running the MDAC checker, but there have been
    >no MDAC changes since the stand-alone server was
    >brought up.
    >
    >Any thoughts??
    >
    >Thanks
    >
    >--john
    >.
    >


  • Next message: User: "Re: ADO on MDAC 2.8"

    Relevant Pages

    • Sporadic Connection Timeout
      ... The network consists of 3 servers: a BDC, a PDC ... The stand-alone server was brought up and SQL Server 7.0 ...
      (microsoft.public.sqlserver.odbc)
    • NEW SBS 2003 Purchase
      ... I am the admin of a small network. ... users over our WAN for a total of 39 users. ... that utilizes MS SQL server and all need access to e-mail. ... this machine will need to be my PDC. ...
      (microsoft.public.backoffice.smallbiz2000)
    • Re: NEW SBS 2003 Purchase
      ... > I am the admin of a small network. ... > users over our WAN for a total of 39 users. ... > that utilizes MS SQL server and all need access to e-mail. ... this machine will need to be my PDC. ...
      (microsoft.public.backoffice.smallbiz2000)
    • Active Directory Windows Authenticatio
      ... Can Someone tell me if SQL server 2000 is fully active ... directory aware or does it rely on having a PDC or BDC ... emulation running on one of the active directory servers. ...
      (microsoft.public.sqlserver.security)
    • Re: Microsoft PDC 2004
      ... Yes, I suppose there will be a big PDC 2005 (hint: ... Sql Server 2005, ...) ... miha at rthand com ...
      (microsoft.public.dotnet.general)