Database Users

Focus wifi

Just Got a focus from america (i live in the uk). Everything seems to work, except the wifi. It just says connection unsuccessful your phone couldnt reach the wi-fi network. . does anyone know how to solve this issue ?

Is this a home router or work router your trying to connect to? Some people have reported that having the router assign a static IP worked, because DHCP was assigning a IP address that was already assigned to another device.
If it's a corporate router MAC address filtering maybe enabled & your phone's MAC address may not be in the list of allowed devices. It could also be that you haven't loaded the required certificate to allow you use of the router.

[Q] VegaComb 8.1 Ad-Hoc Tether issues

I'm almost at the end of my tether (urgh) with this one.
I have a 10s freshly flashed to VegaComb 3.2 Build 8.1
Loving it except it flat refuses to tether in any way, shape or form with my mobile (HTC TP2 + Energy 6.5 ROM)
Bluetooth doesn't work (pairs but can't share internet) but we'll ignore that for now.
I'm using HTC's Wifi Router software. I know this is working because a PC can connect to it fine and browse the web.
VegaComb could see the AP from the outset. I have tried the wpa_supplicant file in the Xoom Ad-Hoc guide thread but I suspect it's identical to the one already in the ROM.
When I tap connect it asks for the WEP key then goes to Obtaining IP Address. It sits there doing this for quite some time then gives up.
If I set an IP manually it changes to Connected, and from a terminal window on the tablet I can ping the IP address on wlan0. However it can't ping the phone, or get any internet access. Pinging the phone gives Destination Host Unreachable.
I have checked the routing table and it looks fine.
I have tried this:
setprop net.hostname test
In case it was due to the long and not-super-compliant (has an underscore) default hostname breaking either DHCP or networking.
Wifi to a WPA2/PSK infrastructure AP works completely fine.
Any suggestions?
I see the latest OTA for the TF has fixed Ad-Hoc for them, I wonder if perhaps someone could tell us what changed to fix it?

WiFi Connected but No Internet - I FIGURED IT OUT!!!!!!!!!!!!

Here is basically a run-down of what I did. I hope this helps everyone out.
Device specs:
Samsung Galaxy Player 4.0 Rooted
Network Specs:
DSL Modem
Router (DHCP with WPA security and does not have MAC Filtering)
4 Access Points (all on same channel broadcasting same SSID with same WPA security DHCP)
2 Servers - Static IPs
-Server 1 - DNS (not sure if it is actually a DNS server or just forwards the requests). Also storage/application server.
-Server 2 - Storage/Application/SQL server
Many clients on network (unsure of total amount but somewhere around 30 would be my guess)
Problem (note this is only on this network, every other network wifi
works just fine):
Wifi Connected but no internet.
My Windows 7 laptop (same network) gets internet access with no problems
No reports of any other clients on the network having this issue
Device has assigned a good DHCP IP address
Subnet, Gateway, and DNS IPs are all correct (they match the ones on my laptop)
Connection strength is great (speed is 52mbps)
Device has full local access (intranet). It can access all files and other devices on the network.
On occasion the device will get "internet" access for a brief period of time but will go back to "intranet" access only after a few minutes.
Tests Performed (My android device will be referred to as "device" my laptop will be reffered to as "laptop". All tests were performed with both laptop and device connected to the network in question, unless otherwise specified, and device was not able to access internet):
Ping from laptop to device - Successful
Ping from device to laptop - Successful
Ping from laptop to gateway - Successful
Ping from device to gateway - Failed
Resolve DNS IP on device - Successful
Resolve DNS IP on laptop - Successful
Ping from laptop to google - Successful
Ping from device to google - Failed
Small FTP file transfer from laptop to device - Successful
Small FTP file transfer from device to laptop - Successful
Device has no problems on other networks (tried un-secured, WEP, and WPA/WPA2)
Connect device using Google public DNS servers
-Intranet - Successful
-Internet - Failed
-Resolve DNS IP - Successful
Connect laptop using Google public DNS servers
-Intranet - Successful
-Internet - Successful
-Resolve DNS IP - Successful
More that I cannot remember right now. Will add as they come to me.
At this point I gave up for a few days. Every test and every bit of research returned nothing. I had spent many many hours trying to figure this out and testing theories and nothing ever pointed me in the right direction of where to go. Nothing made sense EVERY single setting is the same is on my laptop. Started thinking maybe there was something in the router that could be blocking Android devices (since it is a work network). Although I am not a aware of a router feature to do that I figure I would try some more tests.
Testing Round 2 (same conditions as initial tests):
Configured laptop to be a Wifi hotspot.
-From CMD command 1: netsh wlan set hostednetwork mode=allow ssid=AP key=XXXXXXXXX
-From CMD command 2: netsh wlan start hostednetwork
-From network and sharing center: Shared the physical wireless network connection with the Microsoft Virtual WiFi Miniport Adapter.
-The above commands create a virtual wireless adapter and set it broadcast the specified SSID with the specified WPA security key. Then you can choose any available, connected, physical, internet connection and share it's internet connection with the virtual connection, thus theorectically turning my laptop into a 5th access point on the network.
Connected device to the SSID "AP"
-Intranet - Successful
-Internet - SUCCESSFUL
Horray!!!! Progress! So with the above information I went to our IT guy and we sat down and looked at some stuff (settings in the router, access points, and servers). After digging and digging around within the settings we came up with.... you guessed it NOTHING!!!!!!!!!!!!! Now I was in "Its on!" mode and decided I wasn't going to stop until I found out at least what was causing the problem. My IT guy was also very determined to figure this out as he doesn't like to get beat either. So we both went at it. We decided the first thing to do was make a very detailed network map containing every piece of information we could possibly find. We did this all from his machine (laptop with Windows 7) and wrote everything down on paper (we even used a piece of our 36" wide roll paper from our plotter to make sure everything would fit) and made an excel spredsheet with all the info. Now with the newly aquired network information I decided I was going to do more testing.
Testing Round 3 (same conditions as initial test):
Map the entire network again gathering every piece of information possible just like before but this time using MY DEVICE (not my laptop).
Compare
Finally! I have found the problem! As stated before my device was getting the correct gateway IP (XXX.XXX.XXX.1) which is the same as my laptop). However the assigned MAC address OF THE GATEWAY (router) to my device is XX:XX:XX:XX:XX:FB but the MAC address OF THE GATEWAY (router) to my laptop is XX:XX:XX:XX:XX:FA. Got back with our IT guy and we found (by looking the router config) that the XX:XX:XX:XX:XX:FA is the LAN MAC address for the router. The XX:XX:XX:XX:XX:FB is the WAN MAC address for the router.
Testing Round 4 (same conditions as intial test):
Connected laptop to network, confirmed XX:XX:XX:XX:XX:FA MAC address was assigned for the gateway by running "arp -a" in CMD.
-Pinged google - Passed
-Changed assigned MAC address of gateway by running "arp -s XXX.XXX.XXX.1 XX:XX:XX:XX:XX:FB" in CMD
-Verified new MAC address assignment by running "arp -a" in CMD
-Pinged google - Failed
-Changed the MAC back and pinged google again - Successful
Connected device to network, confirmed XX:XX:XX:XX:XX:FB MAC address was assigned for the gateway by running "arp -a" in Terminal.
-Pinged google - Failed
-Changed assigned MAC address of gateway by running "su" then "arp -s XXX.XXX.XXX.1 XX:XX:XX:XX:XX:FA" in Terminal
-Verified new MAC address assignment by running "arp -a" in Terminal
-Pinged google - Successful
-Changed the MAC back and pinged google again - Failed
Conclusion:
For some reason the device is getting assigned the correct gateway IP but the wrong gateway MAC. This is allowing the device to connect to the network but not communicate with the router. Since it can't communicate with the router any "Internet" requests time out because the packets have to go through the router to make it to the "Internet". Since it is not blocked from the network it can still connect and communicate with other clients on the "Intranet" but not the router.
Our IT guy thinks there is a client somewhere on the network in the same subnet that is configured in this matter and it just so happens that for some reason my device is picking that up when it connects. He is going to look into it more when time permits but since we are very busy and we have already spent way too much time on this, and I now know at least what the issue is, he is going to move on for now.
Why would my device be picking up the WAN MAC address of the router?
What would be responsible for assigning a WAN or LAN MAC address?
How can I prevent this?
Has anyone ever experienced anything like this?
Temporary Solution (must be rooted):
Open your favorite terminal app on your device.
-Enter "su" (without quotes)
-Enter "arp -s [Your gateway IP here] [Your gateway's LAN MAC address here]
Browse away!!!!!

Hello.
I had the same problem, that I could connect to router but had no connection to internet.
Read this post and started to do some research on my router. When I configurated my router, there was an option to clone MAC address. And of course to get it done fast I cloned MAC. And now I checked that it cloned my laptop MAC. Changed MAC from laptop to Routers MAC (must be on label under router) and got a really nice internet connection.

Hi, I think I have the same problem with the same device, Samsung Galaxy Player 4, but even if my device is rooted I still can't excecute the "arp" command from the Terminal application (there is no "arp" command). How can I check/modify the arp list on my device???
I really appreciate your help. Thanks in advance!!!

I use the terminal emulator app. It works just fine for me and I never had to download any other software to be able to run the ARP command.

bmx0964 said:
Here is basically a run-down of what I did. I hope this helps everyone out.
Temporary Solution (must be rooted):
Open your favorite terminal app on your device.
-Enter "su" (without quotes)
-Enter "arp -s [Your gateway IP here] [Your gateway's LAN MAC address here]
Browse away!!!!!
Click to expand...
Click to collapse
anyone found a solution to this ?
just updated to ics4 and cannot connect to the internet.

You only have one device that assigns IP adresses, right?
How about changing the channel to see if that works? or maybe even the security protocol

greeky510 said:
You only have one device that assigns IP adresses, right?
How about changing the channel to see if that works? or maybe even the security protocol
Click to expand...
Click to collapse
the only thing that worked for me is to turn on the dhcp option
in my router. previously, i was using static ips

may_east said:
the only thing that worked for me is to turn on the dhcp option
in my router. previously, i was using static ips
Click to expand...
Click to collapse
I had the sams problem. I could connect with my wifi but had no internet acces. The solution here was the wifi encription.
My smartphone could not encript the hard encription I think. With WEP encription it all works well.

Hey guys,
Here's a run down of the problem I'm currently having. A few months ago I purchased a Dapeng A75 currently running ICS 4.0. Although a beautiful and fast phone, just recently it started going out of wack.
- Youtube and Play Store hang on "Loading" screen
- My Gmail accounts won't sync
- I can no longer search on Google.com with ANY browser through WiFi. (I do not have data service on my phone)
I've tried several attempts at troubleshooting this, all which have failed.
- I restored my phone to factory default.
- Uninstalled and reinstalled these apps.
- Downgraded the apps to previous versions.
- Cleared my cache on just about everything.
- Release and renewed my IP in Terminal.
Just recently I noticed a CWM recovery image posted and I figure this is the only solution. Wiping out the phone and flashing a fresh ROM but unfortunately I can only get as far as installing the drivers to my Windows 7 machine. Some reason when I plug the phone in after installing the drivers, Windows will prompt me that the device is plugged in but before I get a chance to hit F9 for SP Flash Tool to do it's thing, the device quickly disconnects.
NOTE: I am able to browse Google via WiFi only by using HotSpot Shield VPN (Which is problematic in itself).
I'm currently losing the battle with this phone and at my wits end. Is there anyone out there who is experiencing the same situation or has some sort of solution which doesn't involve be shelling out more money for a new phone?

