$ nmap -v -sn 10.77.114.1-255 -p 3389 Starting Nmap 6.25 ( http://nmap.org ) at 2014-01-03 07:47 EST Failed to resolve given hostname/IP: sn. Note that you can't use '/mask' AND '1-4,7,100-' style IP ranges. If the machine only has an IPv6 address, add the Nmap -6 flag to scan that. Initiating Ping Scan at 07:47 Scanning 256 hosts [2 ports/host] Completed Ping Scan at 07:47, 8.83s elapsed (256 total hosts) Initiating Parallel DNS resolution of 256 hosts. at 07:47 Completed Parallel DNS resolution of 256 hosts. at 07:47, 0.40s elapsed Nmap scan report for 10.77.114.0 [host down] Nmap scan report for 10.77.114.2 [host down] Nmap scan report for 10.77.114.3 [host down] Discovered open port 3389/tcp on 10.77.114.35 Discovered open port 3389/tcp on 10.77.114.36 Discovered open port 3389/tcp on 10.77.114.148 Discovered open port 3389/tcp on 10.77.114.185 Discovered open port 3389/tcp on 10.77.114.196 Discovered open port 3389/tcp on 10.77.114.150 Discovered open port 3389/tcp on 10.77.114.154 Completed Connect Scan at 07:47, 1.00s elapsed (20 total ports) $
Rants and ravings of a semi-autistic developer who has a hard time remembering idiotic nonsense details. Why remember it, when you know where to find it.
Friday, March 1, 2013
Finding RDP machine after router flushed MAC IP table
They flushed the router tables again... where is my RDP machine....
Zenmap/nmap to the rescue... the only thing you need to know is the actual assigned windows name for your computer... and make sure your have it powered up... waiting for logon..
The nmap command would be something like this for scanning the 0-255 ip addresses on a 10.77.114.x
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment