3306/tcp 80/tcp 24699/tcp 7000/tcp 6900/tcp 21/tcp 22/tcp 60000-65535/tcp
./tcping64.exe 104.129.17.203
Probing 104.129.17.203:80/tcp - No response - time=2006.336ms
Probing 104.129.17.203:80/tcp - No response - time=2000.803ms
Probing 104.129.17.203:80/tcp - No response - time=2000.850ms
Probing 104.129.17.203:80/tcp - No response - time=2000.840ms
Ping statistics for 104.129.17.203:80
4 probes sent.
0 successful, 4 failed.
Was unable to connect, cannot provide trip statistics.
1
visonnn 2018-07-24 09:06:47 +08:00 via Android
SSH 时抓包看看就知道发生了什么…
|
2
jptx 2018-07-24 09:22:05 +08:00
废了,大约从 5 月 21 日开始,屏蔽的几轮都是能 ping 通但啥端口都访问不了
|
3
sarices 2018-07-24 09:24:13 +08:00
服务商防火墙不开放端口你也连不进去啊,应该和服务商沟通一下
|
4
runhua 2018-07-24 09:34:00 +08:00 via Android
有些服务商会提供安全组这种东西,也是一种防火墙,你看看是不是那里没放行你的端口
|
5
doubleflower 2018-07-24 09:51:30 +08:00
现在还有人不知道现在墙的新技能 tcp 阻断
|
6
coolloves 2018-07-24 10:42:12 +08:00
Nmap scan report for 104.129.17.203.static.quadranet.com (104.129.17.203)
Host is up (0.27s latency). All 1000 scanned ports on 104.129.17.203.static.quadranet.com (104.129.17.203) are filtered Nmap done: 1 IP address (1 host up) scanned in 15.32 seconds 估计有安全组或者机器 iptables 做了限制,指定 ip 可以访问. |
7
sodora 2018-07-24 14:19:08 +08:00
现在检测有没有被 Q 应该用 tcping,而不是用 ping。
社会在发展,那个东西的技术也在进步,你的那些过时的知识需要更新了。 |
8
metrxqin 2018-07-24 15:38:12 +08:00
ping 不能说明什么问题,谁都可以返回响应报文。
|
9
akira 2018-07-24 15:44:02 +08:00
拿台海外的服务器去连
|
10
ThirdFlame 2018-07-24 15:45:41 +08:00
被 Q 的新的表现形式, ping 通,tcping 端口 不通。
|
11
opengps 2018-07-24 15:54:38 +08:00
端口能从外部扫描到开通,是一系列条件的同时具备:
1,硬件防火墙,硬件路由器,安全组等主机外部工具放行端口 2,软件防火墙类主机内部防护需要放行端口 3,主机启动了监听对一个端口的服务 |
12
Vimax OP @sodora ./tcping64.exe 104.129.17.203
Probing 104.129.17.203:80/tcp - No response - time=2006.336ms Probing 104.129.17.203:80/tcp - No response - time=2000.803ms Probing 104.129.17.203:80/tcp - No response - time=2000.850ms Probing 104.129.17.203:80/tcp - No response - time=2000.840ms Ping statistics for 104.129.17.203:80 4 probes sent. 0 successful, 4 failed. Was unable to connect, cannot provide trip statistics. 知道真相了。 |
13
Vimax OP @metrxqin ./tcping64.exe 104.129.17.203
Probing 104.129.17.203:80/tcp - No response - time=2006.336ms Probing 104.129.17.203:80/tcp - No response - time=2000.803ms Probing 104.129.17.203:80/tcp - No response - time=2000.850ms Probing 104.129.17.203:80/tcp - No response - time=2000.840ms Ping statistics for 104.129.17.203:80 4 probes sent. 0 successful, 4 failed. Was unable to connect, cannot provide trip statistics. 知道真相了。 |
14
Vimax OP @ThirdFlame 你说的对。 ./tcping64.exe 104.129.17.203
Probing 104.129.17.203:80/tcp - No response - time=2006.336ms Probing 104.129.17.203:80/tcp - No response - time=2000.803ms Probing 104.129.17.203:80/tcp - No response - time=2000.850ms Probing 104.129.17.203:80/tcp - No response - time=2000.840ms Ping statistics for 104.129.17.203:80 4 probes sent. 0 successful, 4 failed. Was unable to connect, cannot provide trip statistics. 知道真相了。 |
17
smiletouch3g 2018-07-24 17:18:21 +08:00 via iPad
改 ssh 端口试试呢
|
18
wycmxg 2018-08-12 03:01:04 +08:00 via Android
tcp 端口全部被阻断了
|
19
Rap 2018-09-07 12:26:07 +08:00 via iPhone
被墙了,用这个办法试试
https://www.vultrcn.com/4.html |