Results 1 to 2 of 2
  1. #1
    Join Date
    Jun 2005

    Unanswered: Can't connect to SQL server 2000.....

    I have SQL server 2000 installed on machine A and when I try to connect using machine B, I get the error message:

    A connection could not be established to "servername"

    Reson: Timeout expired.

    I have been able to connect to the machine in the past and this morning, the server was rebooted and now I can't connect. I can see the server using enterprise manager and I can start and stop machine A from B, but I just can't connect. Any ideas?


  2. #2
    Join Date
    Dec 2002
    Lots of places to start checking, but try the SQL Server Error logs first. Look for the following entries:

    2006-01-26 11:09:34.59 server    Using 'SSNETLIB.DLL' version '8.0.2039'.
    2006-01-26 11:09:34.62 server    SQL server listening on xx.xx.xx.xx: 1433.
    2006-01-26 11:09:34.62 server    SQL server listening on 1433.
    2006-01-26 11:09:34.71 spid3     Server name is 'MYSERVER'.
    2006-01-26 11:09:35.62 server    SQL server listening on TCP, Shared Memory, Named Pipes.
    2006-01-26 11:09:35.73 server    SQL Server is ready for client connections
    If something is amiss here, google the error message and start from there.

    Next try telnetting to your server's ip address on port 1433 (or whatever port SQL says it's listening on). From a command window, type telnet MyServer 1433. The command window should blink, go entirely black and nothing else. If you get a response like 'cannot connect', then there are network issues (or the SQL Server service is not started.

    Try starting there...


    Have you hugged your backup today?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts