Nmap find open TCP/IP ports for a target that is blocking ping

nmap -sT -PN -vv <target ip>
Change the IP address from 127.0.0.1 to the target machines ip address. Even if the target has ICMP (ping) blocked, it will show you what ports are open on the target. Very handy for situations where you know the target is up and online but wont respond to pings.
Sample Output
Starting Nmap 5.00 ( http://nmap.org ) at 2011-07-21 19:21 PDT
NSE: Loaded 0 scripts for scanning.
Initiating Connect Scan at 19:21
Scanning localhost (127.0.0.1) [1000 ports]
Discovered open port 111/tcp on 127.0.0.1
Discovered open port 993/tcp on 127.0.0.1
Discovered open port 25/tcp on 127.0.0.1
Discovered open port 995/tcp on 127.0.0.1
Discovered open port 113/tcp on 127.0.0.1
Discovered open port 143/tcp on 127.0.0.1
Discovered open port 21/tcp on 127.0.0.1
Discovered open port 110/tcp on 127.0.0.1
Discovered open port 22/tcp on 127.0.0.1
Discovered open port 1984/tcp on 127.0.0.1
Discovered open port 465/tcp on 127.0.0.1
Discovered open port 5432/tcp on 127.0.0.1
Discovered open port 3333/tcp on 127.0.0.1
Discovered open port 10025/tcp on 127.0.0.1
Discovered open port 8333/tcp on 127.0.0.1
Discovered open port 10024/tcp on 127.0.0.1
Discovered open port 2401/tcp on 127.0.0.1
Completed Connect Scan at 19:21, 0.14s elapsed (1000 total ports)
Host localhost (127.0.0.1) is up (0.00092s latency).
Scanned at 2011-07-21 19:21:55 PDT for 0s
Interesting ports on localhost (127.0.0.1):
Not shown: 983 closed ports
PORT      STATE SERVICE
21/tcp    open  ftp
22/tcp    open  ssh
25/tcp    open  smtp
110/tcp   open  pop3
111/tcp   open  rpcbind
113/tcp   open  auth
143/tcp   open  imap
465/tcp   open  smtps
993/tcp   open  imaps
995/tcp   open  pop3s
1984/tcp  open  bigbrother
2401/tcp  open  cvspserver
3333/tcp  open  dec-notes
5432/tcp  open  postgresql
8333/tcp  open  unknown
10024/tcp open  unknown
10025/tcp open  unknown

Read data files from: /usr/share/nmap
Nmap done: 1 IP address (1 host up) scanned in 0.23 seconds

0
By: Richie086
2011-07-22 02:37:19

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: