GlobalSCAPE Knowledge Base

Disabling the COMB Command

GlobalSCAPE 5 — Fri, 12 Mar 2010 05:27:29 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server version 5.1.1 and later
DISCUSSION
	In EFT Server 5.1.1 and later, you can create/edit a registry location to disable the COMB command to avoid problems with multipart uploads causing multiple file upload events. Restricting transfers to one-part uploads will result in slower transfers, but greatly reduces headaches when you want to process uploaded files, because a file upload success is the entire file. This option is disabled by default (legacy behavior), but setting this DWORD registry value to a non-zero integer causes COMB to be disallowed and not shown in the response to FEAT. On 32-bit systems: [HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 3.0\] On 64-bit systems: [HKEY_LOCAL_MACHINE\Software\Wow6432Node\GlobalSCAPE Inc.\EFT Server 3.0\] "DisableCOMBCommand"=dword:00000001

Redirect Custom Command Output to Connected FTP Clients

GlobalSCAPE 5 — Fri, 12 Mar 2010 05:26:25 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server version 5.1.1 and later
DISCUSSION
	In EFT Server version 5.1.1 and later, you can create/edit a registry location to cause the output of an Event Rule-executed custom command (when "redirect output to client" is on) to be sent back over the FTP command channel. This option is disabled by default (which is legacy behavior), but setting this DWORD registry value to a non-zero integer will result in this behavior. The Event Rule must be executed SYNCHRONOUSLY for the output to be redirected to the client, so you should ensure at least one IF FAILED Action is defined to force synchronous operation. On 32-bit systems: [HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 3.0\] On 64-bit systems: [HKEY_LOCAL_MACHINE\Software\Wow6432Node\GlobalSCAPE Inc.\EFT Server 3.0\] "FileUploadEventResult"=dword:00000001

Folder Monitor Change Filter Override

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:27:04 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server version 5.1.1 and later
DISCUSSION
	In EFT Server version 5.1.1 and later, you can create/edit a registry key to set the "dwFilter" parameter that is passed into the function "ReadDirectoryChangesW()", which is the core of the Folder Monitor feature. On 32-bit systems: [HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 4.0\EventRules] On 64-bit systems: [HKEY_LOCAL_MACHINE\Software\Wow6432Node\GlobalSCAPE Inc.\EFT Server 4.0\EventRules] "FolderMonitorFilterValue"=dword:0000007D The default value is the same legacy value that had been present since the initial delivery of the feature: FILE_NOTIFY_CHANGE_FILE_NAME \| FILE_NOTIFY_CHANGE_ATTRIBUTES \| FILE_NOTIFY_CHANGE_SIZE \| FILE_NOTIFY_CHANGE_CREATION \| FILE_NOTIFY_CHANGE_LAST_WRITE \| FILE_NOTIFY_CHANGE_LAST_ACCESS (This is a value of 0x7D) This is useful to override to "quiet" the folder monitor event dispatching; for example, if only looking for NEW files added to the folder, then exclude the "FILE_NOTIFY_CHANGE_FILE_NAME \| FILE_NOTIFY_CHANGE_ATTRIBUTES \| FILE_NOTIFY_CHANGE_LAST_ACCESS" set.

Legacy SMTP Send Behavior

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:25:59 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server version 5.x and later
DISCUSSION
	This key is used for communicating with legacy SMTP servers that do not support RFC 1652 or if having trouble sending messages through your existing SMTP server. On 32-bit systems: [HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 4.0\] On 64-bit systems: [HKEY_LOCAL_MACHINE\Software\Wow6432Node\GlobalSCAPE Inc.\EFT Server 4.0\] "LegacySMTPSendBehavior"=dword:00000001 (DWORD; non-zero to enable the feature)

Using the Server's time zone for file/folder listings in the HTTP/S engine

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:24:43 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server version 5.x and later
DISCUSSION
	In EFT Server version 5 and later, you can create/edit this registry key to alter the behavior of the HTTP/S engine's directory listing format. By default, files and folders are displayed using UTC; however, if this registry value is present and non-zero, we use the Server's time zone for file/folder listings in the HTTP/S engine. On 32-bit systems: [HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 4.0\] On 64-bit systems: [HKEY_LOCAL_MACHINE\Software\Wow6432Node\GlobalSCAPE Inc.\EFT Server 4.0\] "UseServerTimeZone"=dword:00000001 0 = use UTC file times any integer other than 0 = use Server time zone for file times

Reverse Banned File Logic

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:23:28 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server version 5 and later
DISCUSSION
	On a Site's Advanced tab (in version 5) or Security tab (in version 6 and later), you can block the upload or download of certain file types. The key below reverses that "banned file logic" from the current "By default allow all files except those below" to "By default exclude all files except those below:” That is, a REVERSAL of the current logic, The reversed logic filters out ALL by default, and only allows in those that the administrator specifies. (For example, if you want to allow only .txt files.) To activate this feature, create the following key: On 32-bit systems: [HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 3.0\] On 64-bit systems: [HKEY_LOCAL_MACHINE\Software\Wow6432Node\GlobalSCAPE Inc.\EFT Server 3.0\] "RestrictionByFileNameOnUpload"=dword:00000001 (DWORD; non-zero means reverse the logic for banned files [exclude all except those listed])

Web Transfer Client Session Timeout

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:22:24 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server version 5 and later
DISCUSSION
	By default, if the Web Transfer client (WTC) sits idle for 5 minutes, the session is released so that others can use one of the concurrent licenses. You may want the session time to be longer or shorter, depending upon your user's expected usage. You can control this with a Windows registry setting by creating a new DWORD value that indicates the number of minutes that you want the WTC session to be active, but idle, before the session is released. On 32-bit systems: [HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 3.0\] On 64-bit systems: [HKEY_LOCAL_MACHINE\Software\Wow6432Node\GlobalSCAPE Inc.\EFT Server 3.0\] "WTCTimeout"=dword:00000005 Set the DWORD value to the number of minutes that a WTC session can remain idle before it is released for use by others. The default value is 5 minutes.

Enable Alternative Permission Logic

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:21:18 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server version 4 and later
DISCUSSION
	This registry key determines whether EFT Server checks for the "Delete" permission when a client uploads a file. If this setting is not present and/or set to zero, when a connecting client uploads a file, EFT Server checks only for Upload permission. If a file already exists with the same name, it will be overwritten. If this registry setting is present and non-zero, then EFT Server determines if an upload will delete (overwrite) an existing file. If a file already exists, EFT Server does an additional check for Delete permission. On 32-bit systems: [HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 4.0\Config\] On 64-bit systems: [HKEY_LOCAL_MACHINE\Software\Wow6432Node\GlobalSCAPE Inc.\EFT Server 4.0\Config\] "UplReqDel"=dword:00000001 (DWORD: if non-zero value, EFT Server checks if client has Delete permission.)

Changing the Number of Concurrent Threads Used by Event Rules

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:20:13 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server version 4.x and later
DISCUSSION
	The "Folder Monitor" Event Rule process is limited to 3 concurrent threads by default. This means that if you have 5 Folder Monitor Event Rules monitoring the same folder, and a file is added to the monitored folder, only 3 of the 5 Rules will fire, as determined by the operating system. The 4th and then 5th Rule execute only when one or more of the first three threads are done firing and executing any actions. If you have, for example, 100 concurrent Monitor Folder Event Rules, they will not all be triggered simultaneously. To override the default, create the following key: On 32-bit systems: [HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 4.0\EventRules\] On 64-bit systems: [HKEY_LOCAL_MACHINE\Software\Wow6432Node\GlobalSCAPE Inc.\EFT Server 4.0\EventRules\] "FolderMonitorWorkerThreadCount"=dword:00000010 (DWORD: the number of allowed concurrent threads) As of version 6.1, the Folder Monitor Action threads use a dynamically growing pool. The system will keep track of the number of active threads over time and periodically calculate the average of number of concurrent active threads over that time period. The sample rate is once every 5 seconds, and the sample period is 10 samples. After sampling 10 times and finding the average concurrent active threads over that period, the system determines if the past average is 85% of the current active thread count or higher and, if YES, then grows that pool by 1/2 of the concurrent active threads, up to a set maximum number of threads. Basically, this means that if we are currently running close to or above the prior average of concurrent threads, we should grow our thread pool to allow for room for any more events that are coming in to be processed. By default, we start with 3 threads in the pool per site, and can grow to a maximum of 32 threads. With this new architecture, the above Registry Entry will override the initial worker thread count as it has since EFT 4.2.x. If the value is bigger than the default 32 maximum thread pool size, the registry value will also become the new maximum pool size. Thus, if the registry value is greater than 32 then we will have a static pool of threads of that designated size (because the initial and maximum values are both the same).

Does the Copy/Move Event Rule Action support resumed transfers?

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:18:33 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server (All Versions)
QUESTION
	Does the Copy/Move Event Rule Action support resumed transfers?

ANSWER
	Yes. The first attempt overwrites the file. All subsequent retries (in the same rule context) use resume logic. This logic applies to all protocols (SFTP, FTP/S, HTTP/S). Refer to Copy/Move (Push) File to Host Action for more information.

Secure FTP Server Version History

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:17:46 GMT

Secure FTP Server Version History

Changes in 3.3.10

Fixed SFTP protocol command validation
Eliminated Memory leak in authentication manager.
Eliminated crash in SFTP.

Changes in 3.3.7

Updated SSH libraries.
Improved audit logger database connectivity.

Changes in 3.3.5

Improved compatibility with Filezilla FTP client.
Improved compatibility with z/OS systems.
Improved resource usage when uploading via HTTP.

Changes in 3.3.1

Corrected problem with inheritance and resulting folder permissions

Changes in 3.3.0

MD5 functions not thread safe causes crash - Repaired
Auto-lockout now resets on successful login (SFTP)
Corrected COM Memory leak when creating users
MLST now works according to specifications
COM method SetMaxSpace inputs correct amount
Corrected error where E-mail notifications fail in certain scenarios
Corrected error when restoring key from backup location
Show in list unchecked no longer allows viewing of directory
HTTPS component correctly handles large file transfers
MLSD correctly returns Virtual folders
COM method RemoveUser error corrected MX Error: 65280 (0000FF00)”
COM method RenameUser error corrected
HTML directory listing links now properly encode for special characters
Service crash error corrected faulting module to be ntdll.dll
Error returned incorrect SSH dates corrected
Correct file information now sent with SSH_FXP_STAT returns
403 and 404 errors corrected when there is no list permission (blind) in HTTP/S
Force auth dbase refresh now works
Folder listings for 1000+ virtual folders now works
New Active Directory user accounts can now log in after service restart
MLST and MSLD no longer return incorrect negative file sizes on files greater than 2GB
Accounts are no longer incorrectly disabled when using AD and “disable account after X” is not engaged
Upload button no longer displays in browser even though no upload permissions are available for that user

Changes in 3.2.0 Build 07.07.2006.6

Optimized internal SMTP client to conform to RFC 2821
Optimized HTML listing to support RFC 1738 guidelines for special characters (sec. 2.2)
Corrected problem with log file showing negative numbers for file sizes over 2GB
Corrected problem with MLSD not returning Virtual Folders as part of the list
Corrected problem with max transfer speeds preventing users with slower connections from uploading
Corrected problem with disk quota limit affecting HTTPS transfers
Corrected problem with SFTP logins for new users using AD Authentication
Improved error reporting for custom command action triggering

Changes in 3.1.5 Build 04.12.2006.2

Corrected error when SFTP clients connect to NT/AD Site using password only authentication
Corrected issue where execution of a custom command with a lengthy parameter line passed to it causes server to crash.
Corrected error in which settings for require client certificates feature for SSL protocols affected all sites, not only the one on which it was turned on.
Enhanced On User Account Disable Event Rule to trigger when expiration of user account occurs (based upon site refresh interval)
Enhanced SFTP server-side logging such that uploads of 0 Byte files are now written to the log file.

Changes in 3.1.4 Build 01.10.2006

Added SFTP upload/download speed and count reporting to administration GUI
Corrected issue with public key authentication in SFTP
Corrected issue with timeout not disconnecting in SFTP
Corrected issue when creating a site using NTLM authentication with custom domain and group
Corrected issue with home folder permissions resetting at user's first login
Corrected issue with impersonation while downloading in HTTP/S
Improved SetMaxSpace and GetMaxSpace COM methods to use units of KB to allow greater maximum values
Corrected issue connecting with OpenSSH 3.5 without Show and List permissions on parent folder
Corrected issue where execution of a custom command with a lengthy parameter line passed to it causes server to crash.

Changes in 3.1.3 Build 10.10.2005

Improved stability of service caused by unsynchronized access to the SFTP socket state
Corrected HTML form-based uploads to work properly through a URL containing escape codes
Corrected issue to allow Windows user impersonation
Corrected event rule processing when transferring files in PASV mode and containing a command

Changes in 3.1.1 Build 08.08.2005.2

Fixed service issue related to Windows 2003
Corrected branding issue in HTTP/S module
Improved service stability

Changes in 3.1 Build 7.06.2005.3

Added module for support of HTTP and HTTPS transfers
Improved registration process
Known Issues:
1. Upgrades with a fully registered (not trial) SFTP module may see the SFTP module disabled after upgrading to 3.1. If this happens, re-enter the SFTP serial to re-activate that component.
2. Those with trial versions of HTTP will need to restart the server service for the HTTP trial to apply.

Changes in 3.0.4 Build 6.15.2005

Corrected SSH response to MSG_CHANNEL_REQUEST that had flip-flopped the sender and receiver channels. Now properly supports multiple channeled during SFTP session.
Corrected error in SetPermission() and GetPermission() from the COM Admin module introduced when adding richer error reporting.

Changes in 3.0.3 Build 4.29.2005

Fixed security vulnerabity due to buffer overflow in FTP command channel
Improved COM interface error reporting by implementing ISupportErrorInfo interface
Improved registration wizard to display options upon failed registration

Changes in 3.0.2 Build 4.12.2005

Corrected file locking problem that caused some files to not appear after uploads (only when a user home folder was specified to be the root folder)

Changes in 3.0.1 Build 3.31.2005

Corrected memory leaks
Corrected problem with quota limits for SFTP uploads

Changes in 3.0.0 Build 3.23.2005

Added MODE Z support with ZLIB compression engine
Added support to limit the number of total concurrent user logins
Added support to lock partially uploaded files (clients cannot download files in the process of being uploaded)
Added support for importing and exporting site configuration data, user settings, site custom commands, and site event rules
Added support for capturing and displaying connection-activity in real-time
Improved logging information and provided option for "Standard" and "Verbose" logging
Added registration wizard
Enhanced logging mechanisms
Corrected ability to disable SMTP authorization option
Corrected issue where Event Rules does not release handles correctly when user redirects output -OR- terminates the process after a certain amount of time
Corrected issue to properly re-establish lost connections with SQL database using ODBC Authentication
Enhanced message prompt on Kick User functionality
Corrected issue with SMTP authorization being disabled
Corrected issue to log failed login attempts
Corrected issue that could crash the Administrator GUI when the admin password is NOT remembered
Corrected issue in receiving BitVise's Tunnelier client SSH/SFTP commands
Corrected issue with multi-part uploads not always working
Corrected issue so IIS logging records partial transfers

Changes in 2.0.7 Build 12.20.2004

Corrected issue with AD Authentication failing to pull GROUP information
Corrected issue with RNFR and RNTO not returning proper codes
Corrected issue with COM ICISites section functionality
Corrected issue with CreatePhysicalFolder failing unless UNIX style path provided
Corrected issue with trial registration on the Windows 2003 Operating System

Changes in 2.0.6 Build 11.03.2004.2

Corrected AD Authentication import of large numbers of users
Corrected incorrect 'modified' date on files
Corrected issue with ODBC Group Management
Corrected issue with SFTP event rules using Email/Custom Command parameters
Corrected issue with STOU command not returning unique filenames
Corrected issue with deployment of default MS Access db

Changes in 2.0.5 Build 9.08.2004

Corrected inappropriate SFTP Banner Message ("unexpected packet #53") on server initiated key re-exchange
Made various SFTP Event Rule improvements
Event rule parameters now honoring quotes so that embedded spaces are not considered parameter delimiters
Administration COM DLL bug fixes (CreateUser, Permissions)
Registration now allows multibyte (MBCS) characters
Error message / prompt / indication string changes for clarification
Corrected issue with disappearing users from ftpserver_ids table
Corrected bug where client password only connections were allowed even though the server required password and certificates for authentication

Changes in 2.0.3 Build 5.16.2004

Corrected condition where SFTP sometimes returned incorrect file permissions
Corrected auto-assign home folder logic when NT Auth was used
Corrected condition where SFTP would always listen on 0.0.0.0:22 regardless of IP settings
Corrected remote administration problem where selecting SFTP tab would lock the admin GUI from selecting any other tab
Corrected a defect introduced in 2.0.2 where SFTP public key authentication failed to occur
Corrected condition where user level settings for protocol restrictions were ignored in favor of site-level restrictions
Corrected default behavior to include Modified Time as part of MLSD/MLST options
Corrected a formatting issue with regard to time values returned as a result of an MLSD command sequence
Corrected security vulnerability where SSH service credentials were being used instead of the connecting user's NTFS permissions when using NT/AD Authentication and SFTP
Corrected condition where server was returning both virtual and physical folder names in the raw listing (for virtual folders)

Changes in 2.0.2 Build 4.15.2004

SFTP commands are logged to log file
Improved SFTP response codes to conform to RFC standard and expectations of clients
SFTP can now run independently of FTP/FTPS
Proper handling of NTLM/AD usernames when connecting over SFTP
Improved Trial Registration mechanisms
Improved SMTP communication to avoid false positives in SPAM checkers
Proper handling of home folder creation upon first login

Changes in 2.0.1 Build 3.16.2004

Corrected two security vulnerabilities (DoS and Buffer Overflow on SITE commands)
Corrected condition where GUI would crash if connecting while on the VFS tab
Corrected issue wherein virtual folders would appear in duplicate places in VFS

Changes in 2.0 3/11/2004

Added Event Rules
Added support for SFTP (SSH2)
Added programmatic interface support with COM
Added support for database polling
Added option to edit path to authentication provider (database)
Added support for 1024,2048, and 4096 bit SSL key lengths
Added feature which makes an expired certificate immediately recognizable in the certificate manager
Added support for TLS 1.0 (SSL v3.1)
Added support for Clear Command Channel (CCC) when using SSL
Added support for server to server transfers using SSCN
Added support for multiple servers to be managed through the Administrator Interface
Added feature to specify a future date to expire user accounts
Added support for Active Directory
Added support to query domain controller
Added feature for the input of personal account information
Added option to use home folder when creating a Site that will use NT or Active Directory Authentication

Changes in 1.2.3 10/17/2003

Added support for the MDTM command
Added ability to use a forward slash on NT Authentication logins
Corrected problem to properly handle Close_Notify sent by SSL client
Corrected problem in handling of heavy loads under SSL that caused VFS to "forget" root path (especially on multi-processor machines)
Corrected problem where server would sometimes close socket prematurely when a client requested a directory listing
Corrected timestamp logic for file dates without explicit times being listed. This improves synchronization logic

Changes in 1.2.1 7/9/2003

Corrected problem where SSL download speeds were substantially slower than SSL upload speeds
Corrected a problem where there was an inconsistency between the change password dialog and the New User Wizard

Changes in 1.2 3/4/2003

Corrected a problem where downloads using SSL would sometimes transfer an incomplete file
Corrected a problem where the server was not sending the correct IP address in response to a PORT mode request when the server has multiple IP addresses and the virtual site is listening on any but the first of those addresses
Added support for files sizes greater than 2 GB
Corrected issue so that IIS log file format now correctly lists time per operation

Can EFT Server pull user accounts from multiple child domains and/or forests?

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:15:23 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server version 6.1
QUESTION
	Can EFT Server pull user accounts from multiple child domains and/or forests?

ANSWER
	EFT Server allows you to specify only one domain and one group. However, that group can contain groups and users from foreign domains, as long as a trust relationship exists between the domains. This allows users from remote domains to authenticate to EFT Server. So, as long as a trust relationship exists between the domains, EFT Server can authenticate users from remote domains. The domain in which EFT Server resides will need to have a group that contains the foreign domain users. The point is that EFT Server simply talks to one AD/forest/controller. If that AD/forest/controller is properly configured to get information from the other domain/forest, then EFT Server will authenticate those users. NOTE: When your forest contains domain trees with many child domains and you observe noticeable user authentication delays between the child domains, you can optimize the user authentication process between the child domains by creating shortcut trusts to mid-level domains in the domain tree hierarchy. For more information, refer to When to create a shortcut trust on Microsoft's Web site. For details of controlling access to shared resources across domains, refer to the Microsoft TechNet article, Accessing resources across domains.

Can EFT Server/Secure FTP Server pull Active Directory users from multiple domains?

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:14:58 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server Secure FTP Server
QUESTION
	Can EFT Server/Secure FTP Server pull Active Directory users from multiple domains by specifying only the domain in which the Server resides?
ANSWER
	When you configure Sites in EFT Server, you specify which type of database to use for user authentication. If you choose Windows Active Directory (NTLM/AD) Authentication, you point EFT Server to a Primary Domain Controller (PDC) and a group on that AD controller. EFT Server queries the domain controller, adds all domain users to the Site tree, and assigns permissions to users from the user database. Any user that exists in the group on the AD controller can be valid users in EFT Server. If the AD administrator can define users in the group that come from other domains, then those users should also be available to EFT Server. EFT Server supports the listing of user accounts and login authentication for accounts that reside in remote AD domain groups referenced by an AD universal group. EFT Server only supports accounts that reside in groups that are from the same domain as the universal group. EFT Server supports traversal of the remote groups referenced by a universal group. The recursive traversal of groups and subgroups that exist in EFT Server are supported and unaffected by the ability to support users in remote groups that are referenced by a local universal group.
	Terminology:
	One or more domains that share a common schema and Global Catalog are referred to as a forest. In a forest, users in one domain tree can gain access to resources in the other trees, the Global Catalog incorporates object information for the entire forest, and the Active Directory schema applies to the entire forest. domain local group: a security or distribution group that can contain universal groups, global groups, other domain local groups from its own domain, and accounts from any domain in the forest. global group: a group that can be used in its own domain, in member servers and workstations of the domain, and in trusting domains. universal group: a security or distribution group that contains users, groups, and computers from any domain in its forest as members. Refer to KB10542 for more information.

What is the difference between SSH protocol version vs. SFTP protocol version vs. SSH implementation version?

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:14:31 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server (All Versions)
QUESTION
	What is the difference between SSH protocol version vs. SFTP protocol version vs. SSH implementation version?

ANSWER
	It is important to distinguish the Secure Shell (SSH) protocol version from the SSH File Transfer Protocol (SFTP) version, and each of these from the more granular SSH library implementation version. Secure Shell (SSH) Protocol The SSH protocol has a variety of versions which are grouped into the following two categories: SSH 1.xx (SSH1) - Vulnerable and increasingly rare. Generally considered obsolete. SSH 2.00 (SSH2) - RFC standard, by now most widely used. (See RFC 4251) EFT Server supports SSH2 only. We do not support SSH1. (As of this writing, SSH3 does not yet exist.) SSH File Transfer Protocol (SFTP) The SFTP version affects functional features; it does not affect security of the connection (which is always SSH2.) Below is a list of SFTP versions and their use: 1 (nonexistent) 2 (rare) 3 (common) 4 (common) 5 (nonexistent) 6 (not yet common but increasingly supported) EFT Server supports SFTP versions 2, 3, 4, and 6. The outbound client defaults to version 4, and it is not configurable through the GUI. The EFT Server outbound client negotiates the SFTP version with the receiving server during session establishment. That is, if the receiving server only supports version 2, EFT Server will negotiate down and operate at version 2. SSH Implementation Version (sshlib) Our sshlib has implementation versions such as 1.81, 1.82, but these refer to the library version, not the protocol version. The SSH protocol version is always 2.0. For more information, refer to the following web pages: Secure Shell (SSH) Protocol: http://en.wikipedia.org/wiki/Secure_Shell SSH File Transfer Protocol (SFTP): http://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol The Secure Shell (SSH) Transport Layer Protocol, RFC 4253: http://tools.ietf.org/html/rfc4253

Scripts fail on EFT Server when installed on the 64-bit Windows 2008 operating system.

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:13:21 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server version 6.x
QUESTION
	Scripts fail on EFT Server when installed on a 64-bit operating system.

ANSWER
	When you run a script for EFT Server on a 64-bit operating system, you cannot call cscript.exe. Instead you must use C:\Windows\SysWOW64\cscript script.vbs.

Is EFT Server's AS2 module Drummond certified?

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:12:56 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server (versions 5.2.3 and later)
QUESTION
	Is EFT Server's AS2 module Drummond certified?

ANSWER
	Yes. The AS2 component used in EFT Server is /n software's IP*Works EDI v8.3 Engine, in compliance with RFC4130. (The Drummond Group requires you to register your email address on their web site linked above to see their Current Certified Product List.) In March 2008, GlobalSCAPE announced that EFT Server supports both client (outbound) and server (inbound) AS2 transfers with a Drummond-certified AS2 adapter that has achieved interoperability with other Drummond-certified AS2 servers and clients. The full product was released in July 2008 with EFT Server version 5.2.3. For more information, refer to How EFT Server Supports AS2 in the EFT Server online help documentation.

