This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


~Rebecca Umluberggon
Apr 19, 2018, 12:47 AM
2 Posts

Notes CLients unable to connect to domino server 9.0.1 on CentOS

  • Category: Configuring
  • Platform: Linux
  • Release: 9.0.1
  • Role: Administrator
  • Tags: server connection,administrator
  • Replies: 3

I've successfully installed Domino server 9.0.1 on a CentOS 7.4 server. I also installed the latest Fixpack. I was able to configure the server with the remote server setup tool and setup the certifiers for the server and the administrator. The server is running without a hitch.

HOWEVER, after installing the Administrator client on my windows 10 laptop, I am simple unable to connect to the server. In fact not even the notes client is able to connect to the server. I've used the IP address as well as the server name, but it just won't connect.

I'm able to ping the server, I'm able to connect to the server through the web browser, but notes clients WILL NOT connect.

It says can't find path to server or server is not responding. I've edited connection documents and location document, but no resolution.

My sense is that there is a firewall restriction on port 1352 on the linux server. Can someone else weigh in?

Thanks.

~Delores Opaverings
Apr 20, 2018, 1:18 AM
5 Posts
CentOS 7 firewall-cmd
IF it is a firewall issue, here's how you would go about fixing it. The following is from my company's internal wiki. The port # you're after for the Notes Client connecting to Domino Server is 1352/tcp so substitute that instead of 143/tcp for IMAP.

--------------


Modifying iptables in CentOS is done through FirewallD. Here are some simple examples of how you would use firewall-cmd to allow or block some traffic:

In most cases, you will use the first command, then after verifying all is well, also give the second command:

1. Allow IMAP immediately, lost after a reboot: or restart of FirewallD:
firewall-cmd --add-port 143/tcp

2. Allow IMAP after the next reboot or restart of FirewallD:
firewall-cmd --add-port 143/tcp --permanent



1. Stop allowing IMAP immediately:
firewall-cmd --remove-port 143/tcp

2. Stop allowing IMAP after reboot or FirewallD restart:
firewall-cmd --remove-port 143/tcp --permanent

Again, you'll probably want to test after the first command before entering the second one.

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal