You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
configure a "bind to" option in either [/settings/WEB/server] or [/settings/default] on a server with multiple IP addresses
restart the service
PLEASE PROVIDE COMMAND HERE
use netstat to see the port listening (or the ressource monitor), exemple with port 8443
netstat -an |findstr 8443
TCP 0.0.0.0:8443 0.0.0.0:0 LISTENING
0.0.0.0 means any IP addresses
Expected Behavior
the ip should be bound for both NRPE and WEB, only NRPE is boud
for comparison, with nrpe on 5666
netstat -an |findstr 5666
TCP 192.168.13.4:5666 0.0.0.0:0 LISTENING
this works fine
Actual Behavior
see command step, the IP is not bound, and the web server listen on any IP addresses.
Details
NSClient++ version: 0.5.2
OS and Version: Windows Server 2016
Checking from: Centreon
Checking with: anything
Additional Details
This issue is blocking only on Direct Access Windows servers. when binding on the internal IP, the firewall rule let things pass, but when binding on "any" the firewall blocks. and the fw is mandatory for direct access.
the problem is really a firewalling issue, but when the binding works for nrpe, the port is open and accessible.
NSClient++ log:
empty log
The text was updated successfully, but these errors were encountered:
krysstof
changed the title
WebServer is bound to IP Address configuered in the "bind to" setting
WebServer is not bound to IP Address configuered in the "bind to" setting
Mar 17, 2020
as a comment : Don't use port from 6000-47000 on a direct access server, this is not allowed.
but the non binding is still an issue
krysstof
changed the title
WebServer is not bound to IP Address configuered in the "bind to" setting
WebServer is not bound to IP Address configured in the "bind to" setting
Mar 17, 2020
Issue and Steps to Reproduce
configure a "bind to" option in either [/settings/WEB/server] or [/settings/default] on a server with multiple IP addresses
restart the service
use netstat to see the port listening (or the ressource monitor), exemple with port 8443
netstat -an |findstr 8443
TCP 0.0.0.0:8443 0.0.0.0:0 LISTENING
0.0.0.0 means any IP addresses
Expected Behavior
the ip should be bound for both NRPE and WEB, only NRPE is boud
for comparison, with nrpe on 5666
netstat -an |findstr 5666
TCP 192.168.13.4:5666 0.0.0.0:0 LISTENING
this works fine
Actual Behavior
see command step, the IP is not bound, and the web server listen on any IP addresses.
Details
Additional Details
This issue is blocking only on Direct Access Windows servers. when binding on the internal IP, the firewall rule let things pass, but when binding on "any" the firewall blocks. and the fw is mandatory for direct access.
the problem is really a firewalling issue, but when the binding works for nrpe, the port is open and accessible.
NSClient++ log:
The text was updated successfully, but these errors were encountered: