In order for Ares to operate properly, certain network ports are required to be open. There are also some optional ports you may choose to use.
Required Network Ports
In order to allow access to Ares and its various component parts, the following ports are required to be open.
Port opened outbound from web server and clients to SQL Server. This allows the Ares client to communicate with the database. This would only need to be open for the web server (if separate server) and the Ares clients to access the SQL Server. If you have changed the port used by SQL Server, this port number will be different.
|Public Web Pages||443 or 80||
Port opened inbound to all or any IP ranges that are allowed access to the Ares web forms. This allows customers to access the Ares Web pages and receive RSS Feeds. This would need to be open to everyone or could be restricted if you wanted to limit access to the customer interface (not commonly done).
Use port 443 for secure web pages (recommended) or 80 for non-secure pages.
|Ares Updates Server||20 and 21 (Hosted Sites)||
Ports opened for the Server AutoUpdater. This allows the Server AutoUpdater to FTP new versions of Ares components from the Atlas server. This only needs to be open to update.atlas-sys.com.
This is the default SMTP server port to be used for sending Ares email. The web server needs to be able to see the SMTP server.
To change the port that the Ares client uses to connect to Microsoft SQL Server, create or edit your existing logon.dbc file and enter 18.104.22.168,1344 into the Server field, where 22.214.171.124 is your server IP address.
Optional Network Ports
You may want to opening the following ports if you use the services described.
If you plan on using Z39.50 to search your local OPAC from within Ares, you will need to check that the Ares client machines have access to the Z39.50 server over that port. This port differs from OPAC to OPAC so you will need to verify that value. The client needs to be able to connect to the port to display local holdings information.
|LDAP||389 or 636||
The Ares web server needs to be able to communicate with the LDAP server outbound to authenticate if using LDAP authentication. The LDAP server needs to allow traffic from the Ares web server's IP to request authentication. Port 389 is used for standard LDAP and 636 is used for SSL.
The Ares web server needs to be able to communicate with the PatronAPI server outbound to authenticate if using PatronAPI authentication. While this port is typically 4500, the port may differ based on your unique setup.
|Remote Desktop Connection||3389||
This would be opened only if you wish to allow customer support to access your Ares server via Remote Desktop Connection.