Re: Only TDSVER=4.2 works when connecting to MS SQL 2005

On Tue, 6 Sep 2011 13:46:29 -0700
"Michael Gurfinkel [TSS]" <[email protected]> wrote:

> > > 14:36:28.595890 3933 (login.c:1057):detected flag 2
> > > 14:36:28.595903 3933 (login.c:782):quietly sending TDS 7+ login
> > > packet
> > ...
> > > 14:36:28.596526 3933 (dblib.c:7929):dbperror(804f988, 20017, 0)
> > > 14:36:28.596541 3933 (dblib.c:7981):20017: "Unexpected EOF from
> > > the server"
> > 
> > The server is rejecting your login, but not for a bad
> > username/password (else you'd see a message).  Is there some sort of
> > encryption or Kerberos login being used, or supposed to be?  
> 
> I am not aware of any encryption or Kerberos login, but I don't know
> how to validate it. All I know this is 2005 SQL Server with
> authentication set to mixed (Windows and SQL Server) mode. 

This for sure: FreeTDS logs in to Microsoft servers for thousands
of users every day.  What you're seeing is therefore attributable to
the server's setup.  

Perhaps FreeTDS should be able to handle that setup, but behaves in a
way unacceptable to the server. Unfortunately, the server's response in
such cases is unhelpful: it simply hangs up.  That leaves you with some
investigation to do.  

You could try other servers, even install the Express product, and then
triangulate settings with your DBA.  Or you could recompile FreeTDS to
log the login packets, which would show exactly what happened, but not
necessarily in the most comprehensible form.  

> What would be my limitations if I will use 4.2?  

You don't want to do that.  You lose BCP and every datatype added in
the last ten years, and you'd probably find other mysterious "features"
because you'd be running the only 4.2 connection since the Mets last
won the World Series.  

--jkl