aletes schrieb:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20 | alex@alex-MS-7369:~$ sudo nmap -sS 174.121.162.194 -p80
Starting Nmap 5.21 ( http://nmap.org ) at 2013-05-12 14:17 CEST
Note: Host seems down. If it is really up, but blocking our ping probes, try -PN
Nmap done: 1 IP address (0 hosts up) scanned in 3.06 seconds
alex@alex-MS-7369:~$ sudo traceroute -n4T -p 80 174.121.162.194
traceroute to 174.121.162.194 (174.121.162.194), 30 hops max, 60 byte packets
1 192.168.2.1 0.580 ms 0.726 ms 0.995 ms
2 217.0.118.173 42.848 ms 45.034 ms 48.457 ms
3 87.186.249.6 52.172 ms 56.061 ms 57.374 ms
4 62.154.47.66 66.104 ms 69.547 ms 71.495 ms
5 194.25.210.46 75.697 ms 78.648 ms 81.892 ms
6 * * *
7 4.69.200.165 183.774 ms 4.69.200.161 150.684 ms 4.69.200.173 151.800 ms
8 4.69.143.205 150.964 ms 4.69.143.201 150.157 ms 149.055 ms
9 4.69.143.58 151.172 ms 4.69.143.66 144.668 ms 144.156 ms
10 4.69.143.70 144.895 ms 143.617 ms 4.69.143.74 143.328 ms
11 4.69.137.74 143.048 ms 141.348 ms 4.69.137.66 140.903 ms
12 * * *
13 * * *
|
Das hat was mit dem Routing, das dein ISP verwendet zu tun. Bei mir funktioniert es:
:~$ sudo nmap -sS 174.121.162.194 -p80
Starting Nmap 5.21 ( http://nmap.org ) at 2013-05-12 14:24 CEST
Nmap scan report for r2-dallas.webserversystems.com (174.121.162.194)
Host is up (0.66s latency).
PORT STATE SERVICE
80/tcp open http
Nmap done: 1 IP address (1 host up) scanned in 4.66 seconds