KpyM Telnet/SSH Server - Forum

server sent disconnect message
John	server sent disconnect message	Jun 17 2010 19:28

I had KpyM up and running (primarily using as a synergy tunnel), but today it refuses to connect. I restarted the service and still it gives me the same error. I am using PuTTY as the client, which gives me this: "Server sent disconnect message type10 (connection lost):"" " The logs on the server show this: 7124 : 6988 2010- 6-17 12:16:19 22 : 0: KTS connected to 192.168.1.114:60572 8056 : 8168 2010- 6-17 12:16:19 648 : 0: session.exe started 8056 : 8168 2010- 6-17 12:16:19 702 : 0: connected to 192.168.1.114:60572 8056 : 8168 2010- 6-17 12:16:20 726 : 0: ssh initialized 8056 : 8168 2010- 6-17 12:16:26 113 : 0: login accepted: [ XXXX ] 8056 : 8168 2010- 6-17 12:16:26 191 : 0: can't read first packet 8056 : 7708 2010- 6-17 12:16:26 194 : 0: session.exe end 7124 : 6988 2010- 6-17 12:16:37 120 : 0: KTS connected to 192.168.1.114:60584 7600 : 6432 2010- 6-17 12:16:37 258 : 0: session.exe started 7600 : 6432 2010- 6-17 12:16:37 322 : 0: connected to 192.168.1.114:60584 7600 : 6432 2010- 6-17 12:16:38 329 : 0: ssh initialized 7600 : 6432 2010- 6-17 12:16:43 552 : 0: login accepted: [ XXXX ] 7600 : 6432 2010- 6-17 12:16:44 281 : 0: can't read first packet 7600 : 7536 2010- 6-17 12:16:44 284 : 0: session.exe end 7124 : 6496 2010- 6-17 12:17:37 46 : 0: stopping service 7452 : 6648 2010- 6-17 12:17:38 320 : 0: daemon.exe started 7452 : 5472 2010- 6-17 12:17:38 321 : 0: starting service 7452 : 5472 2010- 6-17 12:17:45 147 : 0: KTS connected to 192.168.1.114:60620 2504 : 5236 2010- 6-17 12:17:45 257 : 0: session.exe started 2504 : 5236 2010- 6-17 12:17:45 329 : 0: connected to 192.168.1.114:60620 2504 : 5236 2010- 6-17 12:17:46 336 : 0: ssh initialized 2504 : 5236 2010- 6-17 12:17:52 316 : 0: login accepted: [ XXXX ] 2504 : 5236 2010- 6-17 12:17:52 576 : 0: can't read first packet 2504 : 6608 2010- 6-17 12:17:52 584 : 0: session.exe end 7452 : 5472 2010- 6-17 12:19:55 807 : 0: KTS connected to 192.168.1.114:60687 6588 : 8180 2010- 6-17 12:19:55 999 : 0: session.exe started 6588 : 8180 2010- 6-17 12:19:56 45 : 0: connected to 192.168.1.114:60687 6588 : 8180 2010- 6-17 12:19:57 51 : 0: ssh initialized 6588 : 8180 2010- 6-17 12:20: 4 920 : 0: login accepted: [ XXXX ] 6588 : 8180 2010- 6-17 12:20: 5 112 : 0: can't read first packet 6588 : 6756 2010- 6-17 12:20: 5 115 : 0: session.exe end Any help would be appreciated.
Kroum Grigorov		Jun 18 2010 04:25

What KTS and Putty versions are you using? Have you made any changes on your KTS host recently -or- in your network. The "can't read first packet" message indicates that the client is already logged in but there was some error receiving the first message from the client. Kroum
John		Jun 18 2010 17:37

I am using 1.19a of KTS and 0.60 of PuTTY. I believe the source of the error was actually with synergy actively looking for the port tunnel before the session was connected. I can repeat this multiple times. If I close the program looking for the port forward, PuTTY connects just fine. Thanks for your response, it encouraged me to take a second look at things!
Kroum Grigorov		Jun 21 2010 14:31

> synergy actively looking for the port tunnel With the current KTS implementation, the port forward tunnel will not be opened before there is an active interactive session and this will take few seconds plus the nag screen. If synergy is trying to just open the port forward tunnel/without the interactive session/ this will not work. Kroum