Forgetting the Admin Password

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:12:36 GMT


THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server Secure FTP Server
QUESTION
	I forgot my administrator password. How can I create a new password?
ANSWER
	If you cannot remember your password to log in, you can log in with the local administrator account for the computer on which EFT Server/Secure FTP Server is installed. Logging in to the Server with the local administrator account allows you to keep your configuration intact and reset an administrator account password, create a new administrator account, and remove inactive administrator accounts. When the Server service receives a login message, it first examines internal user accounts for a matching username/password pair. If the login attempt is made locally on the Server computer and the login attempt fails to find a matching login, the Server then attempts to validate whether the supplied login corresponds to valid user account credentials with administrative privileges to the local computer on which the Server is running. If the supplied credentials match a valid administrator account for the local computer on which the Server is running, then the Server allows the login attempt, but only the Server node and the Administration tab appear. None of the sub nodes in the tree (Sites, Templates, Users, etc.) are available. On the Administration tab, you can create a new Server administrator account, change the password on an existing account, unlock the account, or reset an expired account.
Note: In the unlikely and unsecure chance that the local administrator account does not have a username or password, create a new local administrator account in Windows or edit the existing local administrator account to provide the account with a password, and ensure that the account has local administrator privileges. (On the Windows Control Panel, click User Accounts.) If you cannot create or edit user accounts, you do not have local administrator privileges on the computer and will need to contact your network administrator for assistance. In many cases, you will need to type the domain and the username. For example, if you log in to Windows using soiljmh on the domain of mycompany to log in to the Server, you might need to type mycompany\soiljmh for the username.

How can I purge EFT Server data from my SQL database?

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:12:08 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT Server (All Versions)

QUESTION

How can I purge EFT Server data from my SQL database?

ANSWER

Use the procedure below to purge EFT Server data from your SQL database.

Download the SQL script PurgeEftData.txt. Do one of the following
- Click the link to open it your browser, then copy and paste the text into a txt file.
- Right-click the link, then save the .txt file to your desktop.
Open the script in a text editor and edit the following values:
1. If the database name is not EFTDB, modify the following line with the name of the database:
  USE EFTDB.
2. In the "DeleteTo" variable:
```
SELECT @DeleteTo = '1/1/2007', @DeleteScope = '1000' 
```
  - All records BEFORE the DeleteTo date are affected. Edit the date and time to some time in the future if you want all rows to be affected.
3. In the "DeleteScope" variable:
```
SELECT @DeleteTo = '1/1/2007', @DeleteScope = '1000'  
```
  - "DeleteScope is the number of rows to be deleted and how quickly they are deleted. This can be a static value or a percentage. If the database is active, you should delete the records in smaller chunks, perhaps 1000 at a time, so that you do not affect the responsiveness of the SQL server for new/ongoing transactions. If you run script after hours or on a test system, you can delete all of the records in larger chunks.
    
    Examples are commented in the top of the script and shown below.
  --SELECT @DeleteTo = '1/1/2006', @DeleteScope = '50%'
  --SELECT @DeleteTo = '1/1/2007', @DeleteScope = '1000'
  --SELECT @DeleteTo = '1/1/2007', @DeleteScope = '2000000000'
Save the script as PurgeEftData.sql.
After you have edited the script as needed, then you can craft the proper command line for "oSQL" to connect to the database:
1. Open a command prompt. (Click Start > Run. Type cmd, then press ENTER.)
2. Type the following to execute the sql file (without breaks):
  [path to oSQL]\oSQL.exe -S [server address] -U [username] -P [password] -i "[c:\path\to\PurgeEftData.sql]\PurgeEftData.sql"
  For example, type (without line break):
  "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\oSQL.exe" -S 192.168.19.17 -U jbond -P asd123!f$s1 -i "C:\Program Files\GlobalSCAPE\EFT\Reports\PurgeEftData.sql"

Can I automatically ban an IP address that has tried to log in incorrectly multiple times?

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:11:45 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT Server versions 5.x and prior
Secure FTP Server (All Versions)

NOTE: You do not need to follow this procedure if you are using EFT Server versions 6 or later; you can configure autoban settings in the GUI. Refer to:

EFT Server version 6.0: Flooding and Denial of Service Prevention
EFT Server version 6.1: Flooding and Denial of Service Prevention
EFT Server version 6.2: Flooding and Denial of Service Prevention

QUESTION

Is there any way of auto-banning an IP address that has tried to log in incorrectly multiple times?

ANSWER

There are several methods that you can use to temporarily or permanently disallow unauthorized or problem users from accessing the Server. This article describes how to ban the IP address of users attempting to connect with a non-existing login name. (For other methods, refer to the links at the bottom of this article.)

Note: Editing and running .vbs scripts are for advanced users. If you need assistance with editing scripts, contact GlobalSCAPE's Professional Services team for assistance.

**You only need to configure this once; you can schedule Event Rules to run the script automatically at regularly scheduled intervals, as described below.**

To create the command and the script that it will execute:

Download the attached script file, addbanip.vbs (or addbanip.txt and rename it with thhe .vbs extension), and save it in c:\temp.
Copy the following text into a text editor (e.g., Notepad/EditPlus) and save it as batch file in c:\temp. For example, c:\temp\LogInvalidIp.bat.
```
 @echo off  rem Simply append all arguments to the log file  rem "%EVENT.TIME%" "%USER.LOGIN%" "%CONNECTION.REMOTE_IP%" "%EVENT.REASON%" 
 "%CONNECTION.LOCAL_PORT%" "%CONNECTION.PROTOCOL%"  Echo %1 %2 %3 %4 %5 %6 %7 %8 %9 >>InvalidIp.txt 
```
The batch file will create a file named InvalidIp.txt whenever there is a failed connection attempt on the Server.
Add a custom command on the Server. Provide any name and description, and the path to the executable (in this example, c:\temp\LogInvalidIp.bat.) Clear the Output check boxes. Do not enter ANYTHING on the Advanced or Permissions tabs.
Create a User Login Failed Event Rule, and add the Execute command in folder Action. (Refer to Using an Event Rule to Execute a Command for details, if necessary.)
Click in the Action to display the Custom Command dialog box.
1. In the Select command box, click the down arrow and select your new command.
2. Copy and paste the following variables into the Specify command parameters box (be sure to include the percent signs and quotation marks):
  "%EVENT.TIME%" "%USER.LOGIN%" "%CONNECTION.REMOTE_IP%" "%EVENT.REASON%" "%CONNECTION.LOCAL_PORT%" "%CONNECTION.PROTOCOL%"
3. In the Specify command working folder box, type or click the folder icon and browse to the folder where the executable resides (c:\temp). (Note: No error checking is done to verify that you have typed a valid path.)
4. Click OK to save the Command, then click Apply to save the rule.
Open the script file that you downloaded, addbanip.vbs, and edit the variables under Constants for server details to reflect your configuration. (Because this plain-text file will contain your username/password pair, be sure to save the file in a secure location.):
- IP address(cServer)
- Site name (cServerSite)
- Port, (cPort)
- Username (cUserName)
- Password (cPassword)
- Log (cLogFile) file path (For this example, "c:\temp\InvalidIp.txt")
- Temp work (cWorkFile) file path (For this example, "c:\temp\InvalidIp.wrk")
- Your IP address to keep you from locking yourself out (cIgnoreIP)
- E-mail variables to e-mail you when an authorized login occurs (You can comment out the calls to the e-mail subroutines to prevent the e-mails from being sent while testing.)
- And most importantly, set the maximum number of invalid login attempts before an IP is added to the ban list (MaxInvalidLogins). Do not set this too low, because if a legitimate user "fat fingers" the login, they will be banned.

To test it:

Use CuteFTP or another client to attempt to log in to the Server using a non-existant username. Repeat multiple times, until you have exceeded MaxInvalidLogins.
The failed login should cause the file InvalidIp.txt to be created in c:\temp. If it is, continue. If not, troubleshoot the above steps. The contents of InvalidIp.txt should look similar to the following text (including the quotation marks):
```
 "24 Jan 08 15:14:41" "wwwww" "127.0.0.1" "Invalid password" "21" "FTP"    
```
At a command prompt, execute addbanip.vbs.
Click OK through the prompts, carefully noting each one.
When the prompt "Add n.n.n.n to denied IPs - click OK" appears, click OK, and the IP addresses should be added to the deny list. If you do not get that far, then most likely no IP addresses matched the criteria. You can add Print lines all through the code as necessary (e.g. Print "now checking blah blah blah") to help you debug/diagnose the script.
If the script works and the IP is added to the ban list, you are set to go. You can manually run the script when necessary or setup Windows Scheduler to run the script automatically. When the script is run, it will parse InvalidIp.txt for any failed login attempts and if there are multiple failures for the same IP address (more than MaxInvalidLogins), the IP address will be banned.

For more information about blocking/disconnecting problem/unauthorized connections to EFT Server, refer to the following topics in the online help file. (Similar procedures are available for Secure FTP Server.)

Block anti-timeout schemes. Many FTP clients send random commands such as REST 0, PWD, TYPE A, LIST, etc., to the FTP server to keep the session alive while the client is idle. (Set at the Site level)
Configure EFT Server to automatically ban IP addresses that may potentially be associated with a DoS (Denial of Service) attack. The Flooding and Denial of Service Prevention settings can block DoS attacks in which the same IP address unsuccessfully tries repeatedly (numerous times per second) to access the Server.
Use the IP access restrictions list to block specific IP addresses or allow only specific IP addresses.
Temporarily or permanently disable user accounts after a defined number of invalid password attempts over a specified time. (Set at the User or User Setting Level only)
Disconnect users and optionally ban their IP address after a defined number of invalid commands. Many FTP clients send a NOOP command to the Server during idle times to keep the connection alive. If you disallow the NOOP command, it will be considered an invalid command and treated according to your settings under Disconnect after <n> invalid commands. (Set at the User or User Setting Level only)
Automatically disconnect users after a specified time of inactivity, set per user or at the User Setting Level, by setting a maximum idle time limit. Set at the User or User Setting Level only)
Temporarily or permanently disable idle user accounts (i.e., accounts that have not accessed the Server in a defined period of time.
Forcibly log a user off the Server. (Performed at the Server Level)
Disable a User Setting Level or user account or set an expiration date on a user account. Expired/disabled accounts are not removed from the Server; they can be re-enabled at any time.
Disconnect users after a defined number of invalid commands, but only if the username is valid and the password is bad. (If the username does not exist, it cannot be banned.)
Disconnect users after a specified time of inactivity

Error 12002. The operation timed out

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:08:58 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
GlobalSCAPE product activation
SYMPTOM
	Received Error #12002. The operation timed out
EXPLANATION/RESOLUTION
	"Error 12002" is a Microsoft Win32 Internet (WinInet) API error code. WinInet provides stand-alone applications with easy access to standard Internet protocols such as Gopher, FTP, and HTTP. The error indicates that the request timed out. For example, if you receive this error when attempting to activate a GlobalSCAPE product, the error can indicate that communication with the activation server has not been established. This can be caused by a firewall or proxy configuration problem, or a temporary network failure. If you receive this error, try the following: Attempt your connection again. Refer to the CuteFTP documentation for the procedure to adjust your connection configuration, if necessary. Follow the onscreen instructions to perform a manual registration. For fastest resolution, submit the necessary information online at http://www.globalscape.com/register/. If online activation is unsuccessful, submit your activation request directly to our customer service team using the online submission form.

Activation and Registration on Windows Vista

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:08:23 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	All products when running on Windows Vista
ACTIVATION OR REGISTRATION ON WINDOWS VISTA
	All GlobalSCAPE programs must be installed by a user that has administrator account credentials. Additionally, successful activation (registration) for most* programs requires that the program itself be started using administrator account credentials. Follow the steps shown below to activate the program on Windows Vista: Close the program if it is already running. Click Start, click All Programs, click GlobalSCAPE, click on the name of the program (e.g.: CuteFTP Home) and then right-click on the name of the program shortcut. Click Run as administrator. Windows Vista User Account Controls (UAC) will ask for permission to continue. If you are using a Standard User account, then you must provide an administrator account user name and password. Click OK or Continue to start the program. For most programs, click Enter Serial Number and then follow the onscreen instructions. (If you are not prompted for the serial number when the program starts, open the Help menu and click Enter Serial Number or Register your purchased copy. After the program starts for the first time, close and then restart it from the Start menu. To confirm a successful activation, open the Help menu and click About. Your name and serial number should be displayed. * CuteFTP 4.2, CuteFTP 7 and CuteZIP 2 are known exceptions. CuteFTP 4.2: Cannot be activated on Windows Vista and will not run beyond the 30-day trial period. Registered users may be eligible to upgrade to CuteFTP 8 Home or CuteFTP 8 Professional at a reduced price. CuteFTP 7: Separate activation is required for each computer user. Administrator credentials should not be used for activation. For each user, Start CuteFTP 7 normally, click Enter Serial Number and then follow the onscreen instructions. CuteZIP 2: Follow the same steps as for all other programs shown above except that you must first log on to Windows using an Administrator User account.

Cannot connect to Server via CuteFTP (Windows Firewall configuration)

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:08:01 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
All Windows-based products/versions
SYMPTOM
	I installed Windows XP SP2 and now I can't connect to the FTP server.
RESOLUTION
	Windows Firewall blocks unsolicited connections to your computer. This includes blocking the ports required for an FTP client to connect to a remote server. In order to connect to an FTP server, you must configure the Windows Firewall to allow incoming connections through port 21. To configure Windows Firewall In the Control Panel, open the Security Center. Click Windows Firewall. The Windows Firewall dialog box appears. Click the Exceptions tab, then click Add Port. The Add a Port dialog box appears. In the Name box, type FTP. In the Port box, type 21. Leave TCP selected, then click OK. Click OK to close the Windows Firewall dialog box. Click the X in the upper right corner to close the Security Center. Your FTP client must be set to Port mode in order to connect to the server: In CuteFTP Home: Open the Site Manager (press F4) and click once on the name of the problem FTP site. On the Type tab change the Data Connection Type to Use Port. In CuteFTP Professional and CuteFTP Lite: In the Site Manager, right-click on the name of the problem site, then click Properties. On the Type tab change the Data Connection Type to Use Port. More advanced information about configuring Windows Firewall is provided by Microsoft.

Can I use a Windows Command Prompt to send FTP Commands to a server?

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:07:07 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT Server (All Versions)
Secure FTP Server (All Versions)
CuteFTP (All Versions)

QUESTION

Can I use a Windows Command Prompt to send FTP Commands to the Server?

ANSWER

Using CuteFTP, you can communicate with an FTP site on the lowest possible level. You can define an FTP site in the Site Manager, then simply double-click it to connect and log in. Using CuteFTP's Custom Commands dialog box, you can define command sequences for common tasks, and place shortcuts for the commands on the toolbar for reuse. CuteFTP makes FTP simple; however, if you prefer to use a Windows Command Prompt, the procedure and table below will help you with some of the more common FTP tasks.

To use FTP commands at Windows command prompt

Open a command prompt and navigate to the folder containing the files that you want to transfer, then press ENTER. For example, type:

cd "C:\Documents and Settings\marsha\My Documents\CaseStudies" (You need the quotes if you have spaces in your path.)
At the C:\> prompt, type FTP. The C:\> prompt changes to ftp>.
At the ftp> prompt, type open followed by the name of the remote FTP site, then press ENTER. For example, type:

open myftpsite.com

When prompted, type the username and password provided to you by the administrator of the FTP site, then press ENTER.

If you get a 10061 error, it is likely the site is refusing to accept your connection because of security privileges or because it is not an FTP server. For a list of FTP error codes, refer to Knowledge Base article Q10142, FTP Status and Error Codes.

Type cd then the path to the remote server's directory in which you have permission to transfer files via FTP. For example, type:

cd M:\InetPub\EFTRoot\MySite\Usr\jbug

You are now ready to transfer files between your local directory and the remote directory using FTP commands such as put and get.

DOS FTP commands are slightly different than regular FTP commands. The table below lists some of the more common FTP commands as you would enter them at a Windows Command prompt. (Certain DOS commands also work in UNIX, but UNIX directories use a forward slash ( / ); DOS directories use a back slash ( \ ).)

If you want to issue a command that is understood by a remote FTP server, but not by DOS, use the literal command in front of the FTP command. This command allows you to pass any request to the remote server without its being a valid DOS command.

Task	DOS Command	Notes
Change user password on a site	Literal SITE PSWD oldpassword newpassword	"Literal" sends a command line to the remote FTP connection and executes the SITE PSWD command.
Connect to the specified FTP host on the specified port	open [host] [port]	For example, type: open myftpsite.com 21
Navigate to a different directory on remote machine	cd [directory]	For example, type: cd M:\InetPub\EFTRoot\MySite\Usr\jbug
Change to parent directory	cdup	Same as cd ..\
Changes directory on local machine	lcd [path]	For example, type lcd c:\temp.
Displays a list of files and folders in the current remote directory	dir [path] ls [directory] [localfile]	For example, type: dir M:\InetPub\EFTRoot\MySite\Usr\jbug or ls M:\InetPub\EFTRoot\MySite\Usr\jbug C:\temp\contents.txt
Creates a directory on the remote file system	mkdir [name]	For example, to create a folder into which you will upload your graphics files, type: mkdir images
Copies a file from the local to the remote computer	put [filename.ext]	To upload the file with a different name, use put oldfilename.ext newfilename.ext
Copies multiple files from the local to the remote computer	mput [files]	Puts multiple files; . puts all files; .txt puts all .txt files, my_.* puts all files that start with my_ with any extension.
Copies a file from the remote to the local computer	get [filename.ext]	For example, type: get dog.jpg
Copies multiple files from the remote to the local computer	mget [files]	Gets multiple files; . gets all files; .txt gets all .txt files, my_.* gets all files that start with my_ with any extension.
Deletes a file	delete [filename.ext]	For example, type: delete dog.jpg
Renames a file	rename [filename] [filename]	For example, to rename a picture of your dog, Pooh Bear, type: rename dog.jpg PoohBear.jpg
Removes a directory on the remote computer	rmdir [name]	For example, type: rmdir olddogpics
List current working directory	pwd	Use when you forget which directory you are in or if you want to copy the path
Close connection	bye (or quit)	Disconnect from remove FTP server
List of available commands or help for a specific command	help help [command] ? [command]	help by itself lists available FTP commands; help [command] or ? [command] provides help for the specific command
Change transfer mode to ASCII	ascii	Used for HTML and text files
Change transfer mode to binary	binary	Used for graphics, compressed files, audio clips, etc.
Displays current transfer mode (ASCII or binary)	status	Query the status of files, transfers in process, and other system information. The STAT command implemented on some FTP servers could allow a remote attacker to obtain sensitive information; therefore, it is disabled on some servers.
Enable/disable prompts	prompt	Use this command if you do not want to be prompted for each file transfer when transferring multiple files.

Effect of Daylight Saving Time change on GlobalSCAPE Software

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:06:46 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	All Products
QUESTION
	Beginning in 2007, the United States will begin observing Daylight Saving Time (DST) from the second Sunday in March until the first Sunday in November. Most of Canada will also observe the new period. Will there be any effect on GlobalSCAPE software from this change? Are there any other known issues related to the change to or from DST?

ANSWER
	There are no known issues concerning the 2007 DST period change specifically however there are issues that occur whenever there is a switch to or from DST. These issues will occur no matter when the switch occurs. Only EFT Server and CuteFTP 8 are known to be affected. The following are known issues: EFT Server (All versions prior to ver. 4.3.4) PROBLEM: When an on timer event is set, the time is modified forward one hour when DST begins and backward one hour when DST ends. Manually changing the time on the system clock does not have the same effect. RESOLUTION: The recommended solution is to upgrade or update to EFT Server 4.3.4 or greater. Alternatively, manually correct the times for the scheduled items as needed. CuteFTP 8 Professional and CuteFTP 8 Home (Versions 8.0.0 through 8.0.7 only) PROBLEM: When a scheduled item exists in the transfer queue, the time for that item is modified forward one hour when DST begins and backward one hour when DST ends. Manually changing the time on the system clock does not have the same effect. RESOLUTION: The recommended solution is to upgrade or update to CuteFTP 8.1 or greater. Alternatively, manually correct the times for the scheduled items as needed. Please report any other DST related issues directly to the Technical Support Team.

Changing the Root Folder of EFT Server while Retaining Permissions

GlobalSCAPE 5 — Fri, 12 Mar 2010 04:05:53 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:
	EFT Server (All Versions) This topic is for advanced users. If you are unfamiliar with running Windows scripts, seek help from your network administrator or contact GlobalSCAPE support.
DISCUSSION
	Copying or migrating EFT Server configuration might be necessary for several reasons, such as: Moving a Proof of Concept (PoC) in your staging environment without recreating all the settings and configuration data. Creating a standard configuration for installation on multiple computers. Updating EFT Server software with a fresh install rather than patching. The help topic "Copying an EFT Server Configuration to Several Computers" provides steps to take before moving EFT Server to another location. If EFT Server's physical file system has been moved, you need to update EFT Server configuration to point to the new location. In the EFT Server Administrator GUI, you specify the path to the Server's root folder; however, pointing to the new root folder causes EFT Server to lose the permissions assigned to EFT Server’s Virtual File System (VFS). To retain all relevant folder permissions and virtual folders, download and extract the scripts in VFS-MigrationScript.zip and use the scripts to copy the VFS permissions to the new root folder structure. To move the EFT Server root folder Backup the following files in the EFT Server installation directory: FTP.cfg [YourSite].aud All .bak and .update files All certificates/keys/PGPkeys STOP all sites so that user activity (such as folder creation) does not interfere with the migration process. Run the eftVFSExport.vbs script to save permission configuration for the EFT Server Virtual File System (VFS). Copy the current EFT Server Root to the new location. It is important that you copy and NOT move the file system, in case you encounter any errors in the root migration process. Change the EFT Server root folder to the new location: In the Administrator interface, click the Server node, then, click the Auditing tab (in EFT Server v5) or the Logs tab (in EFT Server v6). In the text box, specify the new path, then click Apply. Run the eftVFSImport.vbs script to restore folder permissions. Verify that permissions have been restored and all virtual folders exist. Review and update Event Rules to point to the new path, if necessary. Delete the previous root location, if necessary. Start the sites to resume user activity. Running the scripts The import and export scripts are visual basic scripts designed for use with cscript.exe. They both take a basic set of command line parameters. Usage: eftVFSExport.vbs <arguments> Required Arguments: -s EFT Server -port admin port on EFT Server -u admin username for EFT Server -p admin password -site the Site ID on the server you are manipulating (will be ‘0’ on most single-site servers) -f path of text file to store/read data Example: cscript.exe eftVFSExport.vbs -s localhost -port 1100 -u admin -p secret -site 0 -f output.txt NOTE: Use of CScript over WScript is strongly recommended for these scripts, because the scripts are very verbose.

GlobalSCAPE Knowledge Base

Disabling the COMB Command

Redirect Custom Command Output to Connected FTP Clients

Folder Monitor Change Filter Override

Legacy SMTP Send Behavior

Using the Server's time zone for file/folder listings in the HTTP/S engine

Reverse Banned File Logic

Web Transfer Client Session Timeout

Enable Alternative Permission Logic

Changing the Number of Concurrent Threads Used by Event Rules

Does the Copy/Move Event Rule Action support resumed transfers?

Secure FTP Server Version History

Secure FTP Server Version History

Changes in 3.3.10

Changes in 3.3.7

Changes in 3.3.5

Changes in 3.3.1

Changes in 3.3.0

Changes in 3.2.0 Build 07.07.2006.6

Changes in 3.1.5 Build 04.12.2006.2

Changes in 3.1.4 Build 01.10.2006

Changes in 3.1.3 Build 10.10.2005

Changes in 3.1.1 Build 08.08.2005.2

Changes in 3.1 Build 7.06.2005.3

Changes in 3.0.4 Build 6.15.2005

Changes in 3.0.3 Build 4.29.2005

Changes in 3.0.2 Build 4.12.2005

Changes in 3.0.1 Build 3.31.2005

Changes in 2.0.6 Build 11.03.2004.2

Changes in 2.0.5 Build 9.08.2004

Changes in 2.0.3 Build 5.16.2004

Changes in 2.0.2 Build 4.15.2004

Changes in 2.0.1 Build 3.16.2004

Changes in 2.0 3/11/2004

Changes in 1.2.3 10/17/2003

Changes in 1.2.1 7/9/2003

Changes in 1.2 3/4/2003

Can EFT Server pull user accounts from multiple child domains and/or forests?

Can EFT Server/Secure FTP Server pull Active Directory users from multiple domains?

What is the difference between SSH protocol version vs. SFTP protocol version vs. SSH implementation version?

Secure Shell (SSH) Protocol

SSH File Transfer Protocol (SFTP)

SSH Implementation Version (sshlib)

Scripts fail on EFT Server when installed on the 64-bit Windows 2008 operating system.

Is EFT Server's AS2 module Drummond certified?

Forgetting the Admin Password

How can I purge EFT Server data from my SQL database?

Can I automatically ban an IP address that has tried to log in incorrectly multiple times?

Error 12002. The operation timed out

Activation and Registration on Windows Vista

Cannot connect to Server via CuteFTP (Windows Firewall configuration)

Can I use a Windows Command Prompt to send FTP Commands to a server?

Effect of Daylight Saving Time change on GlobalSCAPE Software

Changing the Root Folder of EFT Server while Retaining Permissions