Database Users

XDAIIs wifi aaaarrrghhh - I wanna break it

into teeny weeny little pieces.
I feel so much better now!!
Anyways...I have a wireless home network up and running and would like to connet the xda to it.
I can connect to the router no probs but IE cant connect to the web. it says "the page you are looking for cannot be found".
Any ideas why I can connect to the router but not to the web?
Cheers folks - thanks

I know how you feel. There are a couple things you have to do.
First check that you have selected to connect via "work".
Then ensure that the IP address shown is in the range of 192.168.0.X

had no problems with my wifi on my home network, as ale210p said, I think it's with the way your connect via "work" or "ISP" is configured

hiya folks
thanks for coming to my rescue..hopefully i can get this thing on the road.
- in connections - advanced - select networks. both selections are set to "my work network"
- in configure network adapters - network adapters. the "my network connects me to" dropdown is selected to work.
- where can i check my ip address on the device?
Alhtough I am connected to my wireless network as that what the wireless LAN manager says?
any ideas guys?
many thanks

Is your internet provider checking the MAC address? my provider checks for the MAC address and hence I had to register my MAC address first with the provider.

I'm pretty sure my ISP isnt checking my MAC address as my PC and other computer on the network work fine with regards to internet access and I never gave the MAC addresses to the ISP.
However, my modem router does have mac filtering enabled. I have copied the MAC address of the xda to the allowed list. However I've also tried to turn this filter off and the result was the same....I still could connect to my home wireless network but had the same error message when trying to surf through pocket IE.
Any other ideas on why I can connect to the network but IE wont let me surf?
thanks again

I'm having exactly the same problem as Richard. What I don't understand is, I can drive around and find free residential wireless hotspots and surf the net , but I can't do it on my own WLAN!

IP info OK?
These symptoms could indicate that vital IP info is missing on your XDA.
Does your XDA get an IP address + gateway address + DNS server address from the router's DHCP server? Use vxIPConfig to determine this http://www.cam.com/windowsce.html
I know for a fact that many times (not always) my QTEK 9090 does NOT get the required IP info from my SMC Barricade 2804WBR b/g wireless router, so I started using fixed addresses on my QTEK.
If I use DHCP, many times I can connect to the router but am unable to access the internet... Because the QTEK has not received an IP address/gateway address/DNS server address in those cases. Fixed addresses always work.

whoa
thanks for the advice. i installed the app. rubbed the sticks together and there were sparks i tell you!!! but what does it all mean?
the ip address is 169.254.84.245
subnet mask 255.255.0.0
dhcp server 255.255.255.255
im no tekkie so am not sure what the above means? does it provide any clues?
thanks for the advice so far

just an update
i manually inputted the ip address assigned to my xda by the router as i have dhcp disabled on the router.
nonetheless it sill doesnt let me connect to the net but i can connect to the wlan?

richard321_blue said:
just an update
i manually inputted the ip address assigned to my xda by the router as i have dhcp disabled on the router.
nonetheless it sill doesnt let me connect to the net but i can connect to the wlan?
Click to expand...
Click to collapse
Fixed IP address is good, but have you also put in the gateway address and DNS server address? Normally the gateway address + DNS server address = router address.
If your routers IP address would be 192.168.1.1 (quite common address), then your IP address could be 192.168.1.2, gateway address would be 192.168.1.1 and DNS server (name server) address also 192.168.1.1.
BTW; this:
the ip address is 169.254.84.245
subnet mask 255.255.0.0
dhcp server 255.255.255.255 <========= !!!!
means that DHCP didn't work!
I suppose that when you state "connect to the wlan" you mean that you can 'see' machines on your local network? Or what? That would make sense because you wouldn't need a gateway address and DNS server address for that normally (broadcasts).

siliconaddict....you're a genius!
finally it works, it works i say.
fantastic.
thanks to all for the advice and feedback - much appreciated.
can i stoke the fire and ask how i can sync via wifi as well?

never done it myself, but here is a guide
I have never synced over WiFi myself, but here are some guides:
http://theillustratednetwork.mvps.org/WM2003/ActiveSync/WM2003ActiveSyncConfiguration.html
http://forum.xda-developers.com/viewtopic.php?p=132820
Please note that the next version of Activesync, version 4, doesn't do syncing over Wifi anymore...
Good luck!

Sorry to be a complete noob, but:
1. How do I find out the IP Address of the XDA (Is it in Wireless LAN Manager, under "current config" and "IP:"?)
2. My Netgear USB WLAN is showing an IP of "0.0.0.0" (on command prompt >> ipconfig) How do I change this?
Thanks

Q & A
A 1: On your PDA use Use vxIPConfig for this http://www.cam.com/windowsce.html. Unfortunately the OS doesn't have a standard utility for it, like 'ipconfig'.
A 2: Does your router hand out IP addresses at all? Or: is DHCP enabled on your router? If true, do you have the correct drivers loaded for that USB NIC? In Device Manager how does it look? Yellow exclamation mark? Can you post the output of 'ipconfig /all'.

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) Set WiFi MAC in CM7 w/ busybox 'ip'

In order to get the Shift to associate with my AP, I need to change the first 2 digits of the WiFi MAC Address to 00 or the router will not accept the device and there is no DHCP lease.
When I remove all saved WiFi entries and run:
ip set eth0 address 00:12:34:56:78:90
to spoof the MAC for example, I can see using the 'ip show' command that it was indeed changed. However when I try to reassociate with any access point (open or not) then I can not connect. The only reason I can think of why this isn't working is because I am not using an engineering hboot.
Does anyone know a workaround for this? Many r outers will not accept the first 6 characters of the mac because it looks invalid. This is with root ofcourse running CM7 with the latest busybox.
Thanks!

I'm having the same problem right now - when I change MAC in my Galaxy S and try connecting to my home router it stops at authenticating and then disconnects.
Router is configured to WPA2-PSK (but with WEP also doesnt work), MAC filtering disabled.
Any ideas?

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

No WiFi after upgrade

Hallo,
I have upgraded my phone to 2.3.5 B521, the one that Huawei has in their site.
The step was: Upgrade to B512 (Problem with WiFi), update to B521 just in case the problem was solved. But, the problem is still there. I get IP from the Router, but I have no connection to the internet!
Please help me.

Does your phone have a mac address or is it nulled?
Sent from my U8800 using xda app-developers app

Yeah check your MAC adress and your IMEI
Probably your MAC adress become to 0 after the update

DriftGT said:
Yeah check your MAC adress and your IMEI
Probably your MAC adress become to 0 after the update
Click to expand...
Click to collapse
I do not have the 2.3.5 installed now, but I if MAC is nulled, how on earth did it get an IP?

Please HELP!
IMEI and MAC are OK and those written at the back of the phone.
When I setup a static IP, everything was OK, I can say that it was FASTER than previously :good: .
So, the problem is DHCP related.
I can confirm now that the problem is somehow related to the the DHCP and the Gateway. Specifically, I have set my router to give as GW itself (10.0.0.1).
BUT, the Gateway I see from the Disp WiFi IP is 0.0.0.0. Any ideas? Is there any log that I can check?
Also, from the router, it is obvious that the phone is NOT connected. The phone is recognized as a such, but it is connected only when I use the static IP.
Important UPDATE
I tried to connect the phone on another router. And it's OK with that router...
The only problem is that I cannot purchase a new router in my home.
So, I need to find out what I can do with my ADSL router (Alcatel Onetouch 585 v6).