Transfer mechanisms, Ftp access and configuration, Transfer mechanisms ftp access and configuration – Grass Valley K2 Media Client System Guide Oct.10 2006 User Manual
Page 69
September 7, 2006
K2 Media Client System Guide
69
Transfer mechanisms
If using VDCP to initiate transfers between K2 systems and Profile XP systems, you
must send the VDCP command to the K2 system, not the Profile XP system. Transfers
(both push and pull) are successful if the K2 system hosts the command. Transfers fail
if the Profile XP system hosts the command.
“Transfer compatibility considerations” on page 139
Transfer mechanisms
You can move material between the systems using the following mechanisms, each
of which offers a different set of features:
• Manual mechanisms — These are the AppCenter transfer features. Refer to the K2
Media Client User Manual for AppCenter instructions. When transferring between
K2 systems you can browse and select files for transfer. When transferring between
K2 systems and other types of systems, one or more of the following might be
required, depending on software versions. Refer to release notes for the version
information:
- Specify the IP address, path, and file name to initiate a transfer.
- Add the remote host in Configuration Manager before the transfer.
- Enter machine names in compliance with UIM naming conventions.
• Automatic mechanisms, including the following:
• K2 FTP interface — This interface supports transfers via third party FTP
applications. For example, you can use Internet Explorer to transfer files
between a PC and the FTP interface on a K2 Media Client (with internal storage
only) or a K2 Media Server on the same network. For more information, refer to
“FTP access by Internet Explorer” on page 70
• Remote control protocols — Industry standard remote control automation
applications can initiate transfers. The protocol command must be sent to the K2
Media Client. This applies to both internal storage and external storage K2
Media Clients. For more information, refer to
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 Clients
• 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/