Issues with import network scan

Published 2 years ago

version 2024.1.17.0 64-bit windows
Issues:
1) 30+ mins and can't scan 20 IP's? Angry IP can do it in 2 seconds. How can I limit the ports to scan? the OUTDATED online docs has a "ping before scan" that is no longer in the program. Also missing from online docs is the ZeroConf scan now in network scan? Nothing about it anywhere.

2) After I do get some entries SSH, the default template I have modified for SSH is NOT applied to the new imported ssh entries, making them worthless. If I manually add an SSH session, the default template is applied. No, I don't want to go batch edit entries.

Thanks!

Import with Network scan - Devolutions Documentation

All Comments (3)

Paul Dumais

Published 2 years ago

Hello Doug,

Can you send me a video of the results of the network scan versus Angry IP, that would help me diagnose where the issue is and how we can improve it.

Right now we scan for certain known ports that we can manage with RDM like the 3389, 389, 5985, 23, 22 etc. We could add the ability to scan a range of ports, but my concern is often if we scan too many ports on a single host it will trigger anti virus software and block RDM.

As for the documentation, I will let our documentation team know that it must be updated.

For the default template, I will look into this issue and fix it asap.

Thanks,
Paul Dumais

James Lafleur

Published 2 years ago

Hello Doug,

I just wanted to inform you that an internal documentation ticket has been opened to update this article https://docs.devolutions.net/rdm/commands/file/import/network-scan/.

Best regards,

James Lafleur

Paul Dumais

Published 2 years ago

Hello Doug,

We have resolved the import from network scan Template issue, it will be in the next build of RDM.

I'm also comparing our network scan to Angry IP, if you can send me a video of the results you are seeing that would be helpful. Does RDM show the same network IP range as Angry IP is showing?

Thanks,

Paul Dumais