I created a little tool to discover Windows machines on a local network with RDP/Remote Desktop enabled. This tool will be integrated in the next RemoteDesktopManager version.
Just run the tool. Let it discover all available machines, uncheck the ones you don’t want. Play with the RDP options available and hit save. Provide an location on disk and the tool will create standard RDP (mstsc compatible) files with the extra options used by RemoteDesktopManager.
If you want to use the files in RDM just select them, start RDM and drop the files on it.
Downloads: RDPDiscovery Exe, RDPDiscovery Source
For the curieus: I used the .NET Ping class to find-out if a machine is running and then try to open an socket on port 3389 to see if RDP is running. Without the use of the Ping class, you will only discover some hosts as Windows (from XP SP2) has some “security” feature build-in to block portscans.
Credits go to Ami Bar for the SmartThreadPool code I used.
Hi, i have a quite strange subnetmask, and the programm scans a wrong subnet (it scans the full class B net instead of the given 2 Class C nets)
the subnet is 255.255.254.0 and my host ip is 172.20.31.221, which means a net 172.20.30.0-172.20.31.255 but RDP Discovery starts scanning at 172.20.0.0
Please correct the problem !
TNX
apos
apos,
I have added this to my TO-DO list. I will (try) to fix the netmask issue when my schedule allows it. Note that it will not be fixed in RDP Discovery but in RemoteDesktopManager (if you don’t want to use that tool, just do a discovery in it once and then export the connection files).