SQL Server Performance

SQL State HYT00. Timeut expired

Discussion in 'General DBA Questions' started by KGautney, Jul 23, 2007.

  1. KGautney New Member

    I am trying to create an ODBC connection from serverA to serverB.
    I can ping serverB from serverA and visa versa. But I cannot successfully create an ODBC connection. I receive the following error:

    ODBC Connection Failed
    SQLState HYT00
    SQL Server error 0
    Timeout Expired

    Anyone have any ideas?
    Kris
  2. ghemant Moderator

    Hi,
    what is protocol set for both server!! Have you try with named pipe protocol?
    Also ensure their is no network congestion.

    Regards

    Hemantgiri S. Goswami
    MS SQL Server MVP
    -------------------------
    "Humans don't have Caliber to PASS TIME , Time it self Pass or Fail Humans" - by Hemantgiri S. Goswami

    http://hemantgirisgoswami.blogspot.com
    http://forum.sqlknowledge.com/

    Disclaimer: This post is provided as is, for the sake of knowledge sharing only.
  3. Chappy New Member

    Is there any firewall in between the servers ?
    Ping uses ICMP, but ODBC is TCP/IP and so still could be blocked
  4. satya Moderator

    Also you have to check the SQL Server alias, as it may be causing errors as your client is having difficulty mapping names to IP addresses. If you are using ODBC DSN, in the Which SQL Server do you want to connect to ? drop down, type the IP Address of your SQL Server box instead of the alias.

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    @http://www.askasqlguru.com/

    This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
  5. KGautney New Member

    I was able to connect using named pipes. I have never used ICMP before, what is the syntax at the command line to test?
  6. KGautney New Member

    THanks so much for the help.
    Using the server name instead of the IP worked. So what is the resolution for this if I need to be able to map to an IP?
  7. Adriaan New Member

    IP address will work for TCP/IP traffic only.

    To find the server name for your IP address, try this from a command line:

    ping -a .........

    ... adn fill in the IP address on the dots.
  8. satya Moderator

    If you are unable to connect by Server name then ensure you have added within the LMHOSTS file on that machine for this server name.

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    @http://www.askasqlguru.com/

    This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
  9. Chappy New Member

    <blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by KGautney</i><br /><br />I was able to connect using named pipes. I have never used ICMP before, what is the syntax at the command line to test?<br /><hr height="1" noshade id="quote"></font id="quote"></blockquote id="quote"><br /><br />Dont worry too much about ICMP, its just a form of UDP (as opposed to TCP), and is what ping uses. <br /><br />My reason for mentioning it, is that just because you can ping the server, doesnt mean you can create a TCP socket to it. Potentially theyre different firewall rules see<br /><br />But to be honest, Id overlooked the fact youre probably using named pipes anyway <img src='/community/emoticons/emotion-1.gif' alt=':)' />

Share This Page