NotesPing as a server setup tool?
Tags :Domino NotesPing
Another interesting bout with unknown causes of server setup failures on an additional Domino server. We were setting up a hosted server, that was to get the necessary data through a private connection with an address supplied by the IT team at said company. We could hit that IP address over port 1352 successfully, so all was good there. However, the server setup would always stop at 20%, which normally means that it cannot connect. Yet even a simple telnet showed that it connected fine. So as we were about to cheat and have them zip and send names.nsf and some other stuff to set the server up locally and then let replication take over, NotesPing was quickly tossed on the server to some interesting results.:
Determining path to server XXX.XX.XX.94
Available Ports: TCPIP
Checking normal priority connection documents only...
Allowing wild card connection documents...
Enabling name service requests and probes...
Checking for XXX.XX.XX..94 on TCPIP using address 'XXX.XX>XX.94'
Connected to the wrong server SaidServer2/SaidDomain using address XXX.XX.XX.94
Connected to the wrong server SaidServer2/SaidDomain using address XXX.XX.XX.94
Unable to connect to XXX.XX.XX.94 on TCPIP (Connection denied. The server you connected to has a different name from the one requested.)
Checking low and normal priority connection documents...
No default passthru server defined
So NotesPing showed us that the server they gave us as an IP address and name, was not the right one for one of the two variables for the setup. Correcting either the IP address for the SaidServer or the server name for the IP address solved the issue.
blog comments powered by Disqus
On Monday, March 24th, 2008 by Chris Miller
