When EFT Server’s Download and Copy/Move action offloads or downloads files to/from other servers, the session is recorded to a log file: cl[yymmdd].log, e.g., cl060312.log.
The contents of the log file is formatted as follows:
Time; Protocol; Host Name; Port; User Name; Local Path; Remote Path; Operation; GetLastCode
For example:
2006-03-06 10:11:03; ftp; 192.168.20.171; 21; ClientA; C:\test1.txt; /test1.txt; download; 226;
The log can be used for troubleshooting connection and transfer errors. The "GetLastCode" value returns the protocol success or error code or socket error. For example, trying to connect to a non-existent Web site will result in the socket error code 10060, connection timeout. Refer to "Windows Sockets Error Codes" in the Microsoft Developer Network for a complete list of common socket error codes. Aside from the standard socket error codes, EFT Server defines a few of its own:
|
# |
Description |
|
0 |
Success (connected OK) |
|
1 |
General socks failure |
|
2 |
Socket connection not allowed by ruleset |
|
3 |
The network is unreachable |
|
4 |
The host is unreachable |
|
5 |
The remote server actively refused the connection |
|
6 |
The Time To Live (TTL) expired. This could indicate a network problem. |
|
7 |
The command was not supported by the remote host. Also a catch all error code. |
|
8 |
The address type or format is not supported |
|
10 |
Illegal socks name |
|
11 |
Socks5 authentication failure (username/password incorrect) |
|
12 |
Can't connect to socks server |
|
2000 |
Internal timeout error code (multiple reasons, such as firewall blocking connection, etc.) |
FTP and FTP over SSL only return protocol-level success and error codes. For example, a successful transfer would return 226 or a bad login password would return 530. Refer to RFC 959 for a complete list of FTP/S return codes.
SFTP (SSH2) returns the following success and error codes:
|
# |
Description | ||
|
-1 |
Undefined or unknown error (not enough information to determine exactly why it failed)
| ||
|
0 |
The operation completed successfully | ||
|
1 |
The operation failed because of trying to read at end of file | ||
|
2 |
The requested file does not exist | ||
|
3 |
Insufficient privileges to perform the operation | ||
|
4 |
The requested operation failed for some other reason | ||
|
5 |
A badly formatted message was received. This indicates an error or incompatibility in the protocol implementation | ||
|
6 |
Connection has not been established (yet) and a timeout occurred | ||
|
7 |
Connection to the server was lost, and the operation could not be performed | ||
|
8 |
A timeout occurred |
