16.6. Troubleshooting
F-Secure
SSH Client, like any other SSH client, can run into unexpected
difficulties interacting with an SSH server. In this section we cover
problems specific to F-Secure SSH. For more general problems, see
also
Chapter 12, "Troubleshooting and FAQ".
- Why is scrolling so slow for F-Secure SSH for Windows?
-
At press time, F-Secure's scrolling speed is quite poor, but
you can speed it up somewhat by turning on jump scrolling, which is
disabled by default. It can be enabled only through F-Secure's
key-mapping facility. The following setup enables jump scrolling for
one given Session File:
- In your F-Secure installation directory, locate the file
Keymap.map.
- Edit this file and locate the line containing "enable
fast-scroll-mapping".
- Uncomment this line by removing any "#" symbols at the
beginning of the line.
- Save and close the file.
- In the Edit menu, select Properties.
- In the Properties window, select
Keyboard.
- Under Map Files, in the Keyboard blank, enter the path to the
Keymap.map file you edited.
- Click OK.
You can now toggle between smooth and jump scrolling by pressing
Control-Alt-F3. Press this key sequence once in
your F-Secure SSH session, and your scrolling will become speedy.
- I got the error message "Warning: Remote host failed or refused
to allocate a pseudo tty."
-
Your server's SSH-1 authorized_keys file
might have the no-pty option specified for the
corresponding public key. [Section 8.2.9, "Disabling TTY Allocation"]
- I can't do port forwarding. I get a message that the port is
already in use.
-
Do you have another F-Secure window open and connected with the same
port forwarding setup? You can't have two connections
forwarding the same local port. As a workaround, create a second
configuration that duplicates the first but with a different local
port number. Now you can use both connections simultaneously.
- I tried using the Key Registration Wizard but it didn't work.
The Wizard said "Disconnected, connection lost."
-
First, verify that your hostname, remote username, and remote
password are given correctly. If they are definitely correct, click
the Advanced button and check the information there. Is the SSH-2
server running on the default port, 22, or a different one? Do the
SSH2 directory and authorization filenames you provided match the
ones on the server?
Another possible (and more technical) cause is a missing or
incomplete sftp-server subsystem entry in the
server's /etc/sshd2_config file.
F-Secure recommends that the fully qualified path to
sftp-server2 appear in this entry, or else the SSH server
possibly can't locate it. The Key Registration Wizard uses the
SFTP protocol to transfer key files. The system administrator of the
server machine needs to make this change.
- How do I prevent the initial welcome window from being displayed in
F-Secure SSH2?
-
For Windows, modify the Registry value:
HKEY_CURRENT_USER\Software\Data Fellows\F-Secure SSH 2.0\TnT\Settings\ShowSplash
The default is yes; set it to
no. The next time you run the program, no welcome
window appears. (This is an undocumented feature.)
- How do I eliminate the Logon Information window that pops up when I
run F-Secure SSH2 Client? I'm using public-key authentication
so the window seems unnecessary.
-
In the Properties window, select Connection, and check the box Auto-
Connect On Open.
| | |
16.5. Forwarding | | 16.7. Summary |