From: Sven Köhler (skoehlerupb.de)
Date: Mon Mar 22 2004 - 16:25:52 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

it's me again with the old nice sweet litte bug that's internally called
with the short name "ODBC driver reports error '709 connection refused'
although the ODBC driver can establish a TCP/IP-connection and get's a
'rejected bad connect packet' message from the server that you can
easily see if you're using ettercap".

I'm a little but ironic, since i reported the Bug twice already and now
i have the following situation here at home:
- a Linux Server with MaxDB 7.5.0.8
- a Windows XP Laptop with SQLStudio 7.5.0.5
- a Windows XP Desktop with SQLStudio 7.5.0.5
- a Linux Server with SAPDB 7.4.x.x

The Desktop PC is a fresh installation of WinXP. This installation
hasn't seen any SAPDB/MaxDB Software before i installed SQLStudio.

If i use the Desktop PC to connect to the MaxDB 7.5 Server, than i get
the famous "error 709" and if i use the Laptop, everything works!

Both computers can connect to the SAPDB 7.4 Server.

I'd like the following to be done:
- Fix the stupid error message reported by the ODBC driver since
"connection refused" lets everybody think of the TCP/IP-error instead of
a "rejected bad connect packet" from the server
- Bring some light into the darkness how this can happen, that two
installations of the same software can behave that different
- Figure out why the ODBC-driver doesn't want to connect to the MaxDB
Server since the error now occures with both ODBC-driver installations:
the SQLSTUDIO-specific installation the the general standalone installation.

I wish i had a real bugtracking-system like Bugzilla or something, since
i don't want to tell the whole story over and over again.

Thx
   Sven

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]