INFO: How To Connect
Through Proxy
This document applies to:
Product(s): SBE. Office Connect, 1500, 2500, 3500
and 5000
Last Revised:
7-17-2000
SUMMARY
This document contains information on ports/protocols used in FaxMain to
FaxPress communication
DESCRIPTION
This notice contains information on ports/protocols used in FaxMain to
FaxPress communication.
This is an information notice regarding the ports and protocols used by
FaxMain and FaxAlert to communicate with FaxPress server. This information
is useful for
a. Network packet analysis
b. Network topologies with a proxy or firewall between client PCs
and FP server
This notice does not contain information on
a. FaxPress to file server protocols. Hence this notice does not
provide information on firewall/proxy issues between the FaxPress and the
File Server. It is assumed that the FP and FS can communicate without
restriction.
b. Admin utilities (i.e. cfconfig, wntconf etc.) to FaxPress
protocols. It is assumed that these utilities can communicate with the FP
without restriction.
This information applies to all client software that uses CPI to
communicate with FaxPress. This includes
a. FaxMain
b. FaxAlert
c. Cover page editor
d. Quick router viewer
e. Exchange Direct
f. SMTP Gateway
g. Notes gateway, ccMail gateway
h. SDK utilities (submitfax etc)
i. Custom programs written on top of CPI
At
this time, this notice includes information only on TCP/IP protocol
communication between clients and FaxPress and not IPX communication.
These are the rules:
1. All client to FaxPress communication is by UDP
2. The "server enumeration" function is done through a UDP level
broadcast. This will likely not work in a situation with a proxy or a
firewall between the client and FP. Thus the FP will have to be enumerated
using the "advanced" function in the server list dialog.
3. Almost all communication between client and server is initiated
by the client to the FP. There is almost always a response packet from the
server to the client. All packets are UDP (however state is maintained by
the server at a higher level, also packet loss is handled by a combination
of client retries and timeouts)
4. Request Packets from client to server have the following
characteristics, which should be useful in setting up firewalls/proxies
Protocol: UDP
Source Port: any/client dependent
Source IP: client IP address
Dest Port: 0x1224 (decimal: 4644)
Dest IP: FaxPress IP
5. Response packets from server to client have the following
characteristics, which should be useful in setting up firewalls/proxies:
Protocol: UDP
Source Port: 0x1224 (decimal: 4644)
Source IP: FaxPress IP
Dest Port: any/client dependent (same as associated request packet)
Dest IP: client IP address
6. There is only one situation where the FP sends an uninitiated
packet to the client. This is for FaxAlert. If alerting is not desired,
the below can be ignored.
Protocol: UDP
Source Port: 0x1224 (decimal: 4644)
Source IP: FaxPress IP
Dest Port: any/client dependent
Dest IP: client IP address
The above information
should be complete information to build firewall/proxy rules for client to
FaxPress communication.
