Android can no longer connect to internal webpage

M

MrHood22

Supreme [H]ardness
Joined
Aug 21, 2007
Messages
4,312
I'm working on a website for my company and so far it's only internal. I have been working on it on my PC but I'm also testing it on mobile devices. When I first tried to connect a few days ago it worked fine and then a few days after that I went to try again and I haven't been able to connect since.

What the website continues to work on...
My Windows 7 PC
iPhone
Android tablet (4.3)
Nook tablet (not sure what OS that runs)


They're all connected to the same wifi network. From my Android phone, I can ping the Gateway but I can't ping the IP of the website.
 
is the wireless network on the same subnet as the server?
 
Sure. You stated that you can ping the gateway but not the site, so that's indicative of a routing problem (as apparently other devices can route to the server, so we'll rule out the gateway itself).

http://www.cyberciti.biz/faq/what-is-a-routing-table/

For a basic overview.

There's some other assumptions here, but say your android is 192.168.0.55 and the website is 10.0.0.23 and both are on different networks that need to be routed. Your android needs to know where to send that packet (likely the default gateway) since it's not a local network.

So you'd have something like this in the routing table:

192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 ra0
0.0.0.0 192.168.0.1 0.0.0.0 UG 100 0 0 ra0

Which is basically saying, if the destination address is on the 192.168.0.0/24 network, put it on the wire using interface ra0 (it's local). If the destination address is anything else (say 10.0.0.23) then send it over to 192.168.0.1 and let him take care of it.

It seems like you're missing the default gateway entry (UG) since you can reach the gateway, but can't reach beyond that.
 
You must log in or register to reply here.
Back
Top