FlexLM and "tcp_s is bad"

[Uwe Bonnes]

Hallo,

I have a demo of a commercial Linux application, which comes with FlexLM
protection but doesn't have a Linux vendor daemon. Running windows flexlm
with the windows vendor daemon and --winver win95 --dll netapi32=b works
fine and will save me having to run a NT Box with VMWare in the
background. 
Good!

Running Linux flexlm calling the windows vendor daemon via wine
however doesn't work. Flexlm aborts with a message "tcp_s is bad!!!".
Could this tcp_s be some sequence number that our present winsock
implementation does wrong somehow? I can give more evidence on reqeust.

Any help appreciated.

Bye