459
Enabling remote access with clientless VPN
Identifying resources with URLs
Using Telnet sessions
Th security gateway supports remote logon from the user interface to other computers using Telnet
sessions. Telnet is a basic resource that lets administrators control the specific hosts (for example,
computer) that the user can access. Telnet uses the following syntax:
protocol://hostname:port
The protocol is always telnet. The host name is either the fully qualified domain name or the IP
address of the host computer. The port is optional; only specify a port if it is different than the default
Telnet port, 23.
The following table shows an example of a Telnet URL for a Telnet resource on an intranet server.
TCP port forwarding
The security gateway supports TCP/IP port forwarding. This feature lets users connect to any TCP/IP
resource (for example, application/applet) behind the security gateway without reconfiguring the
application client.
The TCP/IP port forwarding feature changes the host files on the end-user’s computer. Therefore, only
users who have permission to modify the host files on their computer (client) can access TCP
resources. The following clients can access TCP resources using clientless VPN:
■
Microsoft Windows 2000 or XP with FAT or FAT derivative partitions
■
Microsoft Windows 2000 or XP with administrator rights and NTFS
■
Apple MAC OS X
Any resource link can be configured on a portal page to automatically start when the user signs on.
Autostart is particularly useful for mail applications.
See
“Autostarting resources”
on page 16.
TCP/IP resources use the following syntax:
protocol://hostname:port
The following table shows an example of TCP resource on an internal server.
Table 11-16
telnet://engineering.symantecexample.com:81
URL
Example
protocol
telnet
host
engineering.symantecexample.com
port
81
Table 11-17
tcp://marketing.symantecdomain.com:110
URL
Example
protocol
tcp
host
marketing.symantecdomain.com
port
110
Summary of Contents for Security 5600 Series, Security 5400 Series,Clientless VPN 4400 Series
Page 76: ...76 Managing administrative access Enabling SSH for command line access to the appliance...
Page 242: ...242 Defining your security environment Controlling full application inspection of traffic...
Page 243: ...243 Defining your security environment Controlling full application inspection of traffic...
Page 269: ...268 Limiting user access Authenticating using Out Of Band Authentication OOBA...
Page 373: ...372 Preventing attacks Enabling protection for logical network interfaces...
Page 509: ...508 Generating reports Upgrade reports...
Page 553: ...552 Advanced system settings Configuring advanced options...
Page 557: ...556 SSL server certificate management Installing a signed certificate...
Page 861: ...860 Index...