NSClient++ Help (#1) - Netmask required? Ini file save permission. Win7 firewall notes. [SOLVED] (#611) - Message List
With 0.3.8 and trying to access by check_nt, the logs showed my access as unauthorized when I had the host IP entered without a netmask. Replacing that with "127.0.0.1/32,192.168.1.0/24" (the latter specific to this case) fixed the access problem. Having it as just 192.168.1.8 (correct in this case) didn't work. Haven't tested if 192.168.1.8/32 will work, or if the 127.0.0.1/32 is required.
The other gotcha's were even being able to edit the ini file. I'm not at all a Windows guy. This helped:
And then getting the Windows 7 firewall right. The Profile it was applying the NEClient++ rules to was Public, which wasn't the one being used for the LAN. I extended that to all in the Advanced tab by checking the others. Just setting it to Private should also do it. And I dumped the UDP rule, and specified the specific port under Protocols and Ports as 12489. Didn't check if all these steps were required, since I did them in the other order. But it works now. Would need a different port for a different access method, of course.
Fixed in next nightly (out in secs...
allowed_hosts=192.168.0.1/24 ,192.168.1.1, www.ibm.com/32 ,www.google.com/0, www.nsclient.org/16, www.nsclient.com/4 Added: 192.168.0.1 with mask 255.255.255.0 from 192.168.0.1/24 Added: 192.168.1.1 with mask 255.255.255.255 from 192.168.1.1 Added: 18.104.22.168 with mask 255.255.255.255 from www.ibm.com/32 Added: 22.214.171.124 with mask 255.255.255.255 from www.google.com/0 Added: 126.96.36.199 with mask 255.255.0.0 from www.nsclient.org/16 Added: 188.8.131.52 with mask 240.0.0.0 from www.nsclient.com/4
Michael Medinmickem07/28/10 12:30:35 (3 years ago)