Grass Valley K2 System Guide v.9.0 - Manual (Page 76)

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 Summit Production Client
• K2 Media Client
• K2 Solo Media Server
• 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 and media access security
The following systems host the K2 FTP interface:
• A stand-alone K2 system.
• A K2 Media Server that takes the role of FTP server
The way in which the K2 FTP interface applies media access security is explained in this section.
The K2 FTP interface uses the credential information for the current FTP session logon and checks
it against the access control list for a K2 bin. This is the access control list that you set up through
the Organize Bins dialog box in AppCenter. Any media access related operations such as get, put,
dir, rename and delete are checked against the FTP session’s logon credentials to access the media.
For example, if an FTP session is denied access to List Bin Contents for bin A, then the session can
not initiate a dir operation on bin A to list the contents of the bin. Furthermore, the session can not
transfer clips into bin A using the put operation.
For the purpose of compatibility FTP access conventions, accounts for user movie or user mxfmovie
are provided on the K2 system. There is also a video_fs account for Mac/FCP access. These accounts
76 K2 System Guide 06 November 2012
System connections and configuration