Troubleshooting Beyond FTP Connections
Problems with Beyond FTP connections are either call establishment or security related. Call establishment problems usually result in time-out errors being returned to Beyond FTP after you have double clicked the server name. The first thing to do in this case is to edit the address book entry and check the server address. You might also open a command window or DOS box and use the PING command by typing:
PING <server address>
If this result in “Request timed out” messages, it means the address cannot be reached. You must either correct the address or determine why it is not accessible. If the PING command lists “Reply” messages, then the problem is confined to the Beyond FTP service port. In this case, a firewall may be allowing the PING through, but not the Beyond FTP calls. You must check for the presence of a firewall and follow the instructions in the previous section.
If the connection returns a 10141 error, there is most likely a problem with the encryption keys on either side of the connection. In this case, set the encryption level to None and try the connection again. If it works, you must correct the keys. See the next topic.
If the connection returns a 10142 error, it means the server name is incorrect. Edit the entry and use the Get Server Name button. If the connection results in a 20100 error, it means that there is an issue with the encryption service. Set the encryption level on both sides to None and try the connection again.
If you can connect to the remote server, but you cannot see any drives or directories, the issue is Beyond FTP security. Either the user id and password in the address book are not correct, or the Beyond FTP security configuration at the remote machine is not correct. Be sure to verify the password field by reentering it, and check that the account does not lock the user out of all remote resources. If you make security changes, be sure to implement the changes before attempting to access the machine.