Troubleshooting
Problem
This document discusses the FTP client file size limits on the Microsoft® Windows® 2003 server and explains how to circumvent it.
Resolving The Problem
Apparently, the native FTP client available with the Microsoft® Windows® 2003 server is limited to 2Gb file sizes
(that is, file sizes <= 2Gb). Therefore, any time you try to send a file that is above 2Gb, the put FTP sub-command
will fail with the following message:
> bigfile: Inode is remote
For example, take a look at the following print screens:
1. We have a file that is above 2Gb in size: bigfile (2.82Gb):
2. We try to send it to our IBM® System i® products system using FTP; however, the transfer fails with the
message Inode is remote:
The above error is related to the Microsoft Windows 2003 server's FTP client rather than the IBM®
OS/400® or i5/OS® FTP server.
3. We turn it on hash printing by running the hash FTP sub-command:
4. We submit the put FTP sub-command again:
5. This time the transfer completes with success:
Recommendation
To ensure that you will be able to transfer any file from the Microsoft Windows 2003 server environment to an
OS/400 or i5/OS environment regardless of its size, turn on Hash mark printing before you submit the put FTP
sub-command.
Historical Number
424603464
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1014809