Possible client issues?

[slansing]

Well, if you still cannot access a port that is completely unrelated to Nagios/NSClient++ that is out of the realm of what we can do for support on our end unfortunately, though we do try to help resolve certain system related issues in some cases. I can say though this is very strange, if it is not something you can easily identify on the system as far as where the blockage is coming from it's tough to point in the direction of where to sniff. I had high hopes it was something related to NSClient but checking a unrelated port pushes that out of the realm of possibilities, at least at this point.

[mobiledataforce]

Checking an unrelated port has no issues.. I can telnet to other ports.

[slansing]

Okay, that's what we needed to know. I'm going to poke around on the NSClient++ bug list/forums, I would do the same on your end too since this could be something that has popped up there before. Are you still seeing the port related error that we had thought was a duplicate NSClient instance running?

[mobiledataforce]

Thank you. I'll let you know if I find anything. Yes, I sill see the socket did not start properly when running the client test.

[mobiledataforce]

I was able to get this host monitoring! I uninstalled the client, rebooted the server, set the selective startup to not load startup items, rebooted the server, installed the client, rebooted the server, set back to normal startup, and rebooted the server. This makes me think there was a conflict with starting the service, although everything looked fine visually; maybe something behind the scenes wasn't fully starting. I have no idea what the conflict could have been, this server is identical to many others I have had no issues with.

Thanks a bunch for your assistance, it's much appreciated.

[slansing]

Holy smokes, I've never seen that happen in the last year.. strange, let us know if it recurs though it should not.. something must have goofed the first time it was configured.