Having spent many hours trying to resolve this with Virgin Mobile (supplier) and Samsung UK (neither of which had a clue) on the Phandroid forum I've finally found a fix that works . If I could find my way back to the post I would give full credit here, but I can't until find it again.
The problem is with WPS. I opened the WPS settings and on the (Belkin N+) Router main menu followed: Wireless - WiFi Protected Setup & found it 'Enabled'.
On the phone I went to Settings - WiFi and on the 'WiFi Networks' page selected hard menu key which gives the option 'WPS PIN Entry' and provides a PIN number to put into the router. Once I'd done this the phone connected immediately.
Once I'd done a bit of Googling I couldn't see any good reason to have WPS enabled, I've even found on line several posts that say it's a security liability when enabled, so I've switched mine off. It seems to have made no difference whatsoever to my other laptops, phones etc.
Perhaps someone on here could indicate to me if, why and what issues I may have set in motion by switching it off.
I hope the fix works for you!
Wi-Fi Protected Setup (WPS; originally Wi-Fi Simple Config) is a computing standard that attempts to allow easy establishment of a secure wireless home network.
Created by the Wi-Fi Alliance and introduced in 2006, the goal of the protocol is to allow home users who know little of wireless security and may be intimidated by the available security options to set up Wi-Fi Protected Access, as well as making it easy to add new devices to an existing network without entering long passphrases.
Prior to the standard, several competing solutions were developed by different vendors to address the same need.
WPS has been shown to easily fall to brute-force attacks.
It seems WPS has been cracked (design flaw - it accepts repeat PIN attempts, and lets you know when you've got the first 4 right).
I'm no expert by the way - just got this from browsing (also found a download link for the hacking software very easily!).
A major security flaw was revealed in December 2011 that affects wireless routers with the WPS feature, which most recent models have enabled by default.
The flaw allows a remote attacker to recover the WPS PIN in a few hours and, with it, the network's WPA/WPA2 pre-shared key.
Users have been urged to turn off the WPS feature, although this may not be possible on some router models.
Thanks Raistlin - I'd seen something similar about the security issues. I don't understand why it is that, with WPS enabled by default for years, this is the first bit of kit that's had a problem connecting to it. It's bizarre and only compounded by the lack of knowledge of the problem by any of the agencies involved in providing the phone - Samsung, Google Android or Virgin Mobile. It's very, very annoying.
Related
I just purchased the Tilt and love the features and possibilities, however I may be forced to return it if I cannot solve this problem.
I can connect the Tilt to my home WiFi network (Open/WEP) without any problems, and I can connect to several other APs (Open/Encrypted and No-Encrypt) without any problems.
In my office (where it'll be used the most) we use Cisco's lightweight access points with the WCS controller system. This system is configured with Open authentication and no encryption, and has a captive portal that you must login to in order to gain access to the network.
When I connect to this network, I stay connected for about 30-45 seconds (I can ping the Tilt from my wireless laptop for about that long), and then the Tilt stops responding on the network. The WiFi status says that it is reassociating with the network, but it never does. I can manually tell it to connect to the network, but that fails, too. While this is occurring, I can see all of the SSIDs (including ones not on the Cisco controller) that are available in our office, but cannot connect to any of those, either.
After a soft reset, I can connect to any of the other SSIDs with no problem until I try to connect to any of the SSIDs that are on the Cisco controller. After trying that, it repeats the same pattern and I must reset the Tilt before it will connect to any other access point.
I've actually done some wireless captures and cannot see any problems with the communication between the Cisco APs and the Tilt. It's just that after this "malfunction", the Tilt will successfully perform the normal 802.11 open-mode authentication, but will never proceed to the association phase.
I've talked to AT&T and HTC, and they told me my phone may be defective and to try a new phone. I've done that now, but it is still doing the same thing.
Has anyone had any similar experience?
Thanks!
This was a similar issue with my phone[Similar by reassociating with network, and soft reset], except it was on a campus[uses cisco] and not office! Basically i just had to register my kaiser's mac address with the school, and everything worked perfectly. Hopefully this helps!
That's an interesting observation. A campus network would be similar to my (large) office network.
Before you registered your MAC with the school, were you able to browse to anything?
I ask because our network doesn't require MAC addr's to be registered. It allows anyone onto the network as a "guest" and then you have to browse to a web page that lets you login to get Internet access.
But, the fact that you had to do a soft reset to get it working again is quite interesting, and points to a bug with WM6 or the device.
The Cisco WCS has some protection against DoS/etc. Maybe the tilt is doing something that's causing the WCS controller to think your device is a bad-guy and it places you on a blacklist. I think by default the WCS has a blacklist timer of about 5 mins... can't remember now. Could be what's happening though if after a reset you can't see the WCS SSID anymore.
That's a great point, too. We don't have any of the IDS/IPS functions that you're referring to turned on, but there's always those hidden features
We ran a quick test and watched the debug output of the WCS and didn't see any messages to indicate foul play.
It turns out that this problem was specific to Cisco's WLAN implementation. Cisco has a set of wireless extensions called CCX that are implemented on wireless devices (clients) to aid the infrastructure in managing the radio environment, location management, roaming, etc.
Apparently the WiFi chipset and/or drivers on the Tilt do not implement CCX (as 90% of other radios and drivers do), so when the WLAN sent a broadcast out asking for radio management reports, the Tilt's WiFi stack would just freak out.
We were able to work around this by disabling the CCX Location Measurement function in our Cisco 4400 series WLAN controller.
It would be nice to see an update from AT&T and HTC to fix this problem.
same thing happened to me.. same cisco wlse and same pda.. i also have to disable CCX. but it is quite useful feature of WLSE. i hope htc can fix it.
knoll said:
It turns out that this problem was specific to Cisco's WLAN implementation. Cisco has a set of wireless extensions called CCX that are implemented on wireless devices (clients) to aid the infrastructure in managing the radio environment, location management, roaming, etc.
Apparently the WiFi chipset and/or drivers on the Tilt do not implement CCX (as 90% of other radios and drivers do), so when the WLAN sent a broadcast out asking for radio management reports, the Tilt's WiFi stack would just freak out.
We were able to work around this by disabling the CCX Location Measurement function in our Cisco 4400 series WLAN controller.
It would be nice to see an update from AT&T and HTC to fix this problem.
Click to expand...
Click to collapse
Anyone know if a new driver is part of WM 6.1? I am holding out for the official AT&T version but was just wondering since I have this problem with the wifi at school.
Hi,
I'm a SysAdmin and usually can figure out stuff by myself but I'm at a loss here, I feel like I've literally tried everything.
Hope you guys can lend a hand - I've also asked the CyanogenMod community here: forum.cyanogenmod.com/topic/8830-nexus-one-cant-connect-to-any-wifi-networks/
I've just received a replacement nexus one and it just won't connect to ANY Wifi networks (I've tried 3 different ones).
I know for a fact that my previous phone connected without any issues and we have several other wireless devices here that work fine (Printer, iPod, Laptops..)
Behavior:
- After resetting Wifi (disabling, re-enabling), it will scan for networks, it will detect my home network as well as several around my house properly.
- My home network is secured with WPA2, I select my network and put in my passphrase
- It will say "Connecting..." for several seconds then it will go back to "Disconnected" and eventually it will start scanning again for networks.
It seems to be the same issue as several people are experiencing here:
66.102.11.100/support/forum/p/android/thread?tid=63fcb1171110570e&hl=en
Several notes:
- Wifi signal is at 4 bars (maximum)
- It will show my home network as remembered once I have attempted one connection
- As soon as the connection fails (falls back to "Disconnected"), my home network goes Out of Range (!?)
- MAC address is definitely entered correctly in my router's MAC address filtering
- Tried restarting router, modem
- Restarted phone, restored it back to factory settings (tried a factory reset via Fastboot and via AmonRa Recovery)
- Tried with default android 2.2 firmware, Cyanogenmod Stable (2.2) and the latest nightly (2.2.1)
- Tried "Wifi Fixer" (Installed via USB)
- Out of the three networks I've tried, one was open and the two others were WPA
Another thing I've tried is setting up a static IP address.
It gets kind of odd here - my top status bar will start showing the icon as if I would be connected to a Wifi network and if I go into "Settings -> Wireless & Networks", it will say that I am connected. However, I'm not connected to any network (eh?).
I've done my best to browse the filesystem for logs with the terminal emulator cyanogen provides but I don't really know the layout of android. If anyone can point out a path, I can pull out some logs for you.
So, any ideas ?
I too have the same issue but unable to solve it
if you find any answers please let me know too
Judging by several ROMs that have been unable to cure your issue - it looks to be HW issue rather than SW one. There are plenty of reasons why the protocol would fail authentication, and the symptoms you're describing fit exactly how would Nexus behave in case of failed network negotiation. The problem is that failed network negotiation can occur if all the networks are protected by MAC access filter which doesn't recognize your MAC, but it's not your case - so it might be some other negotiation failure, which might be HW-related.
Jack_R1 said:
Judging by several ROMs that have been unable to cure your issue - it looks to be HW issue rather than SW one. There are plenty of reasons why the protocol would fail authentication, and the symptoms you're describing fit exactly how would Nexus behave in case of failed network negotiation. The problem is that failed network negotiation can occur if all the networks are protected by MAC access filter which doesn't recognize your MAC, but it's not your case - so it might be some other negotiation failure, which might be HW-related.
Click to expand...
Click to collapse
Do you know if Android logs events or errors ? I'd really like to know why it fails.
fooraide said:
Do you know if Android logs events or errors ? I'd really like to know why it fails.
Click to expand...
Click to collapse
adb logcat
Or install alogcat from market..
If you're rooted, you might be even better off dumping /proc/kmsg
Even though you say the MAC address is entered correctly, I would turn MAC filtering off at least temporarily just to be 100% sure something funny is not happening.
I've also had problems with hidden SSID, might broadcast it temporarily if its in fact off
crachel said:
Even though you say the MAC address is entered correctly, I would turn MAC filtering off at least temporarily just to be 100% sure something funny is not happening.
I've also had problems with hidden SSID, might broadcast it temporarily if its in fact off
Click to expand...
Click to collapse
Tried turning MAC address filtering off but no go - I doubted this could had been the issue since my device can't connect to an open network either.
The SSID broadcast isn't the issue either.
I'll try and look into the logs later tonight and see what I can dig up (thanks to those who hinted at how I could look them up)
Hi,
I'm trying to connect to a WiFi network that is protected with WPA2 with PEAP / TTLS.
It simply is not working. No problems connecting with my HTC Desire though.
Anybody experiencing the same bug? I already installed the required root certificates, tried various combinations of user account / password. The thing is, that the network is provided by my university (Eduroam if you are familiar with that) and it is very annoying that I have to fall back to HSDPA consuming my data quota.
Cheers,
chross
Normally with eduroam wifi there isn't wpa2 or other key. Just connect your phone to it, open your browser and you will be redirect to the website of your university and then you can log with your id.
Envoyé depuis mon XT890
Yes!! This is the exact same problem I'm having with my university wifi
http://forum.xda-developers.com/showpost.php?p=33962871&postcount=2
I'd configure the settings on my uni wifi choosing PEAP and then MSCHAPV2 and put in my log in username and password according to the instruction and as soon as press connect or save it looses the signal immediately to very low and never connects. We also have eduroam as an alternative they tried that and same problem just doesn't want to connect.
It works perfect on my htc one x. I'm beginning to believe the phone has a bug.
It does have a bug. It doesn't connect to 802.11 n!
My problem was solved by reconfiguring my AVW Fritz!Box 7270 to 802.11 b+g only and limit the phones wifi frequency to 2,4ghz only. You can find that in advanced wifi configuration.
I'm lucky i only recognized this bug in my own wifi network and not others i don't have admin rights for...
eduroam works for me with PEAP/TTLS but I guess it's 802.11g
I'm on the 40002 rom, but worked also on the 31006
After receiving the 4.0.4 update yesterday, WiFi now works flawlessly.
Cheers,
chross
Hi there,
I got the same problem with my university network in hamburg. I updated the razor to android 4.0.4 (Stock-Rom: 81.5.40002.XT890.Retail.en.EU), also the phone is rooted but still not working. Our IT advices to use WPA2 Enterprise TTLS/PAP authenthication in combination with a t-com root certificate. Every time i safe these setting the wifi signal drops as told by previous posters and the connection fails. When i enter the settingspage again, all settings are reverted to default. This also happens, while trying to connect to eduroam
any further advices?
Thanks in advance!
I have no problems connecting to eduroam at Braunschweig and other citys. Maybe you can visit the IT Desk at your university?
jagwar1 said:
I have no problems connecting to eduroam at Braunschweig and other citys. Maybe you can visit the IT Desk at your university?
Click to expand...
Click to collapse
Yep, me and and a fellow student went there and told them about the problem. But they also gave up, after trying about an hour or so. It seems to be a general problem in the used android build, at least there are a lot of post reporting this at the google code repo -> code.google. com /p/android/issues/detail?id=15631 (sorry for that but I'm to new here to post links). I'll try the provided tips like changing the wpa_suplicant file tomorrow and report the results. Seems to be strange issue, if it works for you (and probably others), because a fellow student got the same Phone and has the same issues
Thought I'd just give an update as I have the same issue
Motorola knows about it, it's been reported to them before and said it'll be fixed with the next update.
Working smooth here with WPA2-Enterprise, PEAP and MSCHAPv2. Using it every day.
But I'm not using TTLS, you might want to disable that if you don't have a valid certificate for your mobile/user.
Also important, fill out the "anonymous user" field with your username. Depending on the RADIUS configuration of your IT this might be required.
[edit]
Just checked my mobile. I don't use a Phase 2 authentication, only EAP = PEAP, no certificates.
Got it working!
After 2 hours of searching the web and playing around, I got it working now, following this guide posted on google code repo:
Razr I (XT890), retail eu, running android 4.0.4 (stock), no root
after endless hours of trying i was able to connect to my university network a couple of minutes ago with the combination of two apps.
1. WiFi Connection Manager
Enter SSID manually
Security "802.1x EAP"
EAP Method "PEAP"
Phase 2 authentication "MSCHAPV2"
Identity "your identity"
Anonymous identity "your identity"
password "your password".
2. WiFi Advanced Configuration Editor
Check Hidden SSID
Key Management: unselect IEEE8021X, select WPA_EAP
AUTH Protocols: select LEAP
Enterprise configuration: make sure Identity and Anonymous Identity are set to your identity, Enter your password
check whether the settings are saved in WIFI Advanced Configuration Editor. If not switch of stock WiFi and repeat step 2 (!!!). Now it should work.
Turn WiFi on and connect to network (Stock WiFi; don't care about settings there, phase 2 authentification is still not saved)
After switching the device off and back on it did still work. Same when leaving and returning to WiFi area.
hopefully it will keep on working. i just tested the browser and play store. didn't discover any problems so far.
Click to expand...
Click to collapse
Connection is stable, but there seem to be some problems regarding to the speed. Whatever it's usable for stuff you do regularly @university.
Hope that helps others, thanks to klemens
hey.qb said:
Hope that helps others, thanks to klemens
Click to expand...
Click to collapse
Thank you for sharing, this made me so happy!
It's those two apps which made my connection possible.
My eduroam configuration is quite different, but the apps did the trick. I fiddled with advanced wifi config editor alone for hours without any result.
Now I just hammered the config into those two apps and what can I say - proxydroid reported a connection a few seconds later.
I dont't know what Moto's Problem with 802.1X is.
Defy latest stock rom - no connection. With CM -> no problem.
Milestone 2 with stock rom - no connection. With CM -> no Problem.
Rarz I no connection with stock wifi manager . . .
My fellow students with their samsung devices seem so have no problem at all. ^^
(even Win Mobile 6 works, thats a little bit depressing)
btw, speed is fine here. 16Mbit up&down is more than I need on a phone.
Greetings from Kiel.
Hi guys,
I was extremely happy with my shiny new Moto X (2nd Gen) (UK), which arrived on Monday, however I am since less pleased as I cannot connect to my office WiFi!
All other WiFi's are fine, but for whatever reason I CANNOT seem to connect to my office WiFi.
I have tried every single setting and the only conclusion I can rationalise is that it's because the SSID is hidden and the Moto X (at least my one) has a problem with this. I've tried restarting the phone, factory restored the phone, asked sysadmin to reset the router, tried changing WiFI Direct name, turned on "WiFI Optimisation" etc.
Nothing works. It just says "Saved, secured with WPA2". Every other device in the office works fine.
There is no MAC filtering and plenty of DHCP licenses available.
What kinda odf crap phone can't handle hidden SSID's? Also, Motorola support is a pile of crap! Been waiting to speak to one of them for 1 hour.
Anyone have any ideas?
Thanks,
TD
I'm connected to my office WiFi with hidden ssid...
So why can't I?!?
Apparently someone told me that hidden SSID's is a violation of the Wi-Fi protocol and hence is not supported in Android/Motorola devices. Guessing that's the reason why apps like: https://play.google.com/store/apps/details?id=jp.sourceforge.soopy.hidden.ssid.enabler&hl=en_GB exist..?
On the other hand, it seems like bullcrap if you and other can connect to hidden networks just fine?
No one know or have any advice on this issue?
Thanks,
Z
I don't now where you're problem is coming from but I swear I'm connected each work day on a Wi-Fi network with hidden SSID. But : when I have configured it for the first time my moto x was telling me that WiFi network was not reachable. Just waiting 5 minutes and voila, moto x was connected. It was exactly same situation with a nexus 5 on same WiFi network.
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
So configure it, and then wait 5 minutes and see if it is now connected. Put your WiFi in always on mode even when idle.
Mine just says "Saved Secured with WPA/WPA2".
Just won't connect!!
Go to wifi settings scroll down and hit
ADD NETWORK
Next enter the ssid exactly it is case sensitive.
Next enter password.
If it doesn't connect then your works wifi may have Mac address filtering on.
In that case you have to have the I. T. guy manually allow you in.
Hope that helps
Nd8 deodexed Rooted and modded
As mentioned there is no Mac filtering and thus isn't a dhcp capacity issue. Everything is fine. All other devices including other 4.4.4 devices are connecting without issue.
Any other ideas..
Is it 2.4 or 5 GHz WiFi? Have you enabled both?
Not sure what band, but doubt that's the issue as works on both bands at home.
Using a great tool called "WiFi Connection Manager" from the Play Store, you can see the following network settings:
Interesting to see what the alert says when clicking into it:
Any ideas? Thinking it could be a Cisco hardware related issue!
Z
Interesting... Using google I can found a lot of people that have same problem as you. But... Hidden ssid is only for bad admins that still think this will protect them
Yeah but it's no excuse for Android and/or Motorola to not play nice with hidden SSIDs. This in my opinion is VERY poor.
It's not moto but android. But since 802.11 have never been designed to work with hidden ssid I don't know if we can complain about android. But I'm not an expert on this subject, so maybe and hopefully someone can explain us in a more detailed manner.
That would make sense if I hadn't been able to use other Android 4.4.x devices and versions to successfully connect to the same network..
I missed that point... You're right if other android devices are able to connect to the same network then it is probably a moto problem... But mine is working good with hidden ssid but the router is not a Cisco one. I suggest to contact moto support by chat ( not by phone ), you should have an answer.
Cisco router? Make sure it is on the latest firmware. There appears to be an issue with older Cisco firmware and the X, independent of broadcasting of SSID.
https://supportforums.cisco.com/dis...isco-controllers-and-pmf-enabled-moto-x-gen-2
Gents,
I have been using my Nokia 8 (T-Mobile service) wiFi tether to connect to a game on Fantasy Grounds for some time, but just recently have lost ability to do so. (Despite the fact that I can do all other things internet while tethering to my Nokia 8)
This was around the time I installed the February security patch, but I'm not 100% that caused the issue.
Also around that time I was working with TMOUS customer svc to address an issue with my phone constantly disconnecting from mobile data (Solved by manually entering APN data).
I have been able to access the game via my wife's Samsung J8 (same service provider) tethering to the same computer, so feel fairly confident that the issue is within the phone, not settings on my laptop.
Fantasy Grounds tech support doesn't seem to know how to address the issue, so I'm posting here.
I'm not sure, but I think I need help with changing whatever firewall settings the phone may have (I have no third party firewall apps installed), or if I need to adjust something within the APN settings I manually entered.
Thanks in advance, I appreciate any help I can get here.