Kris - 2013-10-29

I'm using com2tcp-rfc2217 with command 'com2tcp-rfc2217 COM8 7000'. I'm having 2 issues:
- when I disconnect (using ctrl-C or a kill command client side), the server side throws 'ReadOverlapped::OnRead(): TCP(1) ERROR 64 - The specified network name is no longer available'. Is there any way to inform hub4com it can safely disconnect the tcp port, without letting it crash on the read?
- after some time (hours) of connecting/disconnecting, tcp accept starts to fail with a WSATRY_AGAIN and it doesn't recover unless hub4com is restarted

I don't know if the two issues are related somehow. Any help/workarounds appreciated.