skearton
Well-Known Member
I would like my triumph to pick up a dynamic IP in my work place.
We are on a 255.255.0.0 subnet, and my phone grabs the same non-working IP everytime no matter which access point I use in the building (5). Wifi manager indicates that I am connected just fine.
I get the "no network" page in my browser, GV doesnt work, Play doesnt work, etc.
My tablet on honeycomb gets an IP and works perfect, all PC's in the network log on fine, Iphones work, etc.
I have 2 android devices, both mine, that wont work.
Honeycomb Galaxy tab works fine.
Froyo rooted Apad - grabs 10.122.1.22
Froyo/CM7/MIUI Rooted Triumph grabs 10.122.1.22 also.
IP is within scope
Gateway is correct
DNS is correct
DHCP is correct
All values are based on NetInfo from Play.
Any idea why this is going on? Think flashing Froyo stock would help? Does only Honeycomb and up support that subnet properly?
When DHCP came from the router it worked fine. When using the DHCP controller (server 2008 r2) is when I started experiencing the issue.
I thought it was a specific Android issue, but then my new Galaxy tab worked fine.
We are on a 255.255.0.0 subnet, and my phone grabs the same non-working IP everytime no matter which access point I use in the building (5). Wifi manager indicates that I am connected just fine.
I get the "no network" page in my browser, GV doesnt work, Play doesnt work, etc.
My tablet on honeycomb gets an IP and works perfect, all PC's in the network log on fine, Iphones work, etc.
I have 2 android devices, both mine, that wont work.
Honeycomb Galaxy tab works fine.
Froyo rooted Apad - grabs 10.122.1.22
Froyo/CM7/MIUI Rooted Triumph grabs 10.122.1.22 also.
IP is within scope
Gateway is correct
DNS is correct
DHCP is correct
All values are based on NetInfo from Play.
Any idea why this is going on? Think flashing Froyo stock would help? Does only Honeycomb and up support that subnet properly?
When DHCP came from the router it worked fine. When using the DHCP controller (server 2008 r2) is when I started experiencing the issue.
I thought it was a specific Android issue, but then my new Galaxy tab worked fine.