Re: Only TDSVER=4.2 works when connecting to MS SQL 2005
"James K. Lowden" <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 22 Aug 2011 14:50:36 -0700 "Michael Gurfinkel [TSS]" <[email protected]> wrote: > My setup is : > MS SQL 2005 running under Win 2003, > Latest 0.91 version of FreeTDS under Unix (SCO) > I build it with ./configure --enable-msdblib --with-tdsver=7.2 > I use $HOME/.freetds.conf to configure connection > > I can connect to the db only when my tds version is set to 4.2, > when I tried 7, 7.1, 7.2, 8 it fails to connect. > > My question - would it be limiting factor? Yes. You want to figure out what's wrong. > 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? Whenever we've seen this before, it's seems it's always been something like that. --jkl