http://bugs.winehq.org/show_bug.cgi?id=21387
Summary: NetTerm locks up Product: Wine Version: unspecified Platform: x86 URL: http://www.securenetterm.com/pub/nt325405.exe OS/Version: Linux Status: UNCONFIRMED Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: nerv@dawncrow.de CC: support@securenetterm.com
This is a Bug discussed in Bug 11621 but not belonging there. Summary:
As the author of NetTerm, SecureNetTerm, SNetTerm and SecureFTP, I am seeing the same problem with NetTerm that I see with Putty as it relates to the telnet connection problem.
Our SNetTerm product, as well as the Microsoft telnet.exe DOES NOT have this issue.
Is there been any additional information on this issue that would help us get this resolved? Where to look? Anytime we can test in the winsock area to help resolve the issue?
I am not sure that this is all that is going on. Our NetTerm product DOES NOT send a SIOCATMARK, yet the behavior is much like Putty's. That is, it connects to the host ok, then about 2-3 seconds after the connect, it freezes.
Note that it IS NOT a the same place everytime. That is, if I run NetTerm without a script, I cannot type fast enough to enter my userid at the Login: prompt before the application locks up. However if I use a script, it logs in and gets to the command line then locks up.
It appears that some type of timer is involved.
The really strange thing is our SNetTerm product is not affected by the bug at all. It does a telnet connect and everything works ok. The same is true for the Microsoft telnet.exe program.
The current version of NetTerm can be downloaded from:
http://www.securenetterm.com/pub/nt325405.exe
and includes a 60 day trial period. If more time is needed, or has been downloaded before and trial period has expired, contact me at support@securenetterm.com and I will send a new key.
I found the problem. It is in the telnet tcpip network code, sort of like the Putty problem. NetTerm locks up when it issues a winsock recv()call for 1 byte with MSG_PEEK in the flags field.