Use this command to configure TN3270 Plus to connect to a host computer via a proxy server or firewall. This command displays the Proxy Server Pane of the Session Setup dialog box. the Proxy Server pane contains the following options.
|None||Check this box if you are not connecting via a proxy server.|
|SOCKS 4 Protocol||Check this box if your proxy server uses the SOCKS version 4 proxy server protocol.|
|SOCKS 4A (proxy can resolve host names)||Check this box if your proxy server uses the SOCKS version 4A proxy server protocol.|
|Telnet||Check this box if your proxy server uses the Telnet proxy server protocol.|
|HTTP||Check this box if your proxy server uses the HTTP proxy server protocol. After connecting to the proxy server the following data is sent:|
CONNECT host::port HTTP/1.1
Proxy-Authorization: Basic username:password
|Proxy Port||Enter the proxy server port number.|
|Username||(Optional) Enter the user name required by the proxy server. This field is only valid for the HTTP proxy server protocol.|
|Password||(Optional) Enter the password required by the proxy server. This field is only valid for the HTTP proxy server protocol.|
|Connect Command||(Optional) This field is used differently for non-SOCKS compliant and SOCKS compliant proxy servers.|
For non-SOCKS compliant proxy servers, enter the connection command required by the proxy server. You can use the following variables in your connect command:
|$HOST||Replaced with the Host Name from the Host Pane.|
|$PORT||Replaced with the Port Number from the Host Pane.|
|<CR>||Sends a carriage return to the proxy server.|
|<LF>||Sends a line feed to the proxy server.|
For example, WinGate, a popular proxy server/firewall, prompts the user for the host name and port number. The following "Connect Command" string works with WinGate:
For a SOCKS compliant proxy server, enter the USERID for SOCKS authentication.
WinGate™ is a registered trademark of Deerfield.com (http://wingate.deerfield.com/)
TN3270 Plus is continually being improved. To learn more about the latest enhancements, please review our Version History web page.