I am looking for what ports and protocols are utilized during an initial Lotus Notes setup. I know that Notes uses port 1352 for communication but what exactly happens during the setup process? It’s clearly different for initial setup than it is for after it’s been completed.
Something occurred on the Domino Server (I don’t know if it was firewall, software, etc) within the last month that will not allow initial setups but if they have a names.nsf and a notes.ini file ported over to the new computer then there is no actual setup process and connection to the Domino server works fine.
If I rename the names.nsf to oldnames.nsf and make a copy of the ini file somewhere else and edit the ini file in the lotus/notes directory to contain the top 4 lines to rerun setup then it doesn’t work. By not working I mean I will get a Lotus Notes Client Configuration dialog box requesting Domino Server Network information such as the Domino server name, specific network information to help locate the server and the server address (ip address or hostname). Even if I provide that information I then get a dialog box saying that it is unable to find path to server. It also says I can use trace from the client to the server but I can’t because I can’t get the File Menu bar since the setup is not complete.
So I am trying to determine what the setup is looking for exactly to make the setup work so maybe I can narrow it down from a Notes admin side since I don’t know what the server side people did.
Subject: Detailed process including ports and protocols used for setup
AFAIK it uses port 1352.
You stated: ‘Even if I provide that information I then get a dialog box saying that it is unable to find path to server.’
What happens if you put the server’s IP address in place of the Server Name? Will setup work then?
This SOUNDS like a case of the DNS entry for the server gone missing.
If you open up a DOS window, and ping the server name, can the user’s PC resolve the name?
Once the client is set up, connection docs are created/updated. So, in your example, you could taking a working configuration and change it to a configuration that you could no longer set up, presumably by deleting the connection docs.
Take a look at the connection docs in your oldnames.nsf for the server, and see how they’re set up.
Subject: RE: Detailed process including ports and protocols used for setup
I can ping the host name from my desktop.
For grins, I did try playing around with the ip address in locations even if it wanted a server name. I even tried the host name but none of that worked either. There are no connection documents in the names.nsf.
This just makes absolutely no sense if it uses port 1352 only during the initial setup unless it uses a specific protocol that they blocked but the firewall isn’t showing anything as being blocked. The firewall person sent me a screen shot of the log file and instead of application it says incomplete but it is port 1352 and it was doing setup so I don’t know what would be causing this unless it is a specific protocol it’s trying to utilize.
Subject: RE: Detailed process including ports and protocols used for setup
Wow, it’s been so long I forgot about that utility. However, it does connect using NRCP from my desktop to the server using both the hostname and ip address.