Used ports in a Fabasoft environment
Summary
This article describes TCP/IP ports used in Fabasoft Folio installations. The article also touches ports used by network infrastructure and operating systems but makes no claims of being complete.
Information
Communication inside and outside the backend LAN
Ports used inside the backend LAN are printed "normal" into the backend LAN in "bold" and out from the backend LAN in "italic".
| Ports | Protocol/Service | Used by |
|---|---|---|
| 10000-10004 | app.telemetry | Port 10001 is used for communication between app.telemetry Server and Agents Ports 10000, 10002-10004 are used for app.telemetry Server internal communication |
| 18070-.... | RPC | Fabasoft Backend services (COO-/MMC-Services). Every service uses one port, default ports starts with 18070 increasing |
| 80 (81, 82, ...) | http | Fabasoft Web services, Fabasoft Conversion services under Microsoft Windows (IIS). Ports 81 and above are used when multiple service installations are used (configurable). |
| 443 (444, ...) | https (SSL) | Fabasoft Web services, Fabasoft Conversion services under Microsoft Windows (IIS). Ports 444 and above are used when multiple service installations are used (configurable). |
| 17060 (17061...) | http | eServices under Linux. |
| 17070 (17071...) | http | Fabasoft Conversion services under Linux. Ports 17071 and above are used when multiple service installations are used. |
| 17080 (17081...) | http | Fabasoft Web services under Linux. Ports 17081 and above are used when multiple service installations are used. |
| 17088 | http | Web Management Console under Linux |
| 17999 | RPC | Fabasoft Management Service |
| 23000 | http | Mindbreeze Administration Web Console |
| 23100-... | https | Mindbreeze Service Ports (Index Service, Query Service, Filter Service) as defined in the Mindbreeze configuration |
The Fabasoft Backendservices communicate with the Fabasoft Folio Kernel via UDP multicast ("Fabasoft UDP and Multicast Caching Protocol"). The multicast IP and port is configured in the current domain object. Therefore Backendservers and Kernel instances (webservers, conversion servers, etc.) should be located in the same subnet.
The webservice ports visible for clients depend on the usage of a load balancer.
Selection of network and operating system ports:
| Ports | Protocol/Service | Used by |
|---|---|---|
| 22 (TCP) | SSH | Linux SSH Sessions |
| 25 (TCP) | SMTP | Simple Mail Transfer Protocol (used if Fabasoft web and/or AT services are configured to send email notifications) |
| 53 (TCP/UDP) | DNS | Name resolution |
| 88 (TCP/UDP) | Kerberos | Kerberos Authentication |
| 123 (UDP) | NTP | Time synchronisation |
| 135 (TCP/UDP) | RPC | Windows RPC (for all Windows based services) |
| 389 (TCP/UDP) | LDAP | LDAP and AD |
| 636 (TCP/UDP) | LDAP SSL | LDAP and AD |
| 3389 (TCP/UDP) | RDP | Microsoft Remote Desktop Connection |
| 1025-5000, 49152-65535 (TCP) | AD | Dynamic ports for Active Directory communication |
For a complete list of Active Directory communication ports see Active Directory and Active Directory Domain Services Port Requirements .
List of TCP and UDP port numbers http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
Please note:
- Not all ports are used in every environment
- Some ports are configurable and may differ from this table. This table uses default ports of the Fabasoft Setup.
- Ports may differ depending on the existence and network location of additional components, for example authentication servers, mail servers
- This list raises no claim to completeness. Please test your environment carefully.
Applies to
- Fabasoft Folio (all versions)
- Fabasoft eGov-Suite (all versions)
- Fabasoft eCRM-Suite (all versions)