There's a few reasons the session can be ended. The most common cause is NAT, which can limit you to 10 total sessions. This is detected by looking at the connections list for device IP addresses that are hyphenated with two values. This is resolved by turning on NAT support under Server Configuration > Server Settings > Enable Server-Side Support for Client Dynamic NAT.
It could also be duplicate Unique IDs (each client needs a unique value). The symptom of this would be devices that steal a session from another device. Details about this can be found under session persistence.
It's also possible that the telnet server or host application ended the session. These programs should have logging recording why they would end the session. We can enable StayLinked logging to validate what was sent to the host before the session was ended if it's helpful.
Lastly, and the one reason we can't do anything about, is if there's a network interruption or packet drops between the telnet host and StayLinked server process. Terminal Emulation protocols are not built for reliability/interruption. This is why we recommend the StayLinked Server resides on the telnet host whenever possible, keeping that traffic internal to the host machine. Standard network troubleshooting is required to diagnose this issue (ping, tracert, packet captures, etc).
Share the post "Session Ended Unable to Reconnect"