Darrell Posted July 18, 2017 Share Posted July 18, 2017 How do you enable network discovery to search across all your VLANs (192.168.1.x, 192.168.10.x, 192.168.20.x excetera)? Link to comment Share on other sites More sharing options...
Administrators Paul Posted July 18, 2017 Administrators Share Posted July 18, 2017 Hi Darrell, We scan all the local (and public if configured) networks that are assigned to your NICs. We take each IP address and subnet mask to calculate which networks we need to scan. If you provide access to other networks via static routes these networks will not be included in your network discovery. -Paul Link to comment Share on other sites More sharing options...
Darrell Posted July 19, 2017 Author Share Posted July 19, 2017 As a NFR I think it would be better to permit identifying the ip ranges that are static routes that you wish to scan. Permit entering something like: 192.168.1.1-254, 192.168.10.1-254, 192.168.20.1-254 and then off the discovery goes across your defined VLANs. Link to comment Share on other sites More sharing options...
Staff Chris Posted July 20, 2017 Staff Share Posted July 20, 2017 Hi Darrell, Thank you for your suggestion, we will consider the possibility to introduce this option into the future, but meanwhile, in order to scan other subnets, you will need to change the subnet mask on the system which is marked as a probe. Link to comment Share on other sites More sharing options...
Administrators Paul Posted July 20, 2017 Administrators Share Posted July 20, 2017 I'd also like to add that you either change the subnet of a NIC as @Chris pointed out to include the other networks or you can simply add additional IP addresses in the other networks on the same NIC just for the duration of the agent deployment procedure. We will consider adding support for manually inputting which networks to scan. -Paul Link to comment Share on other sites More sharing options...
Haddi Posted August 20, 2018 Share Posted August 20, 2018 Hi Paul, I would like to second the suggestion for being able to manually request an IP range to be scanned. I have quite a few clients where i would like to be able to do a probe from their domain controller that is hosted off site and on a tottally different network than the on site router (f.x. router network is 192.168.1.x and DC is on 10.100.100.1) I have tried adding a 192.168.1.x IP to the NIC before running the probe but it doesn't work. P.S. The on premise network is completely accessible from the DC. B.R. Haddi Link to comment Share on other sites More sharing options...
MichaelS Posted August 21, 2018 Share Posted August 21, 2018 Hello Haddi, Noted, I'm going to forward your request to for further evaluation. Link to comment Share on other sites More sharing options...
philipcyr Posted March 12, 2019 Share Posted March 12, 2019 Any update on this feature? This is something Labtech offered 5+ years ago on their RMM. Comissha 1 Link to comment Share on other sites More sharing options...
Continu IT Solutions Posted June 23, 2020 Share Posted June 23, 2020 I would also like this ability. We have 18 locations all connected via IPSec to a main hub where the domain controllers are. It would be great if the domain controller could probe all the subnets. Link to comment Share on other sites More sharing options...
rwgs Posted September 5, 2020 Share Posted September 5, 2020 Yep I also need this feature... and it was first requested 3 years ago... Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now