When we use Remote Server Setup to create a secondary server in a Domino domain, the process hangs at about 20% if we are using public IP addresses. We don’t get an error message–the setup simply crashes (and we need to use Task Manager to kill the Remote Server application).
But the problem doesn’t happen if we do the process with all three boxes (the primary server, the remote server being set up, and the client running Remote Server Setup)on the same LAN. It even works well with the primary server being accessed via a VPN tunnel over the trusted interface.
We’ve tried making sure that port 8585 is open on both of the servers but this doesn’t seem to solve the problem. Also, the problem doesn’t seem to be communication between the client running Remote Server Setup and the remote server being setup, since we can ping and and have no trouble with the step to select the server.id file to be used.
Two sub-questions that come to mind:
Is there an undocumented requirment that the two servers be on the same LAN to run Remote Server Setup?
How does communication go once the setup starts?
a) client tells new secondary server to contact primary server and get info
b) client tells primary server to contact new secondary server and give it the info.
Thanks.