Buy or Renew
Buy or Renew
NOTICE: You can now engage in the community. Learn about the great new Cisco Umbrella content.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2452
Views
0
Helpful
1
Replies

Android tablet not responding to ping anymore

fabio.fumi
Level 1
Level 1

‎10-17-2011 03:37 AM

How can we explain this?

This is the output of a 'ping' command given from my PC towards my  tablet IP address:

how can we explain this?

This is the output of a 'ping' command given from my PC towards my  tablet IP address:

C:\Users\FFUMI>ping -n 100 192.168.0.100

Pinging 192.168.0.100 with 32 bytes of data:
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
<<  WiFi de-activated and re-activated on tablet >>
Reply from 192.168.0.100: bytes=32 time=2017ms TTL=64
Reply from 192.168.0.100: bytes=32 time=9ms TTL=64
Reply from 192.168.0.100: bytes=32 time=8ms TTL=64
Reply from 192.168.0.100: bytes=32 time=9ms TTL=64
Reply from 192.168.0.100: bytes=32 time=6ms TTL=64
Reply from 192.168.0.100: bytes=32 time=5ms TTL=64
Reply from 192.168.0.100: bytes=32 time=4ms TTL=64
Reply from 192.168.0.100: bytes=32 time=16ms TTL=64
Reply from 192.168.0.100: bytes=32 time=6ms TTL=64
Reply from 192.168.0.100: bytes=32 time=13ms TTL=64
Reply from 192.168.0.100: bytes=32 time=14ms TTL=64
Reply from 192.168.0.100: bytes=32 time=13ms TTL=64
Reply from 192.168.0.100: bytes=32 time=10ms TTL=64
Reply from 192.168.0.100: bytes=32 time=12ms TTL=64
Reply from 192.168.0.100: bytes=32 time=12ms TTL=64
Request timed out.
Reply from 192.168.0.100: bytes=32 time=10ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
<<  WiFi Deactivated and re-activated on tablet >>
Reply from 192.168.0.100: bytes=32 time=31ms TTL=64 
Reply from 192.168.0.100: bytes=32 time=12ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
<<  WiFi Deactivated and re-activated on tablet >>
Reply from 192.168.0.100: bytes=32 time=29ms TTL=64
Reply from 192.168.0.100: bytes=32 time=10ms TTL=64
Reply from 192.168.0.100: bytes=32 time=9ms TTL=64
Reply from 192.168.0.100: bytes=32 time=7ms TTL=64
Reply from 192.168.0.100: bytes=32 time=5ms TTL=64
Reply from 192.168.0.100: bytes=32 time=3ms TTL=64
Reply from 192.168.0.100: bytes=32 time=11ms TTL=64
Reply from 192.168.0.100: bytes=32 time=9ms TTL=64
Reply from 192.168.0.100: bytes=32 time=347ms TTL=64
Reply from 192.168.0.100: bytes=32 time=135ms TTL=64
Reply from 192.168.0.100: bytes=32 time=13ms TTL=64
Reply from 192.168.0.100: bytes=32 time=12ms TTL=64
Reply from 192.168.0.100: bytes=32 time=11ms TTL=64
Reply from 192.168.0.100: bytes=32 time=11ms TTL=64
Reply from 192.168.0.100: bytes=32 time=11ms TTL=64
Reply from 192.168.0.100: bytes=32 time=10ms TTL=64
Reply from 192.168.0.100: bytes=32 time=5ms TTL=64
Reply from 192.168.0.100: bytes=32 time=13ms TTL=64
Reply from 192.168.0.100: bytes=32 time=11ms TTL=64
Reply from 192.168.0.100: bytes=32 time=10ms TTL=64
Reply from 192.168.0.100: bytes=32 time=8ms TTL=64
Reply from 192.168.0.100: bytes=32 time=7ms TTL=64
Reply from 192.168.0.100: bytes=32 time=16ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
...

It looks like the ping service is kept active for just a few seconds  after I reactivate on the tablet the WiFi (from the system settings).

Note how the tablet on the other hand is perfectly logged onto the WiFi net and I can use it without issues to browse the Internet, for example.

But it isn't only ping. If I try to use a SSH deamon app (QuickSSHd) it  starts successfully, but I can't connect a terminal client from my PC.

At least, I can't anymore... It used to work, until (I think) I installed the "Cisco AnyConnect Rooted" VPN app. That's the only operation I have done on the tablet, before I had this issue. Cisco AnyConnect installed sucesfully a but it never succeeded to start, because it required root privileges  (which I haven't given to the tablet yet). Tablet is with its factory firmware:

Android: 2.2.1

Baseband: BD_P678A1V1.0.2B09

Kernel: 2.6.29 hengai@and-ser2#11020

Build: renesas_emev-eng 2.2.1 MASTER eng.hengai.20110729.172420  test-keys

(my tablet is this one:

http://www.aliexpres..._d03p0558e02r02

; with 3G)

Same issue is there even after un-installing Cisco AnyConnect Rooted. Of course I will post this same request for help on this tablet-expert forum as well, but how does it come that installing Cisco AnyConnect may have changed system services, without a root access?

Any hint on how to debug this issue?

thanks

Labels:
0 Helpful
1 Reply 1

fabio.fumi
Level 1
Level 1

‎10-17-2011 04:03 AM

Actually, what I'm seeing is that the ping response is "unstable", rather than totally absent. Leaving it going for a while I get this:

C:\Users\FFUMI>ping -n 100 192.168.0.100

Pinging 192.168.0.100 with 32 bytes of data:

Reply from 192.168.0.101: Destination host unreachable.

Reply from 192.168.0.101: Destination host unreachable.

Reply from 192.168.0.101: Destination host unreachable.

Reply from 192.168.0.101: Destination host unreachable.


<<  WiFi Deactivated and re-activated on tablet >>

Reply from 192.168.0.100: bytes=32 time=2015ms TTL=64

Reply from 192.168.0.100: bytes=32 time=8ms TTL=64

Reply from 192.168.0.100: bytes=32 time=7ms TTL=64

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 192.168.0.100: bytes=32 time=7ms TTL=64

Reply from 192.168.0.100: bytes=32 time=5ms TTL=64

Reply from 192.168.0.100: bytes=32 time=3ms TTL=64

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 192.168.0.100: bytes=32 time=7ms TTL=64

Request timed out.

Reply from 192.168.0.100: bytes=32 time=8ms TTL=64

Request timed out.

Request timed out.

Reply from 192.168.0.100: bytes=32 time=7ms TTL=64

Reply from 192.168.0.100: bytes=32 time=6ms TTL=64

Request timed out.

Request timed out.

Reply from 192.168.0.100: bytes=32 time=13ms TTL=64

Reply from 192.168.0.100: bytes=32 time=11ms TTL=64

Request timed out.

Request timed out.

Request timed out.

Request timed out.

...

I can't notice any delay or issue with Internet browsing, which feels quick and continuous in response. WiFi signal is shown as stable too. The list of "request timed out" can last for minutes, which I would have noticed if it was a real missing connectivity issue! Indeed I can browse the Internet with no isue at all, while I see at the same time these "request timed out" from the ping window on my PC.

Let me attach a fragment of the DLog, from the same period of time, in case it can give some additional clue...

115529-DLog1.txt.zip
0 Helpful
Customers Also Viewed These Support Documents