good work brother
i understood the above problem n i too experienced the same problems so now i will take ur research to next level n see my know of network .
i appreciate all the work done you , in research of this LITTLE but hetic problem.
i have learned a lot through u r research.
n will do more n keep u guys posted if i found somthing on this
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
bmx0964 said:
Here is basically a run-down of what I did. I hope this helps everyone out.
Device specs:
Samsung Galaxy Player 4.0 Rooted
Network Specs:
DSL Modem
Router (DHCP with WPA security and does not have MAC Filtering)
4 Access Points (all on same channel broadcasting same SSID with same WPA security DHCP)
2 Servers - Static IPs
-Server 1 - DNS (not sure if it is actually a DNS server or just forwards the requests). Also storage/application server.
-Server 2 - Storage/Application/SQL server
Many clients on network (unsure of total amount but somewhere around 30 would be my guess)
Problem (note this is only on this network, every other network wifi
works just fine):
Wifi Connected but no internet.
My Windows 7 laptop (same network) gets internet access with no problems
No reports of any other clients on the network having this issue
Device has assigned a good DHCP IP address
Subnet, Gateway, and DNS IPs are all correct (they match the ones on my laptop)
Connection strength is great (speed is 52mbps)
Device has full local access (intranet). It can access all files and other devices on the network.
On occasion the device will get "internet" access for a brief period of time but will go back to "intranet" access only after a few minutes.
Tests Performed (My android device will be referred to as "device" my laptop will be reffered to as "laptop". All tests were performed with both laptop and device connected to the network in question, unless otherwise specified, and device was not able to access internet):
Ping from laptop to device - Successful
Ping from device to laptop - Successful
Ping from laptop to gateway - Successful
Ping from device to gateway - Failed
Resolve DNS IP on device - Successful
Resolve DNS IP on laptop - Successful
Ping from laptop to google - Successful
Ping from device to google - Failed
Small FTP file transfer from laptop to device - Successful
Small FTP file transfer from device to laptop - Successful
Device has no problems on other networks (tried un-secured, WEP, and WPA/WPA2)
Connect device using Google public DNS servers
-Intranet - Successful
-Internet - Failed
-Resolve DNS IP - Successful
Connect laptop using Google public DNS servers
-Intranet - Successful
-Internet - Successful
-Resolve DNS IP - Successful
More that I cannot remember right now. Will add as they come to me.
At this point I gave up for a few days. Every test and every bit of research returned nothing. I had spent many many hours trying to figure this out and testing theories and nothing ever pointed me in the right direction of where to go. Nothing made sense EVERY single setting is the same is on my laptop. Started thinking maybe there was something in the router that could be blocking Android devices (since it is a work network). Although I am not a aware of a router feature to do that I figure I would try some more tests.
Testing Round 2 (same conditions as initial tests):
Configured laptop to be a Wifi hotspot.
-From CMD command 1: netsh wlan set hostednetwork mode=allow ssid=AP key=XXXXXXXXX
-From CMD command 2: netsh wlan start hostednetwork
-From network and sharing center: Shared the physical wireless network connection with the Microsoft Virtual WiFi Miniport Adapter.
-The above commands create a virtual wireless adapter and set it broadcast the specified SSID with the specified WPA security key. Then you can choose any available, connected, physical, internet connection and share it's internet connection with the virtual connection, thus theorectically turning my laptop into a 5th access point on the network.
Connected device to the SSID "AP"
-Intranet - Successful
-Internet - SUCCESSFUL
Horray!!!! Progress! So with the above information I went to our IT guy and we sat down and looked at some stuff (settings in the router, access points, and servers). After digging and digging around within the settings we came up with.... you guessed it NOTHING!!!!!!!!!!!!! Now I was in "Its on!" mode and decided I wasn't going to stop until I found out at least what was causing the problem. My IT guy was also very determined to figure this out as he doesn't like to get beat either. So we both went at it. We decided the first thing to do was make a very detailed network map containing every piece of information we could possibly find. We did this all from his machine (laptop with Windows 7) and wrote everything down on paper (we even used a piece of our 36" wide roll paper from our plotter to make sure everything would fit) and made an excel spredsheet with all the info. Now with the newly aquired network information I decided I was going to do more testing.
Testing Round 3 (same conditions as initial test):
Map the entire network again gathering every piece of information possible just like before but this time using MY DEVICE (not my laptop).
Compare
Finally! I have found the problem! As stated before my device was getting the correct gateway IP (XXX.XXX.XXX.1) which is the same as my laptop). However the assigned MAC address OF THE GATEWAY (router) to my device is XX:XX:XX:XX:XX:FB but the MAC address OF THE GATEWAY (router) to my laptop is XX:XX:XX:XX:XX:FA. Got back with our IT guy and we found (by looking the router config) that the XX:XX:XX:XX:XX:FA is the LAN MAC address for the router. The XX:XX:XX:XX:XX:FB is the WAN MAC address for the router.
Testing Round 4 (same conditions as intial test):
Connected laptop to network, confirmed XX:XX:XX:XX:XX:FA MAC address was assigned for the gateway by running "arp -a" in CMD.
-Pinged google - Passed
-Changed assigned MAC address of gateway by running "arp -s XXX.XXX.XXX.1 XX:XX:XX:XX:XX:FB" in CMD
-Verified new MAC address assignment by running "arp -a" in CMD
-Pinged google - Failed
-Changed the MAC back and pinged google again - Successful
Connected device to network, confirmed XX:XX:XX:XX:XX:FB MAC address was assigned for the gateway by running "arp -a" in Terminal.
-Pinged google - Failed
-Changed assigned MAC address of gateway by running "su" then "arp -s XXX.XXX.XXX.1 XX:XX:XX:XX:XX:FA" in Terminal
-Verified new MAC address assignment by running "arp -a" in Terminal
-Pinged google - Successful
-Changed the MAC back and pinged google again - Failed
Conclusion:
For some reason the device is getting assigned the correct gateway IP but the wrong gateway MAC. This is allowing the device to connect to the network but not communicate with the router. Since it can't communicate with the router any "Internet" requests time out because the packets have to go through the router to make it to the "Internet". Since it is not blocked from the network it can still connect and communicate with other clients on the "Intranet" but not the router.
Our IT guy thinks there is a client somewhere on the network in the same subnet that is configured in this matter and it just so happens that for some reason my device is picking that up when it connects. He is going to look into it more when time permits but since we are very busy and we have already spent way too much time on this, and I now know at least what the issue is, he is going to move on for now.
Why would my device be picking up the WAN MAC address of the router?
What would be responsible for assigning a WAN or LAN MAC address?
How can I prevent this?
Has anyone ever experienced anything like this?
Temporary Solution (must be rooted):
Open your favorite terminal app on your device.
-Enter "su" (without quotes)
-Enter "arp -s [Your gateway IP here] [Your gateway's LAN MAC address here]
Browse away!!!!!
Click to expand...
Click to collapse
i would like to add if u have seen the
cmd-ncpa.cpl-ipv4-propreties- in this section u see its Dhcp so all fields are inactive
but u can see gateway ip which is inactive such as in my case 192.168.1.1
u cannot remove that.
any body saw the reply....
thanks regards

