Friday, November 7, 2014

SnTT - In Which Port Settings Don't Quite Work

Been a long time since I wrote a Show n Tell Thursday so let's get on with it.

Building an IBM Domino cluster is not as difficult as it was years ago and I was done with the basic parts and wanted to test the fail over.

I figured easiest way to do this was to enter at a server console "stop port tcpip" while connected via rdp to the server.

I tested mail clients could fall over to the 2nd server and mail routed. Great.

Back to the server and server console and tell it to "start port tcpip".

I didn't think much about it and since there were some server updates to add to the box, I decided to shut it down after the updates were done.

It came back up and was running and I was working on another server in the domain when the client let me know no one could connect to the server. Odd, I was there and it "looked" ok. On closer inspection, it was not ok.

Errors that said databases could not be found, no route found, no network could be found, trace connections and some other fine error messages that mean nothing to the average person.

After poking around a bit, I figured the notes.ini needs to be edited. I checked with Rob Kirkland, of this book fame on Domino System Administration, and followed it to solve the problem.

I found the TCPIP port listed under disabled ports. Deleted it form there.
Found TCPIP=TCP,0,15,0,,45088 was missing which is for compression and encryption (see below).
Also missing was Ports=TCPIP

After putting it all back together, rebooted and all is good again. Still not sure why the commands failed and did not help this 8.5.3FixPack6 server but at least someone else out there will not have to waste an hour or 2 tying to figure it out.
Selection NOTES.INI parameter
          Nothing TCPIP=TCP,0,15,0,,12288,
Compression only TCPIP=TCP,0,15,0,,12320,
Encryption only TCPIP=TCP,0,15,0,,45056,
Both TCPIP=TCP,0,15,0,,45088,

No comments:

Post a Comment