Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Mac OS X 10.5.2 AirPort/D-Link DIR-625 802.11n workaround: drop to b/g

A number of posters have reported difficulties connecting to their D-Link DIR-625 wireless routers after updating to Mac OS X 10.5.2.

Most of these same posters have reported that disabling 802.11n mode and using the router in 802.11b/g only mode restores connectivity.

This may be an incompatibility between D-Link's implementation of the 802.11n draft standard and Apple's implementation of a later version of the draft standard.

This post exists to document the workaround and as a suggestion to others having difficulties with other vendors' 802.11n routers to try the same workaround.

If you have success doing the same with another vendor's router, please reply below.

In the mean time, if you are an affected D-Link customer, you may want to contact D-Link customer service to inquire about the issue while Apple engineers investigate.

Quad 2.5 GHz G5, 5 GB | 2.33 GHz MBP C2D 2 GB, Mac OS X (10.5.2)

Posted on Feb 13, 2008 7:43 PM

Reply
29 replies

Jun 14, 2008 3:02 PM in response to Sermonator

I am in love with my Macbook but when it comes to Wifi, I embarassingly enough have to work on XP via Boot Camp.

I bought the D-Link DIR-300 wireless router only cause it had the capacity to manipulate thresholds like you said but it didn't work. I have done everything on these forums. Logged into safe mode and this and that, but no result.

Any idea what else I could change in the router to get wifi going? At least in my own office. Thank you.

Jul 20, 2008 3:30 AM in response to Dogcow-Moof

I can confirm this for the router AVM FRITZ!Box Wlan 3170: Disabling their proprietary 802.11g++ option forcing the router back to standard b/g solved my wireless dropouts on my imac entirely.
Ironically this option is "hidden" in the expert view of the router's interface that needs to be activated first.

Though I'm glad to have solved this problem I hope that Apple adresses this in future releases on the client-side. It would help a lot to provide an option to disable Draft n mode especially when using public hotspots.

Jul 24, 2008 2:12 PM in response to tomi0001

Cannot confirm workaround for AVM FRITZ!Box Wlan 3170. It seemed to be okay for a day but for several days the "old" problems are there again (connection gets lost every 10-20 seconds, only "rescanning" helps). The same imac works fine on Bootcamp XP SP2 so I think it's a software problem in OS X rather than a imac-hardware or router bug.

Aug 17, 2008 1:39 PM in response to tomi0001

so im trawling through this info but embarrassingly i don't understand a lot of what's being advised...

i have my new mac book and have been online on and off all day, on and off because i keep losing connection. i updated to OS 10.5.4 as advised, however i suspect the problem is my router, d-link rangebooster n650.

can someone detail what i need to do? do i connect the router to the macbook to updates its software? do i toggle with connection settings on the macbook?

many thanks in advance,

Stephen, a virgin mac user who is still getting to grips with the change over from pc and windows

Sep 19, 2008 10:59 AM in response to Dogcow-Moof

my opinion:

This is bad advice, a person with a laptop and WIFI should be able to travel with their laptop to any public location and be able to maintain a reliable WIFI connection. They CANNOT upgrade every router they encounter during their travels to make it work with their macbook laptop. The macbook should WORK with any 3rd party router with a Certified protocol. If it cannot connect with the fastest it should connect with the next lowest "Certified" protocol such as G/B/A.

This is clearly a software problem, I discovered things broken with the 10.5.3 update. I have performed 3 Archives and Installs and every time when I roll back to 10.5.2 the Airport range is restored to normal. This is all verified in the logs.

Granted 802.11"N" is "draft" protocol, but the fact remains if "N" protocol is not able to maintain a reliable connection with "N" then it SHOULD drop down to CERTIFIED "G" or even "B". +But the connection even at the lower spec should be reliable and consistent.+

Why does this problem seem to go away with a Airport Extreme?
and only fails with 3rd party routers?

Well that is obvious but it doesn't resolve the problem for the person who travels with their laptop with decreased Airport performance. Now you might say this a marketing ploy to encourage sales of proprietary equipment, but that will only come back to bite them when people go to public WIFI locations and find they cannot connect at Starbucks or elsewhere. So it is foolish to mess with your router settings when it worked prior to the latest upgrade installed.

Sure you might try to tweak a few things and change packet size (going from 2346 to 2306 as mentioned in other threads) but that does nothing to address the root of the problem, like I said you cannot run around and tweak someone else's router. All my tests confirm the performance of the Airport (quality of the signal, range etc.) all dropped on my Broadcom 4311 Airport card after I applied 10.5.3.

And you are RIGHT Apple should NOT be addressing 3rd party router issues, but they should be COMPLYING with the standard for "Certified" standards especially when people buy their products to Roam and use 3rd party equipment.

IF this truly was a "Draft N" or a router problem there would be a similar amount of complaints from the PC world.

For me,

It worked fine in 10.5.2
Was broken in 10.5.3
Remained broken in 10.5.4 a week later
Remained broken in 10.5.5 the other day

Each of the times above I have performed an Archive and Install back to 10.5.2 and the problem resolved itself, Airport card connectivity and performance were restored.

Only problem NOW is when you roll back to 10.5.2 you are vulnerable by NOT having all the Security patches applied that have been released since then such as the DNS vulnerability which allows someone to hack your macbook in 60 seconds or less.

Sep 19, 2008 7:59 PM in response to go.dizzy

go.dizzy wrote:
This is bad advice, a person with a laptop and WIFI should be able to travel with their laptop to any public location and be able to maintain a reliable WIFI connection. They CANNOT upgrade every router they encounter during their travels to make it work with their macbook laptop. The macbook should WORK with any 3rd party router with a Certified protocol. If it cannot connect with the fastest it should connect with the next lowest "Certified" protocol such as G/B/A.


To a certain degree I agree with you here.

IMHO, Mac OS X should have a way to disable use of 802.11n if it proves to be problematic, forcing it to drop back to 802.11b/g.

I can't disagree with the rest of your statements.

It's not Apple's responsibility to have to work around broken third party products.

Note that Macs do successfully connect to a variety of "N draft" routers from other manufacturers that don't suffer from the same firmware bugs and/or broken implementation of the 802.11n draft spec used on the D-Link DIR-625, and even then I'm not sure if D-Link has addressed this themselves with a firmware patch by now.

I've gone into why Windows/PCs/other versions of Mac OS X can't be used to exonerate routers as the cause of problems in multiple other threads.

Only problem NOW is when you roll back to 10.5.2 you are vulnerable by NOT having all the Security patches applied that have been released since then such as the DNS vulnerability which allows someone to hack your macbook in 60 seconds or less.


The DNS vulnerability has absolutely zero to do with "hacking your macbook."

The DNS vulnerability had to do with being redirected to spoofed web sites and in no way allows access to your personal machine.

Sep 27, 2008 1:03 AM in response to wallmac

wallmac wrote:
Does anyone know how to connect Mac OS x 10.5.2 Airport/D-Link DIR-615 instead of Dir-625?


If you're having difficulties connecting, you should first make sure your D-Link has the most up-to-date firmware available from the D-Link website installed on it.

If you're still having issues after that, you can also try disabling "N" mode to see if it solves your problem.

Oct 14, 2008 10:03 PM in response to Dogcow-Moof

This problem oddly enough remains a pain in the neck.

Although the advice given here solves the problem for some, I still encounter it.

So what I did:

My router DIR-635 does have the latest formware update.
I disabled 802.11n
I deleted the airport preference file located in \Library\Preferences\SystemConfiguration\ and called com.apple.airport.preferences.plist
I deleted any password in my Keychain that is related to my wireless network

Sometimes this would be enough for a few weeks or days. But "the problem" came back. Randomly. From 10.5.2. until 10.5.5.

Now I tried all the steps mentioned above to no avail. After those steps I rebooted the DIR-635 which seemed to help.

Another strange fact is that I could while NOT being able to connect wirelessly to the internet control another machine on my network with a remote control client.

I guess there won't be anyone from Cupertino reading this....still the problem as such is still unresolved to me.

Greets everyone.

Mac OS X 10.5.2 AirPort/D-Link DIR-625 802.11n workaround: drop to b/g

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.