DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 5 of 5

Thread: Can't access SQL server on 1433

  1. #1
    mark erickson Guest

    Can't access SQL server on 1433


    Hi,

    Our servers had power failures over the weekend (the power outage lasted
    longer than our battery backups!).

    Subsequently, one of our computers can't attach to SQL server on TCP/IP port
    1433. There are 2 different SQL servers...same inability to connect to either
    SQL server from this machine.

    When I go into ODBC, I CAN connect with named pipes, but not with TCP/IP.

    Query analyzer fails with timeout.

    Netstat shows a connection is being attempted to 1433, but it timed out.

    No problems on any other computer trying to attach to SQL.

    Any ideas?

    Thanks, Mark


  2. #2
    Paul Mc Guest

    Re: Can't access SQL server on 1433


    G'day Mark.

    >Our servers had power failures over the weekend (the power outage lasted
    >longer than our battery backups!).


    >Subsequently, one of our computers can't attach to SQL server on TCP/IP

    port
    >1433. There are 2 different SQL servers...same inability to connect to

    either
    >SQL server from this machine.
    >
    >When I go into ODBC, I CAN connect with named pipes, but not with TCP/IP.


    Sounds like an adressing problem. If your network is using DHCP then the
    power outage would have caused the SQL boxes to have new IP addresses reassigned.
    I would make sure that you are addressing the SQL servers by name and not
    by IP address.

    HTH,
    Cheers,
    Paul

  3. #3
    mark erickson Guest

    Re: Can't access SQL server on 1433


    Hi Paul,

    Thanks for the response! I have verified that the SQL servers are being
    called by name and not by IP. Ironically, when I call the servers by IP
    address rather than by name, the misbehaving computer m_a_k_e_s the connection!
    Also, I can successfully ping the SQL servers both by name and by IP address
    from the misbehaving computer.

    I'm baffled, Mark



    "Paul Mc" <paulmc@nospam.thehub.com.au> wrote:
    >
    >G'day Mark.
    >
    >>Our servers had power failures over the weekend (the power outage lasted
    >>longer than our battery backups!).

    >
    >>Subsequently, one of our computers can't attach to SQL server on TCP/IP

    >port
    >>1433. There are 2 different SQL servers...same inability to connect to

    >either
    >>SQL server from this machine.
    >>
    >>When I go into ODBC, I CAN connect with named pipes, but not with TCP/IP.

    >
    >Sounds like an adressing problem. If your network is using DHCP then the
    >power outage would have caused the SQL boxes to have new IP addresses reassigned.
    >I would make sure that you are addressing the SQL servers by name and not
    >by IP address.
    >
    >HTH,
    >Cheers,
    >Paul



  4. #4
    kevin knudson Guest

    Re: Can't access SQL server on 1433


    Check on the work station that it configured for "multiple Protocol" to the
    SQL server. I can't remember where the setting is , (client config ???).
    I had a machine do something similiar, and found out somehow it had been
    configed to only use TCP/IP. (Actually I probably figured, hey what do I
    need a theis protocal garbage on my network)


    KLK, MCSE


    "mark erickson" <m1erickson@cs.com> wrote:
    >
    >Hi,
    >
    >Our servers had power failures over the weekend (the power outage lasted
    >longer than our battery backups!).
    >
    >Subsequently, one of our computers can't attach to SQL server on TCP/IP

    port
    >1433. There are 2 different SQL servers...same inability to connect to

    either
    >SQL server from this machine.
    >
    >When I go into ODBC, I CAN connect with named pipes, but not with TCP/IP.
    >
    >Query analyzer fails with timeout.
    >
    >Netstat shows a connection is being attempted to 1433, but it timed out.
    >
    >No problems on any other computer trying to attach to SQL.
    >
    >Any ideas?
    >
    >Thanks, Mark
    >



  5. #5
    mark erickson Guest

    Re: Can't access SQL server on 1433


    Hi Kevin,

    That's it!

    I went into the ODBC manager. There is a button during DSN setup that offers
    "Client Configuration". I set up one DSN to use Named Pipes and another DSN
    to use TCP/IP. The malfunctioning computer now plays happily with the SQL
    servers!

    Thanks, Mark


    "kevin knudson" <klk@knudsons.com> wrote:
    >
    >Check on the work station that it configured for "multiple Protocol" to

    the
    >SQL server. I can't remember where the setting is , (client config ???).
    >I had a machine do something similiar, and found out somehow it had been
    >configed to only use TCP/IP. (Actually I probably figured, hey what do I
    >need a theis protocal garbage on my network)
    >
    >
    >KLK, MCSE
    >
    >
    >"mark erickson" <m1erickson@cs.com> wrote:
    >>
    >>Hi,
    >>
    >>Our servers had power failures over the weekend (the power outage lasted
    >>longer than our battery backups!).
    >>
    >>Subsequently, one of our computers can't attach to SQL server on TCP/IP

    >port
    >>1433. There are 2 different SQL servers...same inability to connect to

    >either
    >>SQL server from this machine.
    >>
    >>When I go into ODBC, I CAN connect with named pipes, but not with TCP/IP.
    >>
    >>Query analyzer fails with timeout.
    >>
    >>Netstat shows a connection is being attempted to 1433, but it timed out.
    >>
    >>No problems on any other computer trying to attach to SQL.
    >>
    >>Any ideas?
    >>
    >>Thanks, Mark
    >>

    >



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center