Comments for PF Hyper Blog
I hate having to spend $60 or so $$ to fix something that should work by default. I think Apple will fix this eventually.
To work around the problem I was seeing (http://www.haloscan.com/comments/pfhyper/
3444963414945836078/?src=hsn#421427), I changed the Actiontec to bridging mode and installed a Linksys WRT54GL running X-Wrt. I haven't encountered any problems since the change.
The latest security updates for OS 10.4.10 should solve the connection problem with Actiontecs. I believe it was the one dated 7/31 that actually fixed it. I had to turn off WPA encryption to get it to work. I've notified Apple of that problem.
I have exactly this problem and I have to say - it's rather inconvenient if you rely on the web for work to wait on Apple and/or Actiontec to fix this problem. Do any of the other Actiontec wireless gateways have this problem? Qwest has three different Actiontecs that they supply to subscribers. Is that a fix? I'm desparate here.
I just opened a bug report with Apple. Thanks for recommending this Jeff.
To report bugs, you have to join Apple's Developer Connection but they have a free level of membership.
I've opened a bug report with Apple (and recommend EVERYONE who has problems with the Actiontec do the same thing!)
Apple asked me for information regarding the wireless, though, and now I can't update my ticket.
So I'll call Apple to see if they can update it, or I'll have to return to the "genius" with two working laptops (and a MacBook) to "prove" to them that there's a problem with the MacBook.
Again.
As noted previously, I tried WPA encryption with no luck. I'll check my firmware and report on that but I did look around for updates once and Qwest didn't have any.
Qwest and Actiontec know about this and are supposedly working on it.
I'm seeing a similar problem here. Qwest DSL with local ISP, Actiontec GT701-WG running firmware version 3.60.1.0.4.1 configured for 40 bit WEP(Yes, I know WEP is insecure). My Thinkpad X40 running Fedora Core 4 has no problem connecting. A G3 iMac running 10.2.8 has to be manually reconnected after sleeping, but otherwise works fine. A new Macbook Core 2 Duo running 10.4.10 will not connect to the network.
My next step is to try a Linksys WRT54 and see if that cures the problem.
No solution here yet. I haven't tried setting the ActionTec to default factory settings but that's probably next.
I have another wireless system I can log too so that's an interim solution for me but I do want to get this working again. Hoping Apple will update and fix.
Rolling back to 10.4.9 seems to fix it. I haven't had time for that.
Another potential solution is purchasing another router and bridging that to the Actiontec. Linksys seems to work for my MBP.
I now have the same problem. Macbook Pro, Actiontec DSL modem, OSX10.4.10. Has been working fine. Now cannot link to the Actiontec though it can to other wireless hosts. Solutions?
It's a straight connection issue with the wireless router and it's not signal strength. It connected with my Actiontec until the 10.4.10 update. Now it doesn't although it does connect to other wireless systems and routers such as Linksys.
I tried WPA encryption and that didn't work. On the Apple discussion forum, someone mentioned setting the Actiontec to default factory settings and that got it to connect. That may be my next strategy.
We've seen some connection problems with Macs that were the result of a bug in Safari, which prevents it from communicating with some gateways. If this is the issue, users can get around it by logging in using Mozilla or another browser. Once logged in, you can switch back to Safari.
Of course another potential problem is that you aren't close enough to the access point or have a strong enough wifi transmitter to talk back to the access point. In short, you can hear it, but it can't hear you; it's like a conversation where the other person has a megaphone. To troubleshoot whether it's this problem, you'd either need to test with a stronger wifi card or move closer to the access point.
Commenting by HaloScan
