Not Able to ping to TP Link Modem

[Masood]

Hi Team,

I am not able to ping TP Link Router Archer VR1600v from Command prompt. Not sure if TP Link router is blocking ping to 192.168.1.1 (or its WAN address)

My TP link is running below Firmware

Firmware Version:0.1.0 0.9.1 v5006.0 Build 220518 Rel.32480n Hardware Version:Archer VR1600v v2.0 00000000

Ping to WAN IP address Failing 

C:\Users\P630872>ping 124.148.72.107

Pinging 124.148.72.107 with 32 bytes of data:
Reply from 124.148.72.107: Destination host unreachable.

Ping statistics for 124.148.72.107:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Control-C
^C
C:\Users\P630872>

Ping to TP Link  LAN Default Gateway Failing 

C:\Users\P630872>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Control-C
^C

Ping to Google DNS Working

C:\Users\P630872>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=10ms TTL=119
Reply from 8.8.8.8: bytes=32 time=10ms TTL=119
Reply from 8.8.8.8: bytes=32 time=10ms TTL=119

Ping statistics for 8.8.8.8:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 10ms, Average = 10ms
Control-C
^C

Traceroute to Goolge and Google DNS

C:\Users\P630872>tracert google.com

Tracing route to google.com [172.217.167.78]
over a maximum of 30 hops:

1 * * * Request timed out.
2 10 ms 10 ms 9 ms 10.20.22.125
3 11 ms 11 ms 11 ms 203.29.134-61.tpgi.com.au [203.29.134.61]
4 12 ms 11 ms 11 ms 209.85.149.84
5 11 ms 12 ms 11 ms 72.14.239.249
6 12 ms 10 ms 14 ms 209.85.247.133
7 10 ms 10 ms 10 ms syd15s06-in-f14.1e100.net [172.217.167.78]

Trace complete.

C:\Users\P630872>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms * * ARCHER_VR1600V [192.168.1.1]
2 9 ms 10 ms 10 ms 10.20.22.125
3 10 ms 10 ms 11 ms 203.29.134-61.tpgi.com.au [203.29.134.61]
4 11 ms 17 ms 12 ms 209.85.149.84
5 11 ms 13 ms 12 ms 72.14.239.13
6 11 ms 11 ms 10 ms 142.251.64.179
7 12 ms 11 ms 10 ms dns.google [8.8.8.8]

Trace complete.

[david64]

Hi @Masood . You need to do this from your computer running standard Windows, not any virtualisation software, and connected directly to Archer.

In command window:

ipconfig        (see that computer has address 192.168.1.x, and default gateway is 192.168.1.1)

telnet 192.168.1.1 80

Blank command window indicates connection to router's web server.

If it times out, the web server has crashed. Turn the Archer off and on. It will get a new WAN ip address.

[Masood]

Hi David,

Accessing Archer via web is not an issue. I was trying to test standard ICMP (Ping connectivity) test. I used to ping my default gateway is 192.168.1.1 from my computer running standard Windows, not any virtualisation software and it always worked. Did TPG blocked ping to Default Gateway or its Public Facing IP Address. 

[david64]

@Masood . In Archer admin, go to Advanced/System Tools/Administration. Check ICMP Ping selection.

Is Local ticked? Also, decide if you want router to respond to external ping.

[Masood]

Afternoon David, 

Under ICMP Ping: both local and remote are ticked. I however was still not able to ping. 

So I unchecked both save the config and checked both again and save config again. I then Rebooted Archer TP Link. Now I am able to ping 192.168.1.1 but still cannot ping Public Facing IP of TP Link (WAN) address. 

Thanks 

[david64]

@Masood . My VR1600 has same firmware build as yours. I can ping my WAN ip address; same response time as router's LAN address. I can also ping some other random ip addresses on same subnet as me (other TPG users).

Have you checked your router's current WAN ip address?

[Masood]

Hi David, 

I have checked again, Connection Type is PPPoE and IP address is lised (WAN IP) but I cannot ping that address from CMD. I have attached screenshot (though removed IP Address)

[david64]

@Masood . Only other thing is factory reset VR1600. Enter PPPoE, username and password (minimum to get internet connected) and try ping again. New WAN ip address again.

If it fails, what is the error message?

If it fails, it's either a bad firmware download, or faulty memory in VR1600.

Any chance you can borrow another router?