SSL_ERROR_SYSCALL, errno 104, on remote PC

[edilpali]

I have 1 PC in my network connected throu VPN.
2 weeks ago, I changed the firewall VPN and updgraded WtWare to the lastest 6.2.30 version.
The PC started to stop the connection with the screen error "TCP/IP connection lost. Network failure?"
Sometimes, it takes 3 or 4 tries to connect or reconnect.
I thought the guilt was the new firewall, but logs said nothing at all.
I downgraded the PC to the 6.2.2 version, and all works!
I send the logs of the 2 versions.

[edilpali]

It seems that the 6.2.28 version works too.
I attach the log

[akatik]

errno 104 is "connection reset by peer". Only peer (RDP server in this case) knows why it reset connection. It does not tell us the reason. We only can change something and retry...

The most significant difference between 6.2.28 and 6.2.30 is related to TCP connection is new linux kernel. TCP stack lives in kernel, and part of SSL stack too.

Please make simple check: configure MTU. In 6.2.30 press Del to enter WTware setup and set MTU 1300 or less if you know the value. Will error 104 repeat with smaller MTU set?

I can make wtware test builds with newer kernel (6.9.10 on kernel.org while 6.9.7 in WTware 6.2.30) or go down to 6.6.x as in WTware 6.2.28 if you can test them.