Known issues and limitations in File Transfer Direct 1.5 Server  (FTDirect)

This article lists all of the important known issues for this release, and is frequently updated as new issues are found. To subscribe to this article and be proactively notified by email when it is updated, use the "subscribe" option to the right.

The following issues have been found since this version was initially released.

1. Documentation correction:  The Firewall Port Settings on p12 of the File Transfer Direct User's Guide contains a table of ports which must be opened on the firewall.  Port 88 (for using Single Sign On) was missing from this table.  Please see the corrected table in article 5369 (link to the right).

The following issues were known at the time of release of this version.
This information is taken directly from the release notes.

• File Transfer Direct supports only US-ASCII characters for Windows single sign-on user names (sAMAccountName), for Super-Administrator passwords, and for policy-related subject annotations.

• The Administrator needs to use a different email address (identifier) for their Administrator account than is used for their end-user account (as defined locally or in Active Directory).

• Be sure to define one or more valid DNS servers in the Administrator Web Interface, or several other Administrator web pages may be unresponsive.

• If you have more than one NTP server that is not reachable, the configured notification is presented for only one of the servers.

• File Transfer Direct policy-related File Type imports do not work with File Types that contain parentheses, such as “Adobe Acrobat(PDF)”. Enter these File Types directly via the Administrator Web Interface instead.

• File Transfer Direct policies Default Offensive Words, GLBA, HIPAA 1 and HIPAA 2 cannot be duplicated by clicking the Duplicate button in the Administrator Web Interface.

• File Transfer Direct policy-related Notification email messages sent from the Admin User do not work properly - source the Notification email messages from another user instead.

• A Unix/tar archive containing unresolved symbolic links causes Policy Engine to prematurely stop recursive decomposition. This may result in file types not being identified or text not being scanned for files contained in the archive. This in turn can result in a text scanning policy or attach-ment filtering policy to miss these files.

If your users exchange tar archives created on Unix/Linux servers, you can create a policy to quarantine messages with attachments of file type “Unix compress/tar” and release them for download after administrator review.

• When you restore File Transfer Direct to a previously saved backup, a new external storage device is automatically added and marked for backups. The name of the new device is the same as the old backup device with a “-<n>” suffix (where <n> is a number to make the device name unique). If you are accessing the backup device using NFSv4 or using unauthenti-cated CIFS protocol, you can delete the old backup device which is no longer in use.

But if you are accessing the backup device using authenticated CIFS protocol, deleting the old unused backup device deletes credentials for the backup device. See the Global Support KnowledgeBase for information about how to handle this situation.

• If you are using an external device for package storage, under load you might receive External Package Storage Connection Failure alerts although the Administrator Web Interface shows that the device is online. This can happen if the device is slow to respond to connection requests. By default, this alert is sent within a minute of the connection failure, but you can configure how often you get these alerts. To change email alert frequency, go to the Monitor – Alert Notifications page and set the frequency for External Package Storage Connection Failure appropri-ately. This will ensure that even if the connection failure is detected more often, an alert will only be generated with the configured frequency. Backup, restore, and external storage functionality are not affected by this behavior.

• After your File Transfer Direct server has been rebooted, in rare cases it might appear to be unlicensed. Reboot your File Transfer Direct server again to resolve this issue.