Hi,
My IT service provider is a Kaseya user. They want to deploy KNM into our network and asked me to allow a bidirectional rule on the firewall for TCP 4242. This rule is in play and they asked me for the public IP for our MPLS network firewall. I sent them this IP and they say they cannot telnet to that IP on port 4242.
4242 as I understand is open bidirectionally to their KServer only. I can telnet out to their KServer on 4242 but they tell me they cannot telnet inbound to our FW public IP on 4242.
Question...
Surely they should not point \ scan the public facing IP of the FW as essentially no networks exist in that range...the public facing IP of the MPLS firewall is a public IP that the FW NATs traffic through to our internal private ranges of which there are many in the 10.200.x.x range.
What should they point their KNM monitor at?
Is it not a better idea to deploy an agent inside the MPLS to scan the internal ranges and report the discovery data back to their cloud based KServer?
Thanks in advance...
durrie.