NomadWeb cannot acces secondary server after domno update

HCL Domino Domino Forum
,
1

Domino/Notes Version: 14.5FP1
Add-on Product (if appropriate, e.g. Verse / Traveler / Nomad / Domino REST API): NomadWeb
Its Version:
Operating System: AlmaLinux9
Client (Notes, Nomad Web, Nomad Mobile, Android/iOS, browser version): Nomad Web

Problem/Query:

Hi,

we have a nomad server R1.0.17 on a Domino 14.5FP1 (linux), working.

we just upgraded a second Domino server in our Domain from 14.0R to 14.5FP1 and this second server is not anymore reacheble with Nomad Web.

The message is: “impossible to find a path to SecondServer/OURDOMAIN because the remote system is not responding anymore”.

Is there something changing from 14.0R to 14.5FP1 that can deny the access to NomadWeb clients?

Or how can we check how Nomad try to connect to the server SecondServer/OURDOMAIN?

(We have also a ThirdServer/OURDOMAIN 12.0.2FPH5HS8 that is still reacheable via NomadWeb)

Thanks a lot for any help

tommaso

2

Hi Tommaso,

Thank you for reaching out and for sharing the details of this issue.

To properly investigate this complex connectivity problem, we recommend raising a case directly with HCL Software Support. This will allow our team to thoroughly review the server configurations and logs from both the working Nomad server and the newly upgraded Domino server to identify the root cause.

Once the case is created, please include any relevant log excerpts or error messages observed during the connection attempts, as these will greatly help in the analysis.

Regards,
PJ

3

Hi tommaso,

Have you tried specifying all your servers in the nomad-config.yml file?

servers:
CN=domino/O=EXAMPLE: 127.0.0.1:1352

See Setting the servers addresses and ports in this documentation:

4

Hi Julie,

as suggested we opened a ticket and HCL Technicians lead us to the solution you mention.

Strange is that with ohter servers the connection works without changing nomad-config.yml file

Probabily it is connected with this strange behaviour that emerged with HCL technicians.

Let’s say that NOMADSERVER/OURDOMAIN (nomadserver.ourdomain.it) is the server Nomad is installed on
and

and SECONDSERVER/OURDOMAIN (secondserver.ourdomain.it) is the server we can’t connect with using NomadWeb

If from NOMADSERVER/OURDOMAIN console I do a trace to the hostname it works:

trace secondserver.ourdomain.it
[522839:000007-00007F11107FF640] Determining path to server SECONDSERVER.OURDOMAIN.IT
[522839:000007-00007F11107FF640] Available Ports: TCPIP
[522839:000007-00007F11107FF640] Checking normal priority connection documents only…
[522839:000007-00007F11107FF640] Allowing wild card connection documents…
[522839:000007-00007F11107FF640] Enabling name service requests and probes…
[522839:000007-00007F11107FF640] Checking for SECONDSERVER.OURDOMAIN.IT on TCPIP using address ‘SECONDSERVER.OURDOMAIN.IT’
[522839:000007-00007F11107FF640] Requesting IP Address for SECONDSERVER.OURDOMAIN.IT from DNS
[522839:000156-00007F11019A6640] 11/07/2025 10:18:05 Remote console command issued by Tommaso/OURDOMAIN: trace secondserver.ourdomain.it
[522839:000007-00007F11107FF640] DNS returned address 12.13.14.15 for SECONDSERVER.OURDOMAIN.IT
[522839:000007-00007F11107FF640] Requesting IP Address for SECONDSERVER.OURDOMAIN.IT from DNS
[522839:000007-00007F11107FF640] DNS returned address 12.13.14.15 for SECONDSERVER.OURDOMAIN.IT
[522839:000007-00007F11107FF640] SECONDSERVER.OURDOMAIN.IT is the address of server CN=Astor_Piazzolla/O=MAGRITTE
[522839:000007-00007F11107FF640] Connected to server SECONDSERVER/OURDOMAIN
[522839:000007-00007F11107FF640] Attempting Authenticated Connection
[522839:000007-00007F11107FF640] Compression is Disabled
[522839:000007-00007F11107FF640] Encryption is Enabled

while if I do a trace with the IP it doesn’t

trace 12.13.14.15
[522839:000007-00007F11107FF640] Determining path to server 12.13.14.15
[522839:000007-00007F11107FF640] Available Ports: TCPIP
[522839:000007-00007F11107FF640] Checking normal priority connection documents only…
[522839:000007-00007F11107FF640] Allowing wild card connection documents…
[522839:000007-00007F11107FF640] Enabling name service requests and probes…
[522839:000007-00007F11107FF640] Checking for 12.13.14.15 on TCPIP using address ‘12.13.14.15’
[522839:000156-00007F110047C640] 11/07/2025 10:19:23 Remote console command issued by Tommaso/OURDOMAIN: trace 12.13.14.15
[522839:000007-00007F11107FF640] Connected to the wrong server SECONDSERVER/OURDOMAIN using address 12.13.14.15
[522839:000007-00007F11107FF640] Connected to the wrong server SECONDSERVER/OURDOMAIN using address 12.13.14.15
[522839:000007-00007F11107FF640] Unable to connect to 12.13.14.15 on TCPIP (Connection denied. The server you connected to has a different name from the one requested.)
[522839:000007-00007F11107FF640] Checking low and normal priority connection documents…
[522839:000007-00007F11107FF640] No default passthru server defined
[522839:000007-00007F11107FF640] Unable to find any path to 12.13.14.15 because Impossibile trovare il percorso al server. Verifica la connessione di rete o VPN. Se la connessione è attiva, vai a Preferenze > Porte Notes e fai clic su Traccia per scoprire

weird

That’s why the following lines in nomad-config.yml doesn’t work for us (I think you must respect indentation in yml file)

servers:
CN=SECONDSERVER/O=OURDOMAIN: 12.13.14.15:1352

while the lines

servers:
CN=SECONDSERVER/O=OURDOMAIN: secondserver.ourdomain.it:1352

are the working ones.

note that the IP 12.13.14.15 is never used in the connection documents between the two servers

At present, in spite of this behaviour that sound strange to me, everything works and we are happy.

thanks a lot

tommaso