Skip to Content.
Sympa Menu

freetds - Re: [freetds] freetds failed to connect to MSSQL server ends with error ( Unable to open socket There was a problem connecting to the server )

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: jklowden AT schemamania.org
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] freetds failed to connect to MSSQL server ends with error ( Unable to open socket There was a problem connecting to the server )
  • Date: Mon, 14 Sep 2009 12:04:43 -0400

On Mon, Sep 14, 2009 at 12:13:32PM +0200, Arlen Drina wrote:
> I read all what is already suggssted here :
>
> https://lists.ibiblio.org/sympa/arc/freetds/2009q3/024997.html
>
> I do know much about freetds so any help is welcome. Bellow are
> outputs of proposed step on link above.
> I have also debian+freetds 0.8.2 but I cannot connect to MSSQL server
> using isql or tsql .
...
> 11:35:29.422216 21769 (log.c:190):Starting log file for FreeTDS 0.82
> on 2009-09-14 11:35:29 with debug flags 0xffff.
...
> 11:35:29.423411 21769 (net.c:210):Connecting to 1.1.1.1 port 1433 (TDS
> version 8.0)
> 11:35:29.427509 21769 (net.c:264):tds_open_socket: connect(2) returned
> "Operation now in progress"
> 11:35:29.970187 21769 (util.c:334):tdserror(0x90100a8, 0x90109d8, 20008, 4)
> Msg 20008, Level 9, State -1, Server OpenClient, Line -1
> Unable to open socket
> 11:35:29.970414 21769 (util.c:368):tdserror: client library returned
> TDS_INT_CANCEL(2)
> 11:35:29.970519 21769 (util.c:389):tdserror: returning TDS_INT_CANCEL(2)
> 11:35:29.970621 21769 (net.c:310):tds_open_socket() failed
> 11:35:29.970737 21769 (mem.c:563):tds_free_all_results()
> There was a problem connecting to the server

http://freetds.cvs.sourceforge.net/viewvc/freetds/freetds/src/tds/net.c?revision=1.71.2.1&view=markup&pathrev=BRANCH0_82

Disregard my prior message. The error "Unable to open socket" is misleading
in 0.82. It should report, "Unable to connect". (One difference between CVS
HEAD and 0.82 is that in 0.82 an error returned by connect(2) is reported as
a socket error. It should be and currently is reported as a connection
error.)

Are you able to telnet to 1.1.1.1 port 1433? The message says you can't.

--jkl




Archive powered by MHonArc 2.6.24.

Top of Page