- Introduction
- Installation
- crossAdmin
- Setting up Across Modes
- Softkeys
- Generating crossGrid Certificates
- Creating Generic Softkeys
- Changing the Across Database User
- Defragmenting Database Files
- Running a Backup
- Auto-Deployment
- Automatic Client Update
- Windows Authentication
- Uninstalling
- Reference: Menus in crossAdmin
- Appendix
Network Configuration
The identification of your Across Server for other Internet users (e.g. other Across Servers and/or crossWAN load Clients) is done by means of IP addresses.
The communication or data exchange with the above-mentioned external Across Servers and crossWAN load Clients takes place via so-called ports.
In order to enable data communication with external Across Servers or Clients, firewall ports must be opened.
If you only want to use the Across Server for your internal network and no firewall is active on the clients, no firewall ports need to be opened under normal circumstances.
If a firewall is active on the clients, you need to open the ports specified in the following figure.
The following figures show the required firewall settings for some common installation scenarios. The specified ports are the default ports that are predefined by Across. These ports can be changed if necessary.
The following scenarios are available:
Across Online Client Scenario
The connections between the individual Across components require the following ports to be opened:
Connection | Protocol | Port |
Across Online Client -> Across Server | TCP | 2309 2310 2311 |
HTTPS | 443 | |
HTTP | 80 | |
Across Online Client -> Database Server | TCP | 1433, 80 |
or | ||
UDP | 1434 | |
Across Server -> Database server | TCP | 1433 |
or | ||
UDP | 1434 |
crossWeb Client Scenario
The connections between the individual Across components require the following ports to be opened:
Connection | Protocol | Port |
crossWeb Client -> Database Server | HTTPS | 443 |
or | ||
HTTP | 80 | |
crossWeb Server -> Database server | TCP | 2309 2310 2311 |
or | ||
UDP | 1434 | |
crossWeb Server -> Database server | TCP | 1433 |
or | ||
UDP | 1434 | |
Across Server -> Database server | TCP | 1433 |
or | ||
UDP | 1434 |
crossGrid with ATE Offline Client (crossWAN Load Client)/Across Online Client (Trusted Server) via crossVPN Scenario
The connections between the individual Across components require the following ports to be opened:
Connection | Protocol | Port |
Across Offline Client (ATE)/ Across Online Client (Trusted Server) -> crossVPN Server | TCP | 2322 |
crossVPN Server -> Across Server | TCP | 2309 |
crossVPN Server -> Database server | TCP | 1433 |
or | ||
UDP | 1434 | |
Across Server -> Database server | TCP | 1433 |
or | ||
UDP | 1434 |
crossGrid with ATE Offline Client (crossWAN Load Client)/Across Online Client (Trusted Server) via crossVPN Proxy Scenario
*These ports can also be deactivated.
**Requires a separate license.
The connections between the individual Across components require the following ports to be opened:
Connection | Protocol | Port |
Across Offline Client (ATE)/ Across Online Client (Trusted Server) -> crossVPN Server | TCP | 2322 |
crossVPN Server -> Across Server | TCP | 2309 |
crossVPN Server -> Database server | TCP | 1433* |
or | ||
UDP | 1434* | |
Across Server -> Database server | TCP | 1433 |
or | ||
UDP | 1434 |
* | These ports can also be deactivated. |
For further information, please consult your contact at Across Systems GmbH.
General information on Across services is available at www.across.net/en/services/.