192.168.1.101:8888 no longer workingquestion

Last week i was able to log into Airdroid and download/upload files and so forth, as of a couple days ago it no longer works (i have tried rebooting the phone)

I get this now:
The connection has timed out

The server at 192.168.1.101 is taking too long to respond.

Last week i was able to log into Airdroid and download/upload files and so forth, as of a couple days ago it no longer works (i have tried rebooting the phone)

I get this now:
The connection has timed out

The server at 192.168.1.101 is taking too long to respond.

Hi,

Thank you for your feedback.

We would like to confirm with you that do you computer and phone were in the same network?

Would you like to following the steps to check if you are in Local Connection Mode:

(1) For Windows user, press “Win + R” to open Run command box, and run “cmd.exe”:

(2) Type ping + IP (e.g. ping 192.168.20.60) and press Enter to see your ping output:


Read the summary of output:



All packets received and the trip time is short: Your device and PC are over same network, and network is stable.

Some packets lost or the trip time is long: Though your device and PC are over same network, the network is unstable. In this case, the connection mode is probably Remote Connection Mode. Try to connect again.

All packets lost: Your device and PC are not in the same network. Reboot the router or ask for help from network admin.

Feel free to let us know if you need further help.

Best Regards,

Sorry for the delayed reply, this is what i get (and they are in the same network)

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\ComputerA>ping 192.168.20.60

Pinging 192.168.20.60 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.20.60:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\ComputerA>

I changed the router in late April but under the new one it still worked for a week before it stopped working so i am very confused.

I have the exact same issue. The server 192.168.0.1 is taking too long to respond.

Sorry for the delayed reply, this is what i get (and they are in the same network)

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\ComputerA>ping 192.168.20.60

Pinging 192.168.20.60 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.20.60:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\ComputerA>

I changed the router in late April but under the new one it still worked for a week before it stopped working so i am very confused.

We're sorry that you cannot use it cause you network issue.

We're sorry that you cannot use it cause you network issue.

Can you be more specific, why would it work then stop working?
Can it be repaired?

Can you be more specific, why would it work then stop working?
Can it be repaired?

Maybe your router has two outlets, and one can ping with the IP address and other can't.

Maybe your router has two outlets, and one can ping with the IP address and other can't.

I tried every outlet on the router, same result.
This was working at the end of April, the only changes since have been Firefox updates and Airdroid updates, though i tried updating the router firmware an hour ago but that didn't fix anything

I just went to Airdroid web to see when i last transferred files, it was May 1, but the address it suggests has changed to http://192.168.1.3:8890/ so i tried it and got:

The connection was reset

The connection to the server was reset while the page was loading.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

Though i never received any replies it started working again.
Did the last Airdroid update fix it?