Grass Valley K2 Media Client System Guide v.3.3 - Manual (Page 79)

June 9, 2009 K2 Media Client System Guide 79
FTP access and configuration
Media Client. This applies to both stand-alone and shared storage K2 Media
Clients. For more information, refer to
Appendix A, Remote control protocols.
FTP access and configuration
For basic LAN access, the following Grass Valley products can connect as an FTP
client to the K2 FTP server with no special configuration required:
• K2 Media Client
• M-Series iVDR
• UIM-connected Profile XP Media Platform
For WAN access, contact your Grass Valley representative for assistance.
If the FTP client is not one of these Grass Valley products, contact the product’s
supplier or your network system administrator for assistance with configuring TCP
window scaling. Any computer that connects as an FTP client to the K2 FTP server
must have TCP window scaling enabled. Refer to http://support.microsoft.com/kb/
q224829/ for more information on this feature. Never set Tcp1323Opts without
setting TcpWindowSize. Also, Windows NT 4.0 does not support TCP window
scaling, but will still communicate with Grass Valley products in a LAN environment.
FTP access by automation
Using FTP, third parties can initiate transfers between two K2 systems or between a
K2 system and another FTP server. Transfers of this type are known as “passive” FTP
transfers, or “server to server” transfers.
If you are managing transfers with this scheme from a Windows operating system
computer, you should disable the Windows firewall on that computer. Otherwise,
FTP transfers can fail because the Windows firewall detects FTP commands and can
switch the IP addresses in the commands.
NOTE: You should disable the Windows firewall on non-K2 systems issuing passive
FTP transfer commands.
FTP security
Refer to “FTP and media access security” on page 140 .
FTP internationalization
The K2 FTP interface supports internationalization as follows:
• Non-ASCII localized characters represented as UTF-8 characters.
• All FTP client/server commands are in ASCII.
• The named movie asset is Unicode 16-bit characters
• The K2 FTP client converts between Unicode and UTF-8 strings explicitly.
The Microsoft FTP client does not convert from a Unicode string to a UTF-8 string.
Instead, it passes the Unicode string to the FTP server directly, which cause the errors.
To avoid these errors, in the FTP command, every reference to the clip path must be
in UTF-8.