Establishing a Server Environment 17
162 Root path to the FTP
Optional string. If the option provided by the
server is blank and the server provides no value
for the field, a null string is used.
\wyse\wnos is automatically appended to the
search path. For example, if you enter
pub\serversoftware, the path searched will
be pub\serversoftware\wyse\wnos.
Note: You can have the \wyse automatic
component of the search path omitted by
appending a dollar sign ($) to the entered path.
For example, if you enter
pub\serversoftware$, the path searched will
be pub\serversoftware\wnos.
Note: The usage or omission of a leading slash
(\) on the path is critical on some servers. Some
servers limit access to the root path of the user
specified at login. For those servers, the usage of
the leading slash is optional. Some *NIX servers
can be configured to allow the FTP user access to
the entire file system. For those servers,
specifying a leading slash specifies that access is
to start at the root file system. Proper matching of
the file specification to the FTP server in use is
critical to ensuring proper operation. A secured
Windows server requires the slash be specified in
order to complete proper access.
181 PNAgent/PNLite server
Optional string. The thin client uses the server to
authenticate the Windows credentials of the user
and to obtain a list of ICA published applications
valid for the validated credentials. The user
supplies those credentials when logging in to the
thin client.
182 NT domain list for
Optional string. The thin client creates a pull-down
list of domains from the information supplied in
option 182. This list is presented at thin client login
in the order specified in the DHCP option (for
example, the first domain specified becomes the
default). The selected domain is the one which
must authenticate the user ID and password. Only
the selected domain is used in the authentication
process. If the domain list is incomplete and the
user credentials must be verified against a domain
not in the list (assuming that the server in option
181 is capable of authenticating against a domain
not in the list), the user has the option of not using
any of the domains specified in option 182 and
typing a different domain name at the time of
Table 1 DHCP Options, Continued
Option Description Notes
Terms of Use | Privacy Policy | DMCA Policy
2006-2020 Rsmanuals.com