Hello! I've got some problem with my htc hero.
when i turn on wi-fi it can find network. but when i try to connect to it, the connecting proccess stops at "obtaining ip address" stage. hero couldn't get ip address from DHCP. wi-fi only works if i set up static ip.
anyone had the same problem? is there any solution?
Thx
yeah
itolianezzz said:
Hello! I've got some problem with my htc hero.
when i turn on wi-fi it can find network. but when i try to connect to it, the connecting proccess stops at "obtaining ip address" stage. hero couldn't get ip address from DHCP. wi-fi only works if i set up static ip.
anyone had the same problem? is there any solution?
Thx
Click to expand...
Click to collapse
happened to me sometimes... I think that is incompatible to some dhcp software based on rooter.. There are some topic that says the problem is on "standard" wi-fi in rooter. here is link:
http://forum.xda-developers.com/archive/index.php/t-541105.html
regards
Thanks for reply.
I found only one reply in that topic where similar problem was described, but the solution given didn't work... (
I think there's some problem with DHCPcd client on hero.
I tried to renew IP address form the shell. here's output:
Code:
# dhcpcd --debug tiwlan0
dhcpcd --debug tiwlan0
tiwlan0: dhcpcd 4.0.1 starting
tiwlan0: hardware address = 00:23:76:20:c3:a2
tiwlan0: executing `/system/etc/dhcpcd/dhcpcd-run-hooks', reason PREINIT
tiwlan0: host does not support a monotonic clock - timing can skew
tiwlan0: broadcasting for a lease
tiwlan0: sending DHCP_DISCOVER with xid 0x85ddb65d, next in 4.00 seconds
tiwlan0: sending DHCP_DISCOVER with xid 0x85ddb65d, next in 7.62 seconds
tiwlan0: sending DHCP_DISCOVER with xid 0x85ddb65d, next in 15.90 seconds
tiwlan0: carrier lost
tiwlan0: carrier acquired
tiwlan0: broadcasting for a lease
tiwlan0: sending DHCP_DISCOVER with xid 0x8d72e552, next in 4.67 seconds
tiwlan0: sending DHCP_DISCOVER with xid 0x8d72e552, next in 7.20 seconds
tiwlan0: sending DHCP_DISCOVER with xid 0x8d72e552, next in 16.93 seconds
tiwlan0: timed out
tiwlan0: probing for an IPV4LL address
tiwlan0: checking 169.254.234.132 is available on attached networks
tiwlan0: sending ARP probe (1 of 3), next in 1.24 seconds
tiwlan0: sending ARP probe (2 of 3), next in 1.94 seconds
tiwlan0: sending ARP probe (3 of 3), next in 2.00 seconds
tiwlan0: using IPv4LL address 169.254.234.132
tiwlan0: adding IP address 169.254.234.132/16
tiwlan0: executing `/system/etc/dhcpcd/dhcpcd-run-hooks', reason IPV4LL
tiwlan0: forking to background
#
What does it mean?
Code:
tiwlan0: host does not support a monotonic clock - timing can skew
maybe this is the problem?
I solved the same problem in a strange way
Hi,
I sure that someone with more knowlege con do it in a better way ...
You must have rooted phone and conected via adb:
C:\HERO\android-sdk-windows\tools\adb.exe root
C:\HERO\android-sdk-windows\tools\adb.exe remount
C:\HERO\android-sdk-windows\tools\adb.exe shell
1) Start wifi and try to conect to you wifi
2) before you get error write this command in the shell:
netcfg tiwlan0 up
netcfg tiwlan0 dhcp
If it not work at the first time do it again.
Cheers
This is a well documented problem with the Hero. It just does not seem to like some wifi routers and will not properly connect to them. AFAIK nobody has come up with a foolproof fix although some say if you disable n and just use g on the router it may work.
I have 3 routers. 2 work fine but 1 (the newest Belkin one) simply will not work. It connects but then whenever I try to use it it comes up with a connection failure message.
i get a simar problem if the ssid is hidden.
You might try setting a Static address by pressing "menu" while in the WiFi setup settings. Unfortunately, this cannot be set for specific routers. It has to be turned on an off when needed. Would be nice to have a Static/DHCP Toggle widget or app.
SSID Problem?
I think this may partly be a SSID issue.
Tried everything, and then noticed I had a large-ish SSID. Changed it to something of 5 chars and all my problems went away....
There may also be issues with special chars in the SSIS that i've seen on other boards. Hope that helps.
SSID Issue Confirmed
I have now successfully "fixed" my home network (netgear wnr2000) by changing its SSID from an 8 character string to a 5 character string.
This is the second network I've fixed in this manner for my Android 2.1 Desire (the other was an airport wireless share from a macbook pro).
Why this is the case I have no idea and I previously tried channels, encryption types, reboots etc all to no avail.
I have the same problem with talk talk router....
Sent from my HTC Hero using XDA App
Related
That is interesting, because it was not the first time.
While working on the internet with my Toshiba all of a sudden I get the remark that no connection could be made with my Linksys B router.
Did a repair and everything was fine.
My Jasjar was just laying on the table, not being used.
Opened my JJ and found out that my pocketweather update was three minutes old. So the JJ had triggered the router.
Too much of a coincidence?
I work on different locations, and also my linksys G router and an old Sitecom at the office had given me minor problems.
I will now try not to use my JJ Wifi for a while and see if the problem comes back.
It is good to know that I never ever had problems with any of tjhose routers for a long period.
Could the Jasjar give problems?
Huib
Have had a similar thing caused by both devices grabbing the same IP. For example,
- PDA in use and allocated an address by the router's DHCP server. PDA then turned itself off due to inactivity.
- A while later, turned on Laptop. Router allocated the same IP address to laptop, since as far as it was concerned, that IP was now free.
- PDA caused to turn on by a scheduled task, such as timed PocketWeather update. Since the PDA still has the original IP allocated, it will immediately try to regain that IP. Depending upon the router/DHCP server, this may be permitted, in which case the laptop will lose it's IP.
Also strange things with WAN IP
astage said:
Have had a similar thing caused by both devices grabbing the same IP. For example,
- PDA in use and allocated an address by the router's DHCP server. PDA then turned itself off due to inactivity.
- A while later, turned on Laptop. Router allocated the same IP address to laptop, since as far as it was concerned, that IP was now free.
- PDA caused to turn on by a scheduled task, such as timed PocketWeather update. Since the PDA still has the original IP allocated, it will immediately try to regain that IP. Depending upon the router/DHCP server, this may be permitted, in which case the laptop will lose it's IP.
Click to expand...
Click to collapse
Yes, absolutely. Could be the case. I did check the DHCP table this morning. But both PC and JJ had a new but different number.
Now however I could force another error, which again I never had before and happened on two different Linksys routers.
Looking at the Linksys status I see
Firmware Version: 1.45.10, Apr 15 2004
Login: Disable
LAN:
(MAC Address: 00-06-25-98-47-00)
IP Address: 192.168.1.1
Subnet Mask: 255.255.255.0
DHCP server: Enabled
WAN:
(MAC Address: 00-06-25-98-47-01)
IP Address: 0.0.0.0
Subnet Mask: 0.0.0.0
Default Gateway: 0.0.0.0
DNS: 0.0.0.0
My Static IP address has disappeared!. Also when doing the setup again (without giving it a confirming "save") I see "optain IP automatically, where it should be "fixed WAN IP".
Switching off and on the router, without doing any setup solves the problem. So no big deal.
I am afraid that my little Jasjar buddy is doing sneeky things with my router.
Huib
I see a somewhat similar problem here :
http://forum.xda-developers.com/viewtopic.php?t=33328&highlight=wifi+router
Close proximity interference? Maybe working wit a Mac address table could solve it?
I do use WEP however.
I am not such a heavy WIFI user with my JJ so I let it rest for a while.
Huib
Hello,
Yesterday I got a wlan/wifi enabled adsl modem/router for my broadband connection which uses telephone line. I wanted to use the wifi output given by the modem, for my ppc in my home for internet. Something like wireless home networking. As this is the first time, I don't know or I'm a noob. The security settings in modem are :
Network Authentication: Open
WEP Encryption: disabled
When I search wifi signal, My ppc detects the modem; Says connecting and after few mins says unavailable so it don't connects.
Here is the manual : Link
Please help................
Solved : The modem was setted to "Bridging" ( Manual Connecting ) and after setting it to "PPP over Ethernet (PPPoE)" ( Auto connect ), The internet in my ppc is working fabulous.
Thanks and regards
Ok, now my PPC says connected. When I assigned ip in network adapters->wlan setting ( SDIO WLAN Wireless Adapter ).
But another problem here, Cannot use the net. Mean, IE or weather report or IM don't connect to internet.
Is there any MAC filtering set on the box? Are you getting a genuine IP lease, or is it a Windows auto-configured setting (169.254.x.x)?
Just looked at the manual - other things to check:
Is NAT (page 48) enabled?
Is DHCP Server (page 55) enabled on the box with correct IP range, subnet mask and gateway IP?
Rock Kicker said:
Is there any MAC filtering set on the box? Are you getting a genuine IP lease, or is it a Windows auto-configured setting (169.254.x.x)?
Click to expand...
Click to collapse
Rock Kicker said:
Just looked at the manual - other things to check:
Is NAT (page 48) enabled?
Is DHCP Server (page 55) enabled on the box with correct IP range, subnet mask and gateway IP?
Click to expand...
Click to collapse
Hello,
Thanks for the reply.
First, It was auto configured IP setting so in my ppc it was not connecting but after assigning the IP ( IP : 192.168.1.2, Subnet : 255.255.255.0, Gateway : 192.168.1.1 ) the ppc says connected.
OK, I will checkout that NAT and DHCP.
Thanks again.
Hey buddy,
This is right down my alley, if you still need some assistance just pm me.
Hi all,
I have strange issue when connecting to my phone over my local WiFi network. I've searched the forum, but all hits are related to issues connecting to the internet over WiFi, which is working fine for me.
This is what's happening:
I have local WiFi-network (802.1n), protected with WPA2-PSK and a HTC HD2 running Android (FRG83D, 2.2.1). Whenever I connect over the network to the Internet, all is fine. However, when I want to connect from my Mac to my phone, the phone is invisible. It doesn't matter what kind of service I start on my phone (adbd, sshd, ftpd, wifi explorer) I always get an error host unreachable or host is down. However, when I ping from my phone to my mac, which is in the same subnet, after that all is fine and I can connect from my Mac to my phone without any issue. It's just frustrating that I always have to ping first from my phone to my Mac, to make sure it's visible to the rest of the network.
My setup: Wireless Router 802.1n connected to the internet, iMac G5 and 2 HD2's. Everything is working fine, except for connecting locally from my iMac to my phone(s).
I've tried whether obtaining an IP-address through DHCP would change things, I've setup fixed IP-adresses, currently my phone obtains a reserved IP-address through DHCP (based on MAC-address). I've rebooted the router, upgraded firmware. My iMac is setup to obtain an address the same way as my phones. DNS-entries on the client direct to the router as gateway, the router is setup with OpenDNS server addresses.
I think I've provided all info I'm able to sure and I would really like to be able to connect to my phones locally without having to ping first. Anybody here to shed some light on this?
Thanks in advance!
Sincerely,
Mac
About the only reason I can think of is some kind of arp cache corruption and/or duplicate IPs.
You are on the same subnet so nothing else should really be messing with connectivity.
See if the mac addresses are correct in your arp table.
"arp -a" should show you what is in the table, both on the phone and the Mac.
It'd be interesting to compare the mac address entry for your phone (if there is one) on your Mac, before and after pinging it from the phone.
If the connection only works after the arp cache populates, you can probably work around it by setting a static arp entry for your phone. This would fix things but not tell us why it's happening though
Hi dadewy,
Thanks for your reply. I followed your advise, with the following result. In my setup 10.0.0.1 is my router, 10.0.0.75 is one of my phone, 10.0.0.100 is my Mac connect by LAN, directly to the router.
On fresh boot (phone, Mac and router) arp -a shows:
On the Mac:
Code:
? (10.0.0.1) at 0:26:f2:73:cc:44 on en0 ifscope [ethernet]
? (10.0.0.255) at (incomplete) on en0 ifscope [ethernet]
On my phone:
Code:
? (10.0.0.1) at 00:26:f2:73:cc:44 [ether] on eth0
I noticed there's one 0 missing in the Mac-adress for the router (10.0.0.1) in the first result. After I tried to connect using adb (which resulted after several minutes in unable to connect to 10.0.0.75:5555) and ssh (which resulted, again after several minutes in ssh: connect to host 10.0.0.75 port 22: Operation timed out) from Mac to Phone , arp -a shows:
on my Mac:
Code:
? (10.0.0.1) at 0:26:f2:73:cc:44 on en0 ifscope [ethernet]
? (10.0.0.75) at (incomplete) on en0 ifscope [ethernet]
? (10.0.0.255) at (incomplete) on en0 ifscope [ethernet]
So, then I tried to ping from phone to Mac, which succeeded and changed the result of arp -a to:
on my Mac:
Code:
? (10.0.0.1) at 0:26:f2:73:cc:44 on en0 ifscope [ethernet]
? (10.0.0.75) at 0:23:76:cb:5b:47 on en0 ifscope [ethernet]
? (10.0.0.255) at (incomplete) on en0 ifscope [ethernet]
and on my phone:
Code:
? (10.0.0.100) at 00:1e:c2:0e:12:f0 [ether] on eth0
? (10.0.0.1) at 00:26:f2:73:cc:44 [ether] on eth0
After pinging from my phone, everything works fine. I can connect through ssh/sftp, adb you name it.
So I rebooted my phone, typed arp -a and apparently the cache was cleaned, because it showed only the router. From my Mac, without reboot, arp -a still showed my phone, and I was able to connect.
Until now I thought it had something to do with my phone, but apparently it's between my Mac and router, isn't it? I was unfamiliar with arp until today, but as far as I understand, it's a cache responsible for translating local MAC-addresses into IP's and vice-versa, correct? Should my router actively broadcast MAC-addresses throughout my local network, or what is it supposed to do?
Any ideas how to proceed? Thanks anyway for your time.
Sincerely,
Mac
Yes arp translates between ISO layer 3 addresses (IP) and layer 2 addresses (MAC).
This (on the Mac side) should fix your issue:
Code:
arp -s 10.0.0.75 00:23:76:cb:5b:47
Might need root (sudo) for that.
Note that this is a workaround and something is definitely wonky on your network (as evidenced by the "incomplete" arp entries).
This works like a charm Thanks for your help.
One more question: Can I just copy that line to .bashrc so it's run whenever I open a new terminal window?
Sincerely,
Mac
Open up Rom Manager and click "Fix Permissions" let it do its thing then restart. That worked for me.
Hi guys and girls...
I've just flashed MDJ's CyanogenMod7 v2.5 rom and now having trouble with my wireless network.
I can see the phone picked up an IP address and connects to the network. The phone says it has an IP address from my DHCP range.
When looking at the logs on the router, the IP address is not what I was expecting to see. The IP address I get is 178.104.241.159 - the MAC address is correct.
I don't understand this.
When I manually set up an IP address it it appears for about 30 seconds, I seem to get to google.co.uk but then when searching for something the page times out and the IP address reverts to a 178 address...
has this happened to anyone else?
Oh yeah, I'm using radio 2.10.50.28
Cheers in advanced...
hi, i just up My HD2 with TyphooN CyanogenMod 7 RC3+ v2.8.5 room and have issue with Wifi, It's not stable. anybody have solution for this issue ?
thanks
Name: customer61856.104.wv.cust.t-mobile.co.uk
Address: 178.104.241.159
you arent connected to the wifi by the looks of it as that ip address is not a local IP from your router it is your data connection IP
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