Re: Sybase Connection - trouble without protocol fallback

2017-06-26 6:10 GMT+01:00 Fredy Paquet <[email protected]>:
> Hello Frediano
>
> Attached, there are two TDSDUMPs which were produced using the compiled
> fisql command. You can see the login packets using protocol version 5.0
> are slightly different.
>
> Between the two runs we were just commenting out the "tds version" line.
> We've stripped out some config search lines for clarity ...
>
> It looks to me as if something isn't reset correctly between the trials.
> I have some time this week to help searching.
>
> Can you give me some pointers where to start searching?
>

Can you try adding

  encryption = request

to the configuration entries ??

> fp
>
> -- fisql_bad.log
>
> $ vs $FREETDS
> [MOKO]
>     host = 192.168.100.2
>     port = 2025
>     tds version = 5.0
>

yes, kind of here.

> $ setenv TDSDUMP /tmp/fisql_bad.log
> $ fisql -SMOKO -Ukommerz -Pguruguru < /dev/null
> Changed database context to 'casy'.
> $ vs $TDSDUMP
> # Search for: tds_process_login_tokens()
>
> -- fisql_ok.log
>
> $ vs $FREETDS
> [MOKO]
>     host = 192.168.100.2
>     port = 2025
> #    tds version = 5.0
>
> $ setenv TDSDUMP /tmp/fisql_ok.log
> $ fisql -SMOKO -Ukommerz -Pguruguru < /dev/null
> Changed database context to 'casy'.
> $ vs $TDSDUMP
>
>
>>
>> Try to use TDSDUMPCONFIG or TDSDUMP if this shed some light.
>> You can post (privately if you want) some dumps (should not be really
>> long as login is failing).
>>

Frediano