Blog

Answer for yesterday and new issue


Tags :


        I am attempting to make sure I follow up on things I post and show some of the answers more often.  Well because I got some heat posting good topics and having solutions but not always how.  Just trying to make the blog even more enticing.
      Yesterday I mentioned an Adminp issue we were troubleshooting.  This one was quite simple in the end.  For some reason the user name was not being changed in a TeamRoom after a recertification was done.  Well come to find out, all the AdminP settings were left at the default.  For some reason this database was waiting until the default Sun at 12:00am to process the request.  Basically treating it as  a delayed request.  So after forcing everything to process in Adminp and checking, all done.  Needless to say we have modified their default settings.

      The new issue for today brings me to one of the most feared pieces of Domino server tasks.  The ICM !!!!  (I can hear the screams of horror and many of you running away from the keyboard in droves thinking of the Internet Cluster Manager).  Here is the scenario...........
      The server was 5.011 and behind a firewall.  We moved it to a new firewall and went ahead and upgraded it to 6.01 just for grins.  OK, we weren't grinning for long.  It stopped working entirely.  First was a port conflict warning that never existed before.  No configurations were changed at all except the Domino upgrade.  So I cheated so far and disabled the actual TCPIP port after Dave F and I banged our heads on the desk forever.

sorry, lunchtime real quick, I will continue on shortly.....

OK, back from lunch, let's continue.

So at the last step we disabled the TCPIP port and restarted the ICMPORT.  Wham, I am running an unsupported Domino HTTP stack for the ICM through a wonderful hack.  We found doing show port commands that the primary IP address was binding to port 80 before we stopped the port and the secondary IP assigned to the ICM was only seeing 1352 as a bind.  So after stopping the TCP port, we were able to pick up 80 on the ICM.