Rather embarrassed but I have discovered the root of my problem and want to share it just on the off chance someone else may experience this in the future. Using a site called uptimerobot I found that periodically it said the port was closed and when I looked it appeared to still be open. Looking more closely I saw that my Noip DDNS address had been updated with a new IP that didn’t match my actual IP so that when the DNS name was used to look for the open port it showed up as closed. I corrected the Noip entry and everything was OK for awhile. Again a few hours later uptimerobot showed a problem and again the Noip IP address had been updated incorrectly. I reasoned that there must be another Noip update client installed somewhere with my credentials that is periodically updating my DDNS entry with the wrong IP address. I changed my Noip logon password online and in my update client and haven’t had the problem since and the Node now shows online all the time. I have no idea where it is located or how the rogue Noip update client got ahold of my logon credentials but somehow it did and now it can no longer make any bogus changes to my DDNS entry.
Thanks for all of your quick and valuable responses since I made lots of useful changes to my Node that may have eventually given me heartache.
3 Likes