If a customer is reporting time-outs you need to adjust these properties below. Note: The settings shown ARE NOT NECESSARILY CORRECT and will change depending on the SITE.
Here are all the time-out fields for KTS.
pass_timeout is relevant to the question below... basically increasing the amount will improve the situation. These values are in seconds... a password time-out means the server did not get the password from the client - i.e. it got the username but not the password. This indicates a "DIFFERENT PROBLEM" not just a timeout - it generally points to a network issue (Bad Wifi at the point the gun is trying to remain connected.)
I would recommend that Max_login_attempts is also increased significant to avoid a user getting "blocked out". Make it at least 10 - this can happen on bad connections - where a login is started but the connection fails - it will also count as a bad login. If this occurs the user IP address is added to a BLACKLIST and the handheld not able to login again ever until the ip is cleared from the folder.
pass_timeout = 30
idle_timeout = 300
io_timeout = 30
max_login_attempts = 3
net_check_delay = 300
refresh_delay = 100
health_monitor_timeout = 1000
Furthermore - there are improved TELNET CLIENTS (WaveLink) which have better connection management - but are not free - and for those with connection issues we recommend they upgrade to that - but we cannot guarantee it will resolve the issues as the WiFi is usually the cause of the problem / either bad coverage or intermittent interference.
KTS_HOWTO: kts and firewall
KTS and firewall.
Since the firewall filters network traffic and KTS is server software your firewall will mostly detect KTS, when it is started. To use KTS together with your firewall you will have to make few adjustments in your firewall configuration.
1) KTS telnetd.exe file must have access to the network.
2) KTS telnetd.exe file must be allowed to act as a server. This is the server component of KTS that handles incoming connections e.g. the server component of KTS.
3) You should allow incoming connections on port 23 (this is the default telnet port; if you change KTS port to custom one then you should allow your custom port in the firewall)
If KTS is blocked by your firewall, you will have a behavior similar to the following:
In the kts log file (log\kts-log.txt) there will be only lines saying that kts is started or stopped. A normal log file will show connection attempts too, successful or unsuccessful. Using a telnet client it may seem that you connect to your host but the client will display blank screen. Actually, you are "connecting" your firewall, depending on your firewall it may refuse connection, forcing your client to disconnect (or not connect at all) or it could just take the connection silently. If you experience any of these symptoms, check your firewall settings, most probably the problem is buried there.