Post reply

Timeout expired error

  • October 10, 2001 at 1:58 am

    #57818

    Hello all,

    I'm trying to connect to a remote SQL Server using my EM. I'm logging in using the SQL authentication.

    Im getting a timeout expired error. What must be the problem?

    I checked the protocol, its TCP/IP only. What else might be the problem?

    Cheers

    Parasu Raman


    Regards
    Parasu Raman

  • October 10, 2001 at 2:00 am

    #418787

    Have you checked the protocol's of both machines?

    Steven

  • October 10, 2001 at 7:20 am

    #418795

    Yes I did. Its the same in both the machines

    Parasu Raman


    Regards
    Parasu Raman

  • October 10, 2001 at 7:23 am

    #418796

    Can you connect using Query Analyzer? Can you ping the machine? Try connecting using the IP address instead of the machine name.

    Andy

    Andy
    SQLAndy - My Blog!
    Connect with me on LinkedIn
    Follow me on Twitter

  • October 10, 2001 at 7:28 am

    #418798

    Are you connecting via name or IP. If you are connecting via name try using the IP instead.

    Steven

  • October 10, 2001 at 11:28 am

    #418812

    Is this SQL 7 or 2000? Does the server have TCP/IP sockets setup? Check the server network utility as well as the client network utility on the client.

    Steve Jones

    steve@dkranch.net

  • October 11, 2001 at 12:52 am

    #418833

    Hi,

    1. I tried connecting using QA, im getting the same error. Im able to ping and also i tried using the IP to connect. The result is same.

    2. Im using SQL Server 7.

    3. I do find TCP/IP at both client and server network utility of the client.

    But, should i do something else to configure the TCP/IP socket?

    Cheers

    Parasu Raman


    Regards
    Parasu Raman

  • October 11, 2001 at 1:40 am

    #418835

    When you checked the 'Client Network Utility'

    was TCP-IP the top of the protocols list?

    If not move it to the top

    Steven

  • October 11, 2001 at 6:53 am

    #418836

    Hi,

    I find the TCP/IP at the top only...

    Parasu Raman


    Regards
    Parasu Raman

  • October 11, 2001 at 6:59 am

    #418838

    Are there any firewalls between the two machines blocking port 1433?

    Steven

  • October 11, 2001 at 7:14 am

    #418841

    Nope. Its both in the same LAN

    Parasu Raman


    Regards
    Parasu Raman

  • October 11, 2001 at 7:19 am

    #418842

    Create a UDL (Microsoft data link) from the desktop on the machine. Try and connect to the server using the sql driver and nt security. Then use the test connection to see if a connection can be made.

    If nothing else you will know that the servers can talk.

    Steven

  • October 11, 2001 at 7:35 am

    #418843

    Yes,

    Im able to connect successfully to the server using a DSN. I guess, u meant only this when saying UDP. If not, kindly explain

    Parasu Raman


    Regards
    Parasu Raman

  • October 11, 2001 at 7:40 am

    #418844

    UDL - In around MDAC 2.1SP2 a new feature was added (UDL). It basically is a quick way of creating a connection string with a gui front end.

    Create a file in a directory called test.udl

    Double click on it and the 'data link' screen should be displayed.

    and fill in the properties ie the driver, the server, security etc.

    One other nice feature is if you open the udl file in notepad. It gives you the full connection string which can be used in VB, ASP etc. hence it sames those typos etc.

    Regards

    Steven

  • October 11, 2001 at 7:47 am

    #418847

    Ooops! Sorry I meant Steven!!!!

    David

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

Viewing 15 posts - 1 through 15 (of 29 total)

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