bmx0964 said:
Temporary Solution (must be rooted):
Open your favorite terminal app on your device.
-Enter "su" (without quotes)
-Enter "arp -s [Your gateway IP here] [Your gateway's LAN MAC address here]
Browse away!!!!!
Click to expand...
Click to collapse
Thanks, This Solution Saved me Today

Help, I know its wrong section.....

Before anybody starts flaming me, I know this is the wrong section but Im not getting any responses on my original post.
I have my wireless router set up to use MAC Address filtering, where as it will only let recognized MAC Addresses onto my network. When I have the router's internal firewall turned off my Kindle Fire will connect np. But when I enable the router's internal firewall it just loops thru the WiFi scanning and obtaining ip address, but never connects. So something in the built in firewall is blocking the Kindle Fire. Any ideas how I can make the Kindle Fire connect after the firewall is enabled? I have 3 cell phones that connect just fine behind the firewall. Its a Belkin N-150 Model Number F6D4230-4 Version 3.

Just remove MAC filtering, a WiFi network with WPA2 and AES encryption is enough to protect your network (unless you have a very good hacker near you).
Be sure your password contains uppercases, lowercases, digits, a special caracter (example : !"/$%?) and a minimal of 8 characters and it will be ok.

Max) said:
Just remove MAC filtering, a WiFi network with WPA2 and AES encryption is enough to protect your network (unless you have a very good hacker near you).
Be sure your password contains uppercases, lowercases, digits, a special caracter (example : !"/$%?) and a minimal of 8 characters and it will be ok.
Click to expand...
Click to collapse
Yea but Im trying to avoid using a passkey, and only use the MAC filtering... Any suggestions?

slufoot69 said:
Yea but Im trying to avoid using a passkey, and only use the MAC filtering... Any suggestions?
Click to expand...
Click to collapse
What is the problem with passkey?
You only need to enter the password one time in your device.
But
You may want to try to force the ip adress with a static ip (search google for that case)

Max) said:
You may one to try to force the ip adress with a static ip (search google for that case)
Click to expand...
Click to collapse
Thanked instead of quoting - oops - but I plus 1 this

Max) said:
What is the problem with passkey?
You only need to enter the password one time in your device.
But
You may one to try to force the ip adress with a static ip (search google for that case)
Click to expand...
Click to collapse
Im trying to avoid the passkey because when my daughter has friends over they bring there electronics and always ask to get on my wifi. I dont mind them getting on my wifi when they are at my house but I dont want the parents stilling my bandwidth, because they will have my password for wifi on there devices. With MAC filtering I can add there individual MAC addresses so I can allow them or deny them access.

Why don't you use a MAC blacklist? When you want a certain device that has been connected not to have access, just add it to the blacklist and that's it. My Asus with DD-WRT does that gracefully.

i wouldnt use just mac filter to as spoofing mac addresses is very easy

Check the firewall logs, perhaps the mac address is showing up different (not sure why it would) on the kindle fire.
slufoot69 said:
Before anybody starts flaming me, I know this is the wrong section but Im not getting any responses on my original post.
I have my wireless router set up to use MAC Address filtering, where as it will only let recognized MAC Addresses onto my network. When I have the router's internal firewall turned off my Kindle Fire will connect np. But when I enable the router's internal firewall it just loops thru the WiFi scanning and obtaining ip address, but never connects. So something in the built in firewall is blocking the Kindle Fire. Any ideas how I can make the Kindle Fire connect after the firewall is enabled? I have 3 cell phones that connect just fine behind the firewall. Its a Belkin N-150 Model Number F6D4230-4 Version 3.
Click to expand...
Click to collapse

bogdan5844 said:
Why don't you use a MAC blacklist? When you want a certain device that has been connected not to have access, just add it to the blacklist and that's it. My Asus with DD-WRT does that gracefully.
Click to expand...
Click to collapse
What is MAC Blacklist? is this a program that needs downloaded and installed?

slufoot69 said:
What is MAC Blacklist? is this a program that needs downloaded and installed?
Click to expand...
Click to collapse
Should just be an option in router settings. It's very similar in appearance to the MAC filtering.

Cant connect to one specific wifi network

Hi everyone,
At my parents' place, there is a wifi extender in my room.
Every possible electronic I have is able to connect to it, except my s10+ for some reason.
My uncle has the same phone and for him, it works fine.
Everywhere else where I connect to wifi it works, its just this specific router.
I get an error message saying "Couldn't get IP address
Does anyone have any idea what is causing this and how I can fix this?

Maybe they have static IP only enabled on their WiFi. Mine requires me to program one in (within range of addresses) or you have static enabled and one of their devices is using that IP.
Use his device to see the config (settings>wifi>tap hold on connection to wifi name>modify or view if available. Type the same into yours but change the last part of the IP (ie. 192.168.6.88 change the 88 to 193. Any number under 254 higher the better chance of it being free. Use the same info as theirs. )
IE
IP 192.168.6.193
Gateway 192.168.6.1
Subnet mask 255.255.255.0 (whatever theirs is)
DNS 1 is 75.75.75.75 or whatever theirs is
DNS 2 is. 75.75.76.76 or whatever theirs is
If that fails then reboot their router and use WPS (Google it got your phone model. Should be settings>wifi> 3 for menu top right somewhere in there as WPS Setup)

leo72793 said:
Maybe they have static IP only enabled on their WiFi. Mine requires me to program one in (within range of addresses) or you have static enabled and one of their devices is using that IP.
Use his device to see the config (settings>wifi>tap hold on connection to wifi name>modify or view if available. Type the same into yours but change the last part of the IP (ie. 192.168.6.88 change the 88 to 193. Any number under 254 higher the better chance of it being free. Use the same info as theirs. )
IE
IP 192.168.6.193
Gateway 192.168.6.1
Subnet mask 255.255.255.0 (whatever theirs is)
DNS 1 is 75.75.75.75 or whatever theirs is
DNS 2 is. 75.75.76.76 or whatever theirs is
If that fails then reboot their router and use WPS (Google it got your phone model. Should be settings>wifi> 3 for menu top right somewhere in there as WPS Setup)
Click to expand...
Click to collapse
Thank you, will try this out