Network scan failure

Hi,
What RDM version do you use? Just make sure to use RDM 10.1

Regards

After eleven years, I have managed to achieve the same effect. hahaha (:
I can see the sessions on the firewall - the first IP gets scanned, certain standard ports, ICMP... After that, nothing else happens (no other IP from subnet is being checked).

Am I overlooking something?

Hello.

Thanks for your message!

I tried to reproduce the network scan behavior you described, but I haven’t been able to replicate it on my side. To help me investigate further, could you let me know:

• Which version of Remote Desktop Manager you’re currently using
• Which data source you’re connected to (Devolutions Server, SQLite, XML, etc.)
• can you let me know a bit more about the setup on your end? (firewall)

And just to check… you're not still on version 10.1, right? 😄

Once I have this info, I’ll be able to dive deeper into the issue.

Thanks, and looking forward to your reply!

Best regards,

Hello,

Following up on my previous post, would it be possible to clarify exactly where the network scan begins?

Is it initiated when creating an RDP session, or via File → Import → Network Scan?

Best regards,

:) :) Hi Carl,
I'm using the latest release - 2025.3. Try with local data source and business hub. Initiated via Tools > Network Scan or Import > Network Scan.

Scan my own subnet without a problem actually. My client(s) subnet over IPsec ends with behavior above.
Test with subnet 192.168.xx.15 - 50 scans 192.168.xx.16 (ping, https, rdp) and stops... :D (no new sessions on fortigate)

VPN on fortigate, so I checked for security scans and any restrictions on firewall policies, not really discover something.
If I use a different IP scanner, works normal, complete subnet scan with most common ports.

How RDM scanner works?

Hello,

I was able to partially reproduce the issue and have created a QA investigation to determine whether the behavior I observed is related to the issue you reported.

I will keep you updated on any developments from our side.

Best regards,

Thank you Carl.
Tricks from your side? How can I cleverly outsmart the problem? ;) ;)
I know that it must have worked in the past. My colleague scanned certain customer networks a year or two ago. It doesn't work with the current version in the same infrastructure.

BR
Philipp

Hello,

Unfortunately, I haven’t found a workaround yet. I was able to reproduce a similar issue, but I wasn’t certain if it matched your case. For this reason, I’ve opened a QA investigation.

I’ll keep you updated if we discover a workaround or make any progress on this case.

Best regards,

Hello,

I hope you’re doing well.

Our team is continuing to investigate the network scan behaviour you reported when scanning over your IPsec VPN. While we are working internally on this, we have two additional questions that will significantly help us move forward.

Could you please provide the following when you have a moment:

1. A short screen recording showing the network scan behaviour with the VPN enabled and with the VPN disabled. We send you an email where you can upload the file
2. From a PowerShell window, could you run the command arp -a both with and without the VPN active and let us know if the output differs?

This information will help us determine whether the issue is related to ARP behaviour, routing, or something specific to how RDM interacts with your VPN tunnel.

Thank you very much for your collaboration, and I’ll keep you updated as soon as we have more findings on our side.

Best regards,