#dominoforever | Product Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Possibility to configure a different TCP port for NRPC communication than only 1352

It would be nice to have the possibility to configure NRPC to use a different TCP port than 1352.


Moving NRPC to a different than the default port would make finding Domino services - a little bit - harder for those mass-port-scanners in the net.


Also it would be a way to circumvent hotel WLANs, guest WLANs in businesses or other public hotspots that block all not well-known TCP ports. Exposing Domino on a well-known port should make connections from these WLANs still be possible.


On the server side in most cases you will have a firewall in front on Domino. There you might use port-mapping to route incoming traffic on the non-default port to the default port internally.


But you still would need an option to tell the Notes client to connect to this port instead of 1352.

  • Guest
  • Aug 16 2022
  • Already Exists
  • Attach files
  • Guest commented
    18 Aug 01:45pm

    Ah okay. Thank you very much!


    HCL support told me it is not possible (CS0337011), so I wrote this idea. :-)


    Indeed, the client uses an alternative port one configured in the connection document when keeping the following pitfalls in mind:

    • Changing the IP and/or port of the server using the "Client reconfiguration wizard" obviously does not change existing connection documents. You have to change it directly in the connection documents.

    • As long as the "old" connection is still working (because we are configuring an ADDITIONAL way to connect to the server here), Notes will still use this way to connect even if the connection document already contains the new connection. Only when it cannot connect to the "last known address" anymore, Notes reconsiders the connection documents.


    I am still struggling to get the server to listen on an additional port like you described. But as I already told, this is no great problem because we may use firewall port mapping.


    BTW: Is there an *easy* way to clear the cached "last known address" in the Notes Client without writing agents or so?

  • Admin
    Thomas Hampel commented
    16 Aug 12:50pm

    You can already do this.
    you can define an ADDITIONAL port by adding the port number in the Network address field.

    To connect your client to this port, you will need to setup connection documents that also specifiy the port number