When the hell is Apple gonna fix the Wireless problem in Leopard?!

[Mlobo01]

Update and an old hint...

The connection had no problems, when I would put it to sleep and wake it up it would find the appropriate network, except when the computer went to sleep on its own, then upon waking it, it would not find the network, there was something else missing, since we all have narrowed down that one of the connectivity issues (Wire and wireless) is due to a firewall anomaly It actually made me remember that early Panther 10.3 had a Firewall issue as well, we could not alter the firewall settings and ports because the feature was locked or greyed out, so in a forum like this one it was figured out that Panther had by default 2 firewalls active: (ipfw) and the one from Sys Prefs, this little bug could of creeped out again in Leopard, so I managed to input in the Terminal App the following command:sudo ipfw flush , entered my password then input y for yes. this flushes any rules set by the 'other' firewall, This could of been creating conflict by blocking the router's connection protocol. If we set rules with one it would be difficult to set rules for the ipfw that I believe it only accesible through Terminal, ipfw as we've seen in Console still has it own log file. After I did the flush command I restarted and tested to see if it retain the connectivity, then when the computer fell asleep on its own, it did reconnect to my network!, after several restarts it connected and when I put it to sleep manually it reconnected also. I wont cry Voila just yet, but I would like to read of others trying these hints.

 

[Mlobo01]

Overnight...

I left the computer to sleep on its own, and this morning my mini lost connectivity, I went to test my laptop and it picks up my network instantly.
So im back to square one but I do feel that answer is closer than before.

 

[Plymouthbreezer]

When Airport Scans, I still get mouse spazzes. Kinda annoying.

 

[Mlobo01]

logs...Firewall Logs...even worse...

my firewall log read:
12/20/07 8:41:13 AM com.apple.launchd[85] ([0x0-0x30030].com.opendoor.doorstopx[370]) Exited: Killed
12/20/07 8:42:13 AM Spotlight[92] Invalid kMDItemPath for DoorStop X 2.2

This was a leftover from a Firewall app called DoorstopX, that I deleted when I was troubleshooting the connectivity issue, under the library>application support I found the Doorstop deamon, this even when thhe app is trashed it keeps on working, still theres no proof that this makes the connectivity crash but I wanted to test it in a non-contaminated manner so I left the computer to sleep on its own, it went to sleep and it reconnected fine, this test was after I deleted this deamon, now im back to test mode, I will let it sleep again, go to work and when I get back I'll see if it reconnects and see if long term sleep affects it, it could be that upon self-sleep it does not log out the connection, thus causing the drop.

 

[Mlobo01]

General commentary...

I've been keeping up with this issue and I've been also tracking the Apple Supports forums as well, I believe that the issue is starting to point out towards Leopard's hastily designed Firewall, the combination of System Preferences not retaining settings and configurations, the Utility Disc App that seems that its been dumbed down in this iteration, unable to fix certain permissions therefore bugs and anomalies never go away, the inability of Leopard to discard old caches that truly affect system performance, the ipfw (a secondary Firewall?) which I believe is an old Panther app and bug that's back?, A Keychain Access App. that maybe prone to errors, my laptop is different, why? could it be that the intel version of Mac OS X has slightly more glitches? you also need to remember that Apple is new at developing for intel processors, and its a good possiblity that they may have overlook a lot, so be patient and see if the upcoming update can resolve our woes or if collectively we can come to various solutions.

 

[Silverbird0000]

I am using an Apple Airport Express router and multiple macs running Leopard, some that came with it and some that were upgraded. The network is secured and I have no problems downloading big files. I don't have any problems at all.

 

[Mlobo01]

the invisible culprit...

I had a reply from the Apple Support forum that confirmed for me that Leopard indeed has a secondary Firewall, The Infamous ipfw! the same one that showed up in panther, well it occured to me that if its set to a default setting how are we to now what it denies or allows access to? your router's ip address may be being denied connection because ipfw is set to a specific address different from the Systems preference Firewall. How do we check its configuration? do the following: in Terminal type: sudo ipfw list _then enter
in one of the lines it shows what ip addresses are being allowed, like this:"allow any from 192.168.0.0 to 24" if this is different from your router then flush the rules with the following command: sudo ipfw flush _then enter
it should configure an address closer to your router's. check to see if the connection behaves as it should. All this time it could of been lurking there unannounced! please try and post any results, thanks

 

[SilentPanda]

I've been having wireless issues ever since 10.5.1 myself. I have both a Mac Pro and Powerbook. I'm using the AEBS with hidden network, mac filtering, and WPA2. I haven't touched the config in ages... but once I went to 10.5.1 I get random drop outs. I ended up going to my box of cables and pulling ethernet to the Mac Pro as it's getting annoying. Hopefully it's a 10.5.1 issue and 10.5.2 will fix it. I might reinstall 10.5 on my powerbook (I rarely use it) to see if 10.5.1 is the culprit.

Oddly enough both computers seem to disconnect at the same time which to me implies it's an issue with the router but I haven't touched or moved the thing in ages... I'm wondering if the OS is sending some weird information to the base station which borks it.

 

[kaiwai]

I've been having wireless issues ever since 10.5.1 myself. I have both a Mac Pro and Powerbook. I'm using the AEBS with hidden network, mac filtering, and WPA2. I haven't touched the config in ages... but once I went to 10.5.1 I get random drop outs. I ended up going to my box of cables and pulling ethernet to the Mac Pro as it's getting annoying. Hopefully it's a 10.5.1 issue and 10.5.2 will fix it. I might reinstall 10.5 on my powerbook (I rarely use it) to see if 10.5.1 is the culprit.

Oddly enough both computers seem to disconnect at the same time which to me implies it's an issue with the router but I haven't touched or moved the thing in ages... I'm wondering if the OS is sending some weird information to the base station which borks it.

Firstly, why have you got it hidden - have you even read the number of posts who have problems, then find its resolved after they make their router visible?

 

[SilentPanda]

Firstly, why have you got it hidden - have you even read the number of posts who have problems, then find its resolved after they make their router visible?

Because I've had it hidden for........ ever? It's been set up this way since I got the base station which was at least 2 years if not 3.

My iPhone is connected to the base station just fine. It's just 10.5.1 that can't connect to it consistently.

 

[kaiwai]

Because I've had it hidden for........ ever? It's been set up this way since I got the base station which was at least 2 years if not 3.

My iPhone is connected to the base station just fine. It's just 10.5.1 that can't connect to it consistently.

For what reason?

Make it visible and see if it makes a difference.

Don't ask questions, just do it.

 

[SilentPanda]

For what reason?

Make it visible and see if it makes a difference.

Don't ask questions, just do it.

Sir yes sir!

/salute

Edit: Shucks... still broken...

 

[QuarterSwede]

The interesting thing is that in my house, my PB has no problems what so ever but my wife's MB loses the connection a lot or shows that it's connected fine but the browser gives her random 404 errors. We're both running Leopard 10.5.1

 

[Neutral Gamer]

Sir yes sir!

/salute

Haha, kaiwai's tone may be a little harsh but he does have a point about making your wireless network visible.

I'd also recommend changing the WPA2 option to something else or even unnecrypted to see if that makes any difference (although don't keep it like that for long!). I found that using an unencrypted network solved my problems. But I only do so in the middle of the night and when I need to download large files.

It's all worth trying to see if it makes any difference. Also, when does your connection drop out - is it when you're downloading a large amount of data, e.g. Software Update, or is it just completely random when just surfing the web for example?

When I first installed Leopard my connection would go all the time and I couldn't even open a webpage like Yahoo! without it dropping out. Then after changing the connection to WEP and messing around with some of the network settings I managed to make things a lot better. But I still get random problems when downloading large files.

Anyway, here's the settings I changed (this is copied from a post on a separate thread I made nearly a month ago):

1. In Network Preferences click on the Airport section on the left.
2. Make sure Location is Automatic and "Ask to join new networks" is unselected.
3. Click the Advanced button.
4. Make sure your network is in the Preferred Networks table. And make sure when you created your network before that you selected "Remember this network".
5. Tick "Remember any network this computer has joined"
6. Untick the other two options.
7. In the TCP/IP section set "Configure IPv4" to "Manually".
8. Put in your local IP address for "IPv4 Address".
9. Put in the Subnet Mask from your Router's configuration web page. (Mine was 255.255.252.0).
10. Put in the IP address of your Router - again you can find this from your Router's configuration web page.
11. Set "Configure IPv6" to "Off".
12. In the DNS section remove all the DNS Servers and add the ones that again should be found in your Router's configuration web page. (For me it was 194.168.4.100 and 194.168.8.100).
13. Press OK and then press Apply.

Hope it helps, and if not Leopard 10.5.2 is getting closer and closer ...

 

[Neutral Gamer]

The interesting thing is that in my house, my PB has no problems what so ever but my wife's MB loses the connection a lot or shows that it's connected fine but the browser gives her random 404 errors. We're both running Leopard 10.5.1

It just goes to show how RANDOM this problem is!

If everyone keeps submitting these problems along with their hardware (computer and router) and software specs to Apple then hopefully they'll be better able to get to the bottom of it.

But at least it shows why some people say that Leopard has no wireless problems or that it's even BETTER than Tiger while some of us are experiencing the exact opposite.

 

[SilentPanda]

Also, when does your connection drop out - is it when you're downloading a large amount of data, e.g. Software Update, or is it just completely random when just surfing the web for example?

It only goes out when I'm sitting at the computer using it... and it's random... normally I'm just browsing the internet.

(actually it probably goes out when I'm not using the computer too but... I'm not here to notice of course!)

While disabling some options may or may not fix the issue, disabling WPA2, hidden network, and mac filtering to get it to work still leaves it broken. It doesn't fix it. It's just a work around. These options *have* been working for 2+ years. I'm pretty sure 10.5.2 will fix it... I hope...

 

[Mlobo01]

issues...and testing...

So far so good, I have not lost connectivity since last I posted, I am testing a new account and its also running well, I believe that migrated accounts transfer poorly under this iteration of Leopard, mainly because of the transferred prefs, unresolved permissions and caches. Once you get over these small hurdles it seems to open the time to keep on testing other performance related matters, I think we must abandon the notion of carrying over our prefs to a system that likes to write files under it's own environment.
My compilation of fixes include the following if not already listed by others: Turn off ipv6, in SysPrefs>energy saver: turn off "put disc to sleep", flush the ipfw, under the Firewall app. (under essential or specific items)include to allow widgets the need the internet, browsers, messengers, mail clients,quicktime or any video players. under the network pane input the dns numbers, also I found this old hint from macosxhints to make system prefs remember:
"Mac OS X Networking Problems? Try deleting these preference files
We previously noted this procedure as part of a workaround for users who were unable to use AirPort functionality after applying one of Apple's firmware updates.
MacFixIt reader Colin writes "I had a bizarre problem where my network settings were screwy. Although I don't use it PPPoE was checked and every time I unchecked it, it would re-enable itself."
If you are experiencing a problem similar to this, or an issue where Network Preferences cannot remember other settings, delete the following files using the Terminal's "sudo rm" command:
/var/db/NetworkInterfaces.xml
/var/db/SystemConfiguration/*.xml
(jan 2003, issue with panther)

 

[d wade]

i have never once had a wireless problem with leopard. linksys router here. sounds like your router is the problem, not leopard.

 

[theBB]

i have never once had a wireless problem with leopard. linksys router here. sounds like your router is the problem, not leopard.

A piece of software that prevents robust communication with a lot of routers should not be absolved of fault so easily.

There is a chance at around the time you installed Leopard, you also got a neighbor who setup a new network or something like that that started causing a lot of interference problems. If that is the case, a new router may not help.

 

[Mlobo01]

i have never once had a wireless problem with leopard. linksys router here. sounds like your router is the problem, not leopard.

Actually it is the slight configurations in Leopard, the router is fine, Im running Leopard on an external drive via USB to test it, my internal meanwhile has Tiger, my laptop is running Leopard and it has never had an issue, while I could not connect my mac mini to the internet my laptop ran flawlessly, when I would reboot in Tiger it connected with no issues. I have posted possible configurations from all over the place and so have others, from the Apple support forums and from past hints as well, so if you have not had any issues with Leopard then you have managed well, in the mean time others have had issues with it and the router will prove the innocent bystander in Leopard's connectivity issue. For now I have implemented the fixes and I think I understand what I did, it has leveled off nicely but Im still testing. I really do not know if you have been following the thread but if you like just read a couple of prior posts to orientate yourself to the issues that are affecting users, Thanks for the input.

 

[Mlobo01]

my laptop...

is running Leopard with no network issues since the day I installed it, I have rebooted, left it alone to go to sleep on it's own and have put it to sleep manually as well and upon wake it finds the network, but my mac mini has been a different case, I m running Leopard from an external drive to fully tested, I have Tiger on the internal HD justin case, Im posting on another thread here in macrumors about it, and the key is minor configurations mar its robustness in certain configurations and through reading the support post in both macrumors and the Apple forums I can deduct that migrated accounts seem to experience more issues, the ghost of copying over files still haunts this Cat, I've also experienced minor glitches when I have copied files from another drive to the desktop and it asks me for a password, but a minor permission adjustment fixes that. The combination of the inconsistent Firewall, the ipfw itself, the System prefs app that some people have reported that it could not retain settings and could not be locked or was found to get unlocked after reboots? Disc Utility has been dumbed down and we do not know if it does anything worth while anymore, easy Keychain corruption also permeates some users, plugin issues etc.
some have done a clean-install and have done away with the issues, I have stayed the course and have managed to fix 99% of the bugs with the help of fellow members and apple forum folks, but once its stable then all goes well, but Leopard has been glitchy as any other OS X iteration in their initial inceptions. hopefully 10.5.2 will address all or most of them

 

[BryanP]

No problem with WPA or WEP either on Leopard.

I agree with getting a new router.

 

[sowillo14]

I was using an Action Tech, but had the exact same problems. I went to Radio Shack, and picked up a Net Gear, and ran it out the back of the Act. Tech. Since then it has been flawless, and no problems downloading huge files.

 

[Neutral Gamer]

No problem with WPA or WEP either on Leopard.

I agree with getting a new router.

I was using an Action Tech, but had the exact same problems. I went to Radio Shack, and picked up a Net Gear, and ran it out the back of the Act. Tech. Since then it has been flawless, and no problems downloading huge files.

It's good to know that you've both got no problems, but for those of us affected, there was no problem in Tiger, Windows or Linux with the same hardware so I find it totally unacceptable to blame everyone BUT Apple for this problem.

I'm not gonna spend money on a new router. IF Apple don't fix this problem with the upcoming 10.5.2 update then I'll be downgrading to Tiger and will, no doubt like many others, be starting a mass online petition which I have a funny feeling quite a few people would want to join ...

Anyway, HAVE A MERRY CHRISTMAS EVERYONE !

 

[poohat1000]

1. In Network Preferences click on the Airport section on the left.
2. Make sure Location is Automatic and "Ask to join new networks" is unselected.
3. Click the Advanced button.
4. Make sure your network is in the Preferred Networks table. And make sure when you created your network before that you selected "Remember this network".
5. Tick "Remember any network this computer has joined"
6. Untick the other two options.
7. In the TCP/IP section set "Configure IPv4" to "Manually".
8. Put in your local IP address for "IPv4 Address".
9. Put in the Subnet Mask from your Router's configuration web page. (Mine was 255.255.252.0).
10. Put in the IP address of your Router - again you can find this from your Router's configuration web page.
11. Set "Configure IPv6" to "Off".
12. In the DNS section remove all the DNS Servers and add the ones that again should be found in your Router's configuration web page. (For me it was 194.168.4.100 and 194.168.8.100).
13. Press OK and then press Apply.

This(combined with sudo ipfw flush in terminal) seems to have done the trick! Thanks