Cisco Cisco Virtualization Experience Client 2111 Administrator's Guide
A-7
Cisco Virtualization Experience Client 2112/2212 ICA Administration Guide for WTOS 7.0_214
OL-215152-01
Appendix A Central Configuration: Automating Updates and Configuration
Configuring Network Services
Configuring FTP Servers
Before you use the information in this section to configure your FTP server, be sure you understand and
use the following guidelines:
use the following guidelines:
•
General Guideline—When the zero client boots, it accesses the software update images and INI files
from the FTP server. The FTP server and path to the software update files are available through
DHCP vendor options 161 and 162 (see
from the FTP server. The FTP server and path to the software update files are available through
DHCP vendor options 161 and 162 (see
). If these
are not specified, the default FTP server is the DHCP server from which the zero client receives its
IP address and the default directory (\wnos for Windows FTP servers, or /wnos for Linux FTP
servers).
IP address and the default directory (\wnos for Windows FTP servers, or /wnos for Linux FTP
servers).
The FTP server and path to the software update files can also be specified locally on the zero client.
DHCP options 184 and 185 can be used to provide the User ID and Password for non-anonymous
access to the FTP server in WTOS.
DHCP options 184 and 185 can be used to provide the User ID and Password for non-anonymous
access to the FTP server in WTOS.
•
Non-Anonymous Access Guidelines—You must first create a local account (name the account so
that you remember it is a non-anonymous account) on the FTP server defined between the DHCP
vendor options 161 and 162 (DHCP server). Then, add DHCP options 184 and 185 to provide the
User ID and Password for non-anonymous access to the FTP server. Ensure that option 184 is the
account User ID and that option 185 is the account Password, and that you keep consistency with
FTP server DHCP vendor options (for example, ensure that the 184 and 185 options are string
parameters). Then provide the non-anonymous account with read-only permissions through the
entire FTP server path. Be sure to modify these guidelines according to your specific security
environment and configuration.
that you remember it is a non-anonymous account) on the FTP server defined between the DHCP
vendor options 161 and 162 (DHCP server). Then, add DHCP options 184 and 185 to provide the
User ID and Password for non-anonymous access to the FTP server. Ensure that option 184 is the
account User ID and that option 185 is the account Password, and that you keep consistency with
FTP server DHCP vendor options (for example, ensure that the 184 and 185 options are string
parameters). Then provide the non-anonymous account with read-only permissions through the
entire FTP server path. Be sure to modify these guidelines according to your specific security
environment and configuration.
•
Windows FTP Server Guideline—You can use the FTP tools available on the Windows server. For
WTOS, this support is not necessary because of the User Interface (UI)/DHCP feature to specify the
login ID and password.
WTOS, this support is not necessary because of the User Interface (UI)/DHCP feature to specify the
login ID and password.
•
Linux FTP Server Guideline—Be aware of the following:
–
The FTP server must be configured to offer FTP services (by adding the following line or
equivalent to the /etc/inetd.conf file, if it is not already present):
equivalent to the /etc/inetd.conf file, if it is not already present):
ftp stream tcp nowait root /usr/sbin/tcpd in.proftpd
–
The FTP server must be configured to support anonymous FTP. For most FTP servers, this
requires establishment of an FTP login account by adding the following line or equivalent to the
/etc/password file:
requires establishment of an FTP login account by adding the following line or equivalent to the
/etc/password file:
ftp:x:17:1:Anonymous FTP directory:/home/ftp:/dev/null/ftp-shell
The shell file /dev/null/ftp-shell need not exist, but some FTP servers require that it be listed in
the /etc/shells file to allow FTP connections on this account.
the /etc/shells file to allow FTP connections on this account.
–
Depending on which Linux distribution you are using, additional modifications to a central
configuration file for the FTP daemon may be necessary to enable anonymous FTP. You can try
man protftp, man wuftpd, or man ftpd to access information applicable to your particular FTP
daemon.
configuration file for the FTP daemon may be necessary to enable anonymous FTP. You can try
man protftp, man wuftpd, or man ftpd to access information applicable to your particular FTP
daemon.
–
A Linux server used for FTP must support passive FTP.
•
FTP Folder Structure Guidelines—The FTP folder structure that is required by zero clients running
WTOS is \wnos and must be placed under the FTP root folder (if DHCP option tag 162 is not used)
or under the folder which has been specified by DHCP option 162. For example, if DHCP option
tag 162 has been configured with the name ThinClients and DHCP option tag 161 has been
configured with IP address 192.168.1.1, then the zero client will check the folder
<FTPRoot>\ThinClients\wnos for a wnos.ini and firmware on the FTP server with the IP address
(192.168.1.1). The sub-folder \bitmap must be placed under the \wnos folder and can contain
WTOS is \wnos and must be placed under the FTP root folder (if DHCP option tag 162 is not used)
or under the folder which has been specified by DHCP option 162. For example, if DHCP option
tag 162 has been configured with the name ThinClients and DHCP option tag 161 has been
configured with IP address 192.168.1.1, then the zero client will check the folder
<FTPRoot>\ThinClients\wnos for a wnos.ini and firmware on the FTP server with the IP address
(192.168.1.1). The sub-folder \bitmap must be placed under the \wnos folder and can contain