Domino Server Setup Failing

HCL Domino Domino Forum
1

Hi all,

I am setting up an additional server in a remote location. I have opened up port 1352 incoming/outgoing on the firewall. I put in the main server name and ip for this setup to download the main files needed for setup however it fails at 20% saying “The server is not responding. The server may be down or you may be experiencing network problems.”

I can telnet to the target server on port 1352 so i know there is no network problems.

Can anyone help? I’m a little lost at this point.

Thanks

2

Subject: Domino Server Setup Failing

Ok well after nothing else would work I set up a vpn between the two offices and it worked straight away. Took away the vpn and the new machine can replicate with the existing server. Perhaps there is an extra port that the setup process uses?

3

Subject: Domino decides ports on its own

Isn’t the port 1352 on Domino server, used by a Notes client to connect to it? For Domino server to Domino server interactions (replication, mail routing, directory lookup etc) the port is decided by Domino itself. For each service it could be using a different port. I would suggest, open the firewall for all ports(high ports) between the two Domino servers, to begin with. Then you can fine tune it later once things are up and running.

Also verify the host names you had given into Domno configuration gets resolved on both the networks - the one inside forewall and the one outside firewall.

Regards,

Byju

4

Subject: RE: Domino decides ports on its own

Port 1352 is used in all NRPC communication, be it Notes/Domino or Domino/Domino. The calling party may use any arbitrary port as outgoing port, but always calls the Domino server on port 1352.

/Peter

5

Subject: RE: Domino decides ports on its own

Hi,

I should have also added this will be the 10th additional server - all others are working fine so the firewall at the target network is setup fine.

I am using ServerName/Domain and xxx.xxx.xxx.xxx for the address in the additional server setup. The target server has a connection document for this additional server with the correct ip for the new additional server.

I’ve seen a few posts on this subject however no replies to them as to how they were fixed.