NyQuil Kid
8f The Nyquil Kid
join:2001-01-06
Brick, NJ
 ·Comcast
 ·Verizon Online DSL
2 edits | ActionTec MI424-WR Firmware and WPA issues
Hi there:
Anyone else using the MI424-WR Actiontec router with the following firmware:
Firmware: 4.0.16.1.56.0.10.7
The problem is that any Vista computer can't connect to a wireless network using WPA-PSK...when using WEP, it works fine.
This is similar to another issue whereby a SONICWALL router would not handle DHCP requests properly with Vista PC's - a firmware update fixed the issue in that case.
Anyone else running into this issue?
Thanks!
[8F] The NyQuil Kid
--
[8F] The NyQuil Kid comes into town not looking for trouble...
n00bz gang up, but he ain't seein' double,...
pulls and draws, his deagles two...
n00bz litter the ground you know it's true. |
|
N O Y B
St. John 3.16
join:2005-12-15
Forest Grove, OR
2 edits | Make sure both router and computer are set to the same version WPA-PSK or WPA2-PSK as well as both set to the same encrypton algorithm TKIP or AES.
Make sure the PSK is correct with no typos etc. such as begining or trailing space.
Make sure the WiFi radio is turned on.
--
Be a Good Netizen - Read, Know & Honor Your ISP Terms of Service
Comcast: »www.comcast.net/terms/index.jsp
Verizon: »onlinehelp.verizon.net/consumer/···0707.pdf |
|
NyQuil Kid
8f The Nyquil Kid
join:2001-01-06
Brick, NJ | Already checked that - no go. |
|
cgeek5467
cleckjr
join:2003-08-30
Trenton, NJ | reply to NyQuil Kid
Already another thread about this
»Actiontec and WPA: problems connecting
Search is our friend  |
|
kyler13
Is your fiber grounded?
join:2006-12-12
Arnold, MD
| reply to NyQuil Kid
Yeah, I started that thread cleckjr referenced. It's definitely a problem with the current firmware. It's specific to just WPA. Not sure if it's hardware and OS specific, but I have the problem you have and I'm using Vista. Two ways around this. If you want to return to the way it was meant to auto-connect, roll back your firmware to the last version. Hopefully it'll get fixed by Actiontec soon since Verizon likes to push the latest firmware to your router weekly. If you do roll it back, you'll have to do this weekly (you'll know when it's pushed because your laptop stops auto-connecting). The other option is to use the faulty "latest" firmware. You can ultimately force the connection over WPA by pulling up the connections list and constantly refreshing the list (the little button on the right side with the two blue arrows) until it finally acquires the connection. That's annoying and can sometimes take up to (maybe even more than) two dozen refreshes. |
|
almahix
Allegro ma non troppo
join:1999-10-18
Camarillo, CA
 ·Verizon FIOS
| reply to NyQuil Kid
I just checked and I have fw version 4.0.16.1.56.0.10.7 and my WPA-PSK devices are able to auto-connect to the MI424-WR, no issues. One is Win XP home, the other is Windows Mobile 5.
I don't have Vista so I can't be sure uf that is the issue, but a friend of mine bought a new laptop with Vista, and he can't auto-connect to his Linksys router. He can manually connect, however. |
|
Alan 99
@nsa.gov
| reply to NyQuil Kid
After operating flawlessly for nearly a year my wireless network crashed while I was on vacation in late January. It won't work any more with WPA-AES - it complains that the password doesn't match. I have reset the password (both on the router and on my Vista laptop) several times but still no satisfaction. I had to revert to using 128-bit WEP encryption on my network. I suspect that Verizon downloaded a buggy firmware load to our routers sometime in the period 20-29 January that clobbered WPA. I guess all we can do is wait until they replace this load with a corrected one. |
|
anon265
@verizon.net
| reply to NyQuil Kid
I'm glad a thread exists about this that I found on google. I downgraded my firmware, but I still have WPA issues.
For what it's worth, I set my DHCP lease time to just 60 minutes, and that seemed to help. I haven't had any problems yet (knock on wood).
Those of you who are having this problem recently, call Verizon and get your router replaced to a newer one. I can't because I don't have FIOSTV, where the router is pretty much infinitely warrantied, and the tech said my router's warranty ran out after 1 year of getting it. |
|
Rattler
join:2001-04-13
Havertown, PA
·Verizon Online DSL
·Verizon FIOS
| anon...
You could go out and get a Linksys or D-Link router and just replace the A/T. I know that's not the way things SHOULD work but at least you would have one that "probably" would not have WPA WLAN problems. Of course, if your internet is delivered via coax from the ONT, then my suggestion wouldn't work.
Replacing with a newer A/T router may or may not fix the problem since the firmware gets bumped up at V*'s whim and could work today but not tomorrow. Not really a complaint, just a statement of fact.
--
Never raise your hands to your kids. It leaves your groin unprotected. -- Red Buttons |
|
rocky01
Premium
join:2002-04-24
NE
4 edits | reply to NyQuil Kid
Definitely an issue. Mine was solved when I rolled back to .43 firmware. That means you'll have to close backdoor and also edit your configuration file as found in these pages, so that there is no forced upgrade. I would expect VZ to fix the Vista problem by the time next firmware is released. My fingers are crossed that this happens soon, since I'm not necessarily adverse to new firmwares, although I have some issues with *forced* upgrades, especially if they cause problems. If interested I would also suggest getting newer revision of ActionTec so as to take advantage of WPA2. |
|
Rickeo
join:2008-01-26 | reply to NyQuil Kid
Just chiming in because I am using WPA2 Personal wonderfully. My MI424WR is a Rev. D with the 4.0.16.1.56.0.10.7 firmware. I have an iMac and Macbook both connected with WPA2. Don't know if that narrows down what the issue could be. |
|
JonathanA
@verizon.net | reply to NyQuil Kid
Does anyone know where to find firmware version 4.0.16.1.55.0.10.4.3? The link in the thread mentioned does not work. |
|
noping
no route to host
Premium
join:2007-01-09
·Verizon FIOS
| »Re: XBOX 360 and FiOs(Actiontec M1424WR)
Use at your own risk (firmware not hosted by Verizon)
--
$ sudo rm -rf / |
|
cgeek5467
cleckjr
join:2003-08-30
Trenton, NJ
| A few weeks back, I posted on the Direct Forum about issues with firmware 4.0.16.1.56.0.10.7.
Haven't heard anything so I asked for an update.
I was told that ActionTec has confirmed that there are no issues regarding WAP encryption with firmware 4.0.16.1.56.0.10.7.
The suggestion is to manually update the firmware -- maybe the auto-update was corrupted. And if that doesn't work, then there must be a problem with the router and a new one with the firmware already installed should be swapped in.
Anyone else told the same thing?
I could maybe believe that this version of the firmware is not working properly with my version of the hardware -- version A. But, that is not what I think they are saying.
I'll probably happily stay on the old version of the firmware ... |
|
rocky01
Premium
join:2002-04-24
NE
1 edit | Even if you get a new ActionTec with .7 already installed my guess is you too may have trouble with Vista computer connecting, for example, and most likely will have the issue solved if you roll back to .43 firmware. And since other users have several other issues discussed in these pages, I think they will end up releasing something new in order to take care of these problems in near future. I'm looking forward to it at least. |
|
buffalox4
@verizon.net
| reply to NyQuil Kid
I was trying everything from buying a new lap top card, to trying to bridge my Action Tec router with my Linksys router with no success. I even tried talking to the Verizon tech team explaining my computer is having trouble identifying the Action Tec router. Since the issue was intermitting they blamed my computer. My last attempt was to roll my firmware back to version 4.0.16.1.55.0.10.4.3. BINGO no issue connecting to the Action Tec router. Reminds me of the old days when I was using my Linksys router and never never never had issues identifying my router!!! Now my only concern is Verizon updating my router with new firmware. Last, Using WPA – PERSONAL TKIP  |
|
NyQuil Kid
8f The Nyquil Kid
join:2001-01-06
Brick, NJ
·Comcast
·Verizon Online DSL
1 edit | This demonstrates how utterly useless 1st line tech support is - one would hope the help desk manager would encourage techs to read forums like BBR to keep informed of such issues. Honestly, one needs the patience to Job himself to deal with such a lack of in-depth knowledge and initiative.
[8F] The NyQuil Kid |
|
Kevin210
join:2008-02-19
Lynnfield, MA
| reply to buffalox4
I don't think Verizon goes around uploading firmware with an open port. What I think is the router itself checks and upgrades when needed. I'm using 4.0.16.1.55.0.10.4.3. Try going to advance-> firmware upgrade and change the web address to something else so it can't check. Just add a couple of letters so the router cant connect to Verizon's site and check. Worked for me. |
|
bfrederi
join:2004-05-06
Burlington, MA
1 edit | reply to NyQuil Kid
Thanks to the earlier posters for confirming that there is a problem.
I had FIOS installed a couple of weeks ago with an MI424-WR running FW 4.0.16.1.56.0.10.7
I'm running XP, not Vista, and although I can autoconnect okay, and use the connection for periods of time, the status shown on my Dell Wireless WLAN Card Utility diagnostics page never goes from "Authenticating" to "Authenticated", and eventually it times out after a couple of minutes. (Oddly, the Windows Wireless Network Connection Status window *does* show a status of "Connected" while the link is "authenticating", and the link is operational.) Then it reconnects, works for a couple of minutes, times out, and so on, ad nauseum.
Fortunately, I still have the Linksys WAP that I had with my Comcast service, so I've just reconnected that to one of the MI424 wired ports.
I thought it was odd that the MI424 admin interface didn't offer WPA as an option up front along with the WEP settings. Makes me wonder if they knew that WPA had problems and they didn't want techs or customers casually enabling it.
[Edited: 080327 9:45 AM EDT -- corrected my observations regarding "authenticating" and "connected" states.] |
|
Shrapnel64
Premium
join:2001-01-24
Hayes, VA
·Verizon Online DSL
·Cox HSI
| reply to NyQuil Kid
It has been my experience when changing the DHCP Server IP Scope from 192.168.1.2 to 192.168.0.100 that wireless clients will not connect, nor will wired clients connect.
Apparently, there is some other bug in their router where you must use .25 as your first available IP Address or it will not let clients connect to the router unless you manually specify an IP address for each client (in which case it is not using DHCP).
I don't know if this information will help any of you out there, but that was one of the problems I had when configuring the router for the first time. |
|
