New features of ftpAxe 2.2

       
    2. Major differences from the ftpAxe 2.1
    3. Major differences nfsAxe 2.1 from ftpAxe 2.0
    4. Undocumented features
    5. Known problems

2. Major differences from ftpAxe 2.1

2.1. The following enhancements have been made:

  2.1.1. Installation:
    - implemented the "-auto2" option for "setup.exe".
      This is the same as "-auto" option with the only difference:
      the Finish dialog message is suppressed.

  2.1.2. Comsetup:
    - implemented the "Enable TCP/IP KeppAlive mode" setting;
    - implemented the "Enable Logotype" setting;


2.2. The following bugs have been fixed:

  2.2.1. FTP:
   - Endless printing into the status area if an incorrect host name entered;
   - Incorrect listing when a link name will match to a user or group name;
   - Incorrect listing when a file name consists of spaces.


3. Major differences ftpAxe 2.1 from ftpAxe 2.0

3.1. The following enhancements have been made:

  3.1.1. FTP:
    - more settings are saved;
    - implemented a new format of a directory listing for the NETWARE FTP daemon;
    - implemented a new format of a directory listing for the Hummingbird FTP daemon.

  3.1.2. Telnet:
    - a review of runaway lines (as "old screens") was improved.


3.2. The following bugs have been fixed:

  3.2.1. FTP:
    - more settings are saved;

  3.2.2. Telnet
    - fixed incorrect selecting of the full Telnet screen region;
    - fixed incorrect receiving of some national characters;
    - fixed some bugs in the "View of previous screens" mode.

4. Undocumented Features


  4.1. Comsetup:
    - implemented the "Auto-start XwpPeg Package Watcher" setting
      to provide the corresponding control of the XwpPeg facility;

  4.2. Ftp:
    - FTP connections (in the "non-Passive", default, mode) can be made through
      an existing SSH connection with prepared Forwarded ports.
      This way does not require especial Telnet/SSH facility and can be used
      with any SSH-client which provides traditional Forwarding.
      All settings are made manually.
      Let's assume that you need to access the remote host
      (say, 192.168.136.41) via FTP, and SSH connection is made with the SSH daemon
      which is on another remote host (say, 192.168.136.34), and each host
      is directly accessible one from another (192.168.136.41 <-> 192.168.136.34).
      Also, you should know two free ports on local machine (say, 21 and 4444) and
      one on the remote host connected via SSH (say, 5555 on 192.168.136.34).
      At first, two forwardings must be made via SSH-Client facility.
      Local-to-Remote: "21->192.168.136.41/21" (that in natural for FTP)
      and Remote-to-Local Forwarding: "4444<-5555".
      After that you must add two lines to the "[FTP]" section in the "xwp.ini" file:
      "IP_SSH_FWD=192.168.136.34" and "PORT_SSH_FWD=5555,4444" (i.e., specify
      the remote and local ports).
      Now the FTP can be started. The "host" field must contain "localhost"
      or "127.0.0.1". The "non-Passive" mode must be set up (i.e.
      the "Passive Transfer" check box must be unchecked).
      After "Connect" the FTP will be connected to "192.168.136.4



5. Known problems

  5.1. Uninstallation:
    - the uninstallation procedure does not remove components
      which were installed in additional (non-first) installation
      sessions. Such additional components should be removed manually.

  5.2. Lpd:
    - printers on the remote MS Windows NT 4 hosts
      are unavailable from the local host under MS Windows NT 4 .


------------
PLEASE NOTE:
------------
The programs associated in this package may send and/or receive broadcast IP
requests. Since such packets cannot cross the nearest firewall/gateway/router,
please be sure that these IP requests are invisible from outside your network.
We assume that such behavior cannot be considered as "Hacking"
or "Trojan horse's action".