The following is a list of frequently asked questions and problems regarding PockeTTY®. If your problem is not explained here, please send us a report explaining what you were doing at the time of the error.
If you haven't yet, you may want to take a look at the on-line manual. If the problem isn't explained in the manual, or the manual is wrong, please tell us that too!
Note: Make sure you're using the latest version of PockeTTY, which you can download from PockeTTY's main web page. It may be that we've already fixed your problem.
Known bugs in the current version of PockeTTY are listed on the main PockeTTY page. Please check there before you look any further.
If the server you're trying to connect to is running OpenSSH version 3.1p1 or 3.4p1, you're probably running into a known bug in OpenSSH. This is not a problem with PockeTTY. Contact the system administrator for the server. In the meantime, if the server is OpenSSH 3.1p1, use SSH2/Blowfish. If the server is OpenSSH 3.4p1, you can use SSH1/3DES or any SSH2 variant.
International versions of Cisco IOS only support DES encryption; only their domestic versions of IOS support 3DES. Since PockeTTY does not currently support (insecure) DES encryption, it is only able to connect to domestic versions of IOS. Also, be aware that domestic versions of Cisco IOS prior to 12.1(3)T contain serious bugs which may prevent PockeTTY from connecting.
1.3: Connecting with SSH2 seems really slow. Why? Can anything be done to speed things up?
SSH2's authentication methods require computations using very large numbers. This makes it very secure, but very slow. Handheld devices have slower CPU's than desktop machines, don't have math co-processors, and generally have a small number of CPU registers. All these factors make big math very time-consuming.
That said, there are some things you can do. You can set the "security slider" to the "Faster connection" position, as described in section 3.3.8 of the manual. You can also choose to use RSA host keys rather than DSS (section 3.3.7), and/or a fast cipher such as Blowfish (section 3.3.1). Note that each of these will slightly decrease the security of your connection, so you'll need to find where you're comfortable within the speed vs. security tradeoff.
As described in section 3.3.6 of the manual, PockeTTY can only accept a private DSS certificate that is in PEM format. Your certificate may not be readable for some reason or is not in PEM format. A sample encrypted certificate in the proper format appears below.
-----BEGIN DSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,E12DEB2D03663CF5 kAI+PggBL/qcKaV9CpPOf22xWaze1BGimfcHxyUa2SGYEA/qL3gVgjNXo8MKMEiC r4gVDoxIhrqRQc6tO/VHxNuQyo32lwccV/RUyxffsMV9hk13VP0schiDiIurGz5u vUEWQntGiy+uan8ESX1+KECK9u8g/sfGUhJY7XIQ54TvwRBDCDmSr8LIt6RDTxZC sIBwPMPhGv+MeVFjJU1KP2ah9BVpp18w5C4m7EMXYGZYS6LoEdVeZ8JU4TTf1LFu r0uxXtMzi9MqEq1XbhkNHtg+TpvxpEYmFseQWrBQERG6odg9MMTCyCXSpjrDLMd7 4xkQKcZYvCDmsQivnZrREPUV0RRHNe793XtZjEk34CoNstTgeDjLXlOjjwWzdfuo Mj9t9yC0vUpkLchnSChPtqcbPCmMAfvIEGsGST4zOAw8apc/t27UzgL1cxMAWTSQ mYxI5OqUs0HYl5bIY3+sb7LYE/640n+JxEQf86JsC1+kIgsPKwG+CmGVFccdDG7/ NuVQok1jRhAzW+xr5tOBc67jk3yCGowxrqAB/NEA93VTajn2DGVKLGONY9W0UpFi 0cPGM4B4tmVA3NOHVqdUeA== -----END DSA PRIVATE KEY-----
PockeTTY also accepts unencrypted certificates, which look like this:
-----BEGIN DSA PRIVATE KEY----- MIIBuwIBAAKBgQDCq9Y3N2yyyC3aGUQ3v8iKGj8TcVKKueGJy2cYpFm2pdCp8Lo/ 2loEMrPEcA8SkOl0FOicNYbzEKZf0h+KQzIp1v2MQWqmOCLzjudESbYv7lT9p0aH 8gUGCPaCI5woGE8GJ7HmovWdeR3UEkX1t7cQpVxXy2vQqXHWyUV8+R5IrQIVAImJ KU/lm0By9jPPMHpd6IZN4VUZAoGAX9pZw2ykuDMqf+9GTGmiN7IS7/CqKgipt9Ch FAjUHpq0rvVI7d6gMQBfiw5akX73+NrGUpTGy2/1jz71kEmB0A09XVuREqPAqxBr HaoXBGCR7Rzf4BJJwzAay2GKNf67ia56WSgR1UnZmznHeFSKlGhDN/MFosDovtH4 hUiS4toCgYEAiJUR9XhRv9OxFk4yN3erDTWXI4XOmipVMKrrzVgDdC7Lo7gCW8zv dS6ak7GvBCDBeLsadtjeviGnTz4gbWJJXjNIngh2OtYlskQS5g+cArDEyRSiqs/h zLT1uuCzvt6W0LNPOBbS9fkKFLGybKkCjzPHITAzRv+n63Qo4H7sI/kCFDD8/MeA lW7ybFslMx1zzxr9mKm2 -----END DSA PRIVATE KEY-----
If you have OpenSSH installed on your server, the command ssh-keygen -t dsa will generate a key in this format.
The server you're trying to connect to has SSH's password authentication turned off to use some other type of password system, like S/KEY. For OpenSSH, in the /etc/ssh/sshd_config file on the server the PasswordAuthentication option is set to 'no'. This must be set to 'yes' for PockeTTY to connect. A future version of PockeTTY will provide support for other authentication methods such as S/KEY. For servers other than OpenSSH, consult server's the documentation for information on how to re-enable password authentication.
1.6: I want to set up a remote port forward (host -> PockeTTY), but in section 3.2.3 of the manual it only describes local port forwards (PockeTTY -> host). How can I set up a remote port forward?
The current version of PockeTTY only supports local port forwards. There is no support for remote port forwards.
1.7: When I try to connect I see "Unknown error 10065".
This error indicates that your device does not currently have a network connection. Some applications such as Pocket IE will attempt establish a network connection if one does not already exist. If you have a pre-WM2003 device PockeTTY assumes that you already have a connection. You need to establish a network connection before using PockeTTY, either using Pocket IE or through some other means. If your device runs WM2003 or later and you're getting this message, let us know.
If your Bluetooth device isn't in the list it probably means that the device isn't connected to your device, or that there's some other Bluetooth problem that's out of our control. Sorry we can't be of more help on this, but Bluetooth is a real mess. If you find a solution though please let us know and maybe together we can help someone else.
The default for terminal dimensions is set to 24 rows by 80 columns. Some devices, particularly VGA devices, are capable of displaying a much larger terminal. Here's how to start using all of the available screen (or as much as you want to):
As of PockeTTY 3, you can also use the Fit To Screen feature. This will scale the currently selected font to fill as much of the screen as possible.
2.2: Does PockeTTY support Big5 characters?
PockeTTY does not support Big5 or other character encoding methods, basically because its internal architecture is not designed for multibyte character sets. Implementing this feature would mean significant restructuring of the code, and as such is not a high priority for us.
While hardware issues aren't really what we deal with, we've had some questions so often that we decided to put them on the FAQ.
Socket Communications makes a CompactFlash card that provides an RS-232 connector, if you have a device with a CF slot. Since most modern devices don't, your only other option would be a Bluetooth serial adapter. We've used the Cordless Serial Adapter from Socket Communications on our devices with some success, but unfortunately, Bluetooth is quite persnickety and there's no way to tell whether or not this is going to work for you.
3.2: I wish my hardware keyboard had a Ctrl/Esc/whatever key. Can PockeTTY remap the keys for me?
Section 4.2.5.1 of the manual describes Soft Control Key handling, which may solve your problem. We didn't put full keyboard remapping functionality into PockeTTY because there's already a great product out there that does this. Have a look at AE Keyboard Mapper. Tell 'em we sent you.
