In case of problems

FTP troubleshooting to/from ftp.ecurep.ibm.com

Use the following troubleshooting information if you are unable to access the ftp.ecurep.ibm.com server to transfer test cases to IBM, or you encounter other problems with the file transfer.

• Check the connection.
  • Is ftp.ecurep.ibm.com server up?
    To check if the site is responding, click on the following link: View the FTP site. A separate browser window should open, and if the site is up and your connection is active, text will be loaded.
  • The ping command will not work. The firewall will block these requests
    Note: If you are behind a firewall, ping generally only works within your local network.
  • How far did the connection get or where did it fail?
    Run traceroute, which shows the path to the server. The last IP address is the probable source of connection failure. The command traceroute will not show the FTP server, the firewall will block these requests
    Note: If you are behind a firewall, traceroute generally only works within your local network.
    • MS/DOS command - tracert
    • Unix command - traceroute
    • MVS, VM, OS/390 command - tracerte
• Check for timeouts
  • The FTP server timeout is 10 minutes if no data transfer. If your FTP session times out in less than 10 minutes, it is not the server that is timing out. The timeout value for the FTP client can usually be specified when FTP is invoked (i.e. timeout=nn where nn is in seconds). Check the documentation for the FTP client you are using to verify the parameters and/or syntax.
  • If you are submitting a large file via batch FTP, the batch job may time out. This is a function of the TIME= parameter on the JOB card. The file size can be reduced by compression (TRSMAIN), or the TIME= parameter can be increased or set to 1440.
• Files not on the server
  • Files received in /toibm/xxx directory not following the defined naming convention are routinely purged from the FTP server. These files require manual intervention by your IBM service representative or they are deleted after 7 Days.
  • Did the file get loaded on the server?
    Because of security considerations, the display of files on the server site '/toibm/' directories is limited to the directories themselves. No individual files can be listed. Files in the '/fromibm/' directories may be listed.
    View the FTP site.
• Server error messages
  If you receive error messages from the server, a connection is occurring. The server will return a 'Permission Denied ...' message for any of the following conditions:
  • Permission Denied upload name ((accept.
    • The filename cannot contain quotes or national characters (#,@,$). It can contain only a-z, A-Z, 0-9 and . (period).
  • Permission Denied upload.
    • The file already exists. You cannot replace existing files. Any 'replacements' must be loaded with a new file name.
  • Permission Denied on Server.
    • Invalid directory is specified.
• Passive mode
  It is recommended that to use "passive" mode for FTP transmissions.
  If none of these procedures solves the problem, further diagnosis can be performed to identify the failure. The testcase server maintains logs of all activity, and the date and time of the transfer problem is needed for further diagnosis. Use the PMR for which the file is being transfered to report any FTP problems you are unable to resolve.
  

Common Firewall

• I can connect to the FTP server. The connection hangs after the ls, dir, put or get command.
  • Use passive FTP. This is done with the "passive" command for most command line clients. If your client does not offer the passive command it will use active FTP properly.
• My FTP client is using passive FTP, but the session still hangs after the ls, dir, put or get commands.
  • Ask your firewall administrator to allow connections to the port range 65024 - 65535 for our FTP server.
• Your firewall may check the control connection for the protocol.
  • Ask your firewall administrator about the setup of your firewall.
    For a CheckPoint Firewall-1 NG, for example, the new line character check must be disabled. Check out Solution ID sk22632.

HTTP(S) troubleshooting uploading to www.ecurep.ibm.com

• I cannot upload a file larger than 2 GByte.
  • The current implementation of Firefox and Internet Explorer does not allow HTTP uploads that exceed a 2 GByte limit. If you are trying to upload multiple files in one session (up to five are offered), please make sure that the total upload size is less than 2 GByte. If a single file is larger than 5 GByte, either use FTP or SFTP for the file upload or split the file.

In case you have any problem with this service please contact contact@ecurep.ibm.com