Can someone make sense of WHY AirDroid 2 is not providing the correct IP address?
(Or, how can I figure out the correct IP address of the device running AirDroid2?)
Here's what happens:
0. I have no data plan so I turn on WiFi on the Samsung Galaxy S3
1. My home modem has a static public IP address - lets call it 55.55.55.55
2. The single 55.55.55.55 wire coming out of the modem goes into a broadband router
3. That home broadband router is on 192.168.1.1 & it hands out DHCP addresses
4. Those addresses start with 192.168.1.2 and continue from there (192.168.1.3, 192.168.1.4, etc.)
5. My Centos PC is handed a DHCP IP address by that router of 192.168.1.2
6. My WinXP PC is handed a DHCP IP address by that router of 192.168.1.3
7. AirDroid on the Samsung Galaxy S3 says to connect to 192.168.1.8:8888
9. But both PC web browsers time out (every time) pointed to 192.168.1.8:8888
10. Whatismyipaddress reports the Samsung Galaxy public IP address of 55.55.55.55
11. Whatismyipaddress also reports the two PC's public IP address of 55.55.55.55
12. This makes sense but then, how do I debug why AirDroid2 won't connect?
Interestingly, if I ping the IP address that AirDroid2 wants me to connect to, it times out:
$ ping 192.168.1.8 (times out)
It seems that AirDroid2 thinks the Samsung Galaxy S3 is on 192.168.1.8, but, it's really not.
But then, what IP address *is* the Samsung Galaxy S3 on anyway?
And, why doesn't AirDroid2 connect on *that* IP address?
It wouldn't be so frustrating if the USB cable connection would work but there are long threads on why you can't connect the Samsung
Galaxy S3 to Centos in either MTP or PTP mode (MTP never worked and PTP just simply stopped working).
Anybody have expertise on how to solve this dilemma that AirDroid2 is telling me to connect
(Or, how can I figure out the correct IP address of the device running AirDroid2?)
Here's what happens:
0. I have no data plan so I turn on WiFi on the Samsung Galaxy S3
1. My home modem has a static public IP address - lets call it 55.55.55.55
2. The single 55.55.55.55 wire coming out of the modem goes into a broadband router
3. That home broadband router is on 192.168.1.1 & it hands out DHCP addresses
4. Those addresses start with 192.168.1.2 and continue from there (192.168.1.3, 192.168.1.4, etc.)
5. My Centos PC is handed a DHCP IP address by that router of 192.168.1.2
6. My WinXP PC is handed a DHCP IP address by that router of 192.168.1.3
7. AirDroid on the Samsung Galaxy S3 says to connect to 192.168.1.8:8888
9. But both PC web browsers time out (every time) pointed to 192.168.1.8:8888
10. Whatismyipaddress reports the Samsung Galaxy public IP address of 55.55.55.55
11. Whatismyipaddress also reports the two PC's public IP address of 55.55.55.55
12. This makes sense but then, how do I debug why AirDroid2 won't connect?
Interestingly, if I ping the IP address that AirDroid2 wants me to connect to, it times out:
$ ping 192.168.1.8 (times out)
It seems that AirDroid2 thinks the Samsung Galaxy S3 is on 192.168.1.8, but, it's really not.
But then, what IP address *is* the Samsung Galaxy S3 on anyway?
And, why doesn't AirDroid2 connect on *that* IP address?
It wouldn't be so frustrating if the USB cable connection would work but there are long threads on why you can't connect the Samsung
Galaxy S3 to Centos in either MTP or PTP mode (MTP never worked and PTP just simply stopped working).
Anybody have expertise on how to solve this dilemma that AirDroid2 is telling me to connect