|
IMAP
|
null
|
Do not select the checkbox
|
|
The Netlet local port on the client side need not
be the same as the destination port on the server side.
If you use anything other than the standard IMAP and SMTP ports, make sure
that the client is configured to connect on a port that is different from
the standard port.
Solaris client users cannot connect to port numbers lower than 1024
unless they are running as root.
|
|
SMTP
|
null
|
Do not select the checkbox
|
|
|
|
Lotus Web Client
|
null
|
Do not select the checkbox
|
|
This rule tells Netlet to listen for the client on port 80, and connect
to the server lotus-server on port 80. A requirement of the Lotus Web Client
is that the client listen port must match the server port.
|
|
Lotus Notes Non-web Client
|
null
|
Do not select the checkbox
|
|
With this rule, the Lotus Notes client can connect to a Lotus Domino
server through Netlet. Ensure that when the client tries to connect to the
server it must not point to localhost as the server name.
It must point to the actual server name of the Lotus Domino server. The server
name must be the same as the system name for the server. The client must resolve
that name to 127.0.0.1 when using Netlet. Two ways to accomplish
this are:
-
Set the server name to point to 127.0.0.1 in
the client host table.
-
Export a DNS
entry of the name of the server that points to 127.0.0.1.
The server name must be the same server name that was used to configure
the Domino server during setup.
|
|
Microsoft Outlook and Exchange Server
This will not work for Windows NT, 2000 and XP. Use Outlook Web Access through the Rewriter for
Windows NT, 2000, and XP.
|
null
|
Do not select the checkbox
|
|
This rule tells Netlet to listen at port 135 on the client and connect
to the server exchange on port 135. The Outlook client
uses this port to make an initial attempt to contact the Exchange server and
determine what subsequent ports to use to talk to the server.
On the client machine:
-
The user must change the hostname of the Exchange server that
is configured in the Outlook client to localhost. The location
of this option varies with the version of Outlook.
-
The user must map the hostname (single and fully qualified)
of the Exchange server to the IP address 127.0.0.1 using
the hosts file.
-
On Windows 95 or 98, the file is in \\Windows\\Hosts
-
On Windows NT4, the file is in \\WinNT\\System32\\drivers\\etc\\Hosts.
The entry looks like this:
127.0.0.1
exchange exchange.company.com
The Exchange server sends
back its own name to the Outlook client. This mapping ensures that the Outlook
client uses the Netlet client to connect back to the server.
|
|
FTP
|
null
|
Do not select the checkbox
|
|
You can provide FTP service to a single FTP Server, with controlled
end-user accounts. This will ensure secure remote FTP transfers from an end-user
system to a single location. Without a username, an FTP URL is interpreted
as an anonymous FTP connection.
You must define port 30021 as the local port for
your Netlet FTP rule.
Dynamic FTP is supported using a Netlet connection.
|
|
Netscape 4.7 Mail Client
|
null
|
Do not select the checkbox
|
|
In the Netscape client, the user needs to specify:
localhost:30143 for IMAP or incoming mails
localhost:30025 for SMTP or outgoing mails
|
|
Graphon
|
third_party/xsession_start.html
|
Select the checkbox
|
-
Local Port: 10491
-
Destination Host: TARGET
-
Destination Port: 491
|
This is the rule used to access Graphon through the Netlet. xsession_start.html is bundled with Graphon.
|
|
Citrix
|
third_party/citrix_start.html
|
Select the checkbox
|
-
Local Port: 1494
-
Destination Host: TARGET
-
Destination Port: 1494
|
This is the rule used to access Citrix through the Netlet. citrix_start.html is bundled with Citrix.
|
|
RemoteControl
|
third_party/pca_start.html
|
Select the checkbox
|
-
Local Port: 5631
5632
-
Destination Host: TARGET
TARGET
-
Destination Port: 5631
5632
|
This is the rule used to access Remote Control through Netlet. pca_start.html is bundled with Remote Control.
|
