Hi guys,
I have asked this already, over a year ago, from my old accound, but no one ever replied.

This is NOT a problem with any particular machine, or OS X version. This "problem" is generic.
I work in an Apple Service Provider, so i have tried it out with the whole Mac lineup, with both Windows 7 and Windows XP, and with OS X Leopard thru Mountain Lion. It's also not a router related issue, same behaviour on a cheap tplink, an expencive cisco and on airport extreme.
If WiFi reception is bad, Mac OS X does see it, but timeouts when i try to connect to it. Windows connects flawlessly.
If WiFi reception is better, (but still not good), Mac OS X connects, but you can't surf the web almost at all (apple.com loads in about a minute, on a 30MBps connection in this scenario), but on Windows, i can even stream videos or download stuff (not at the max speed ofc, but at least 3-4mpbs).
I noticed that Terminal ping timeouts 80 out of 100 times, and dos 10 out of 100.
And in the first scenario, here is my Console output:
MacAuthEvent en1 --- Auth request tx failed
directed SSID scan fail
Now, i am aware that this is solvable - buy an AirPort Express as an extension.
I'm not asking because of that, i have bought a bridged express...
I'm asking because i would really like to know what makes it tick the way it does?
Is there a way to "fix" this?
And if someone has any ideas on why would Apple "underclock" our wifis on osx?
The only answer to this third question that i have found, would be "battery conservation" - i have noticed a huge battery drain when on weak wifi signal.
But what if i don't care about the battery consumption, if im on an iMac, or if i REALLY don't care about the battery....
It would be cool if someone wants to discuss this with me
I have asked this already, over a year ago, from my old accound, but no one ever replied.
This is NOT a problem with any particular machine, or OS X version. This "problem" is generic.
I work in an Apple Service Provider, so i have tried it out with the whole Mac lineup, with both Windows 7 and Windows XP, and with OS X Leopard thru Mountain Lion. It's also not a router related issue, same behaviour on a cheap tplink, an expencive cisco and on airport extreme.
If WiFi reception is bad, Mac OS X does see it, but timeouts when i try to connect to it. Windows connects flawlessly.
If WiFi reception is better, (but still not good), Mac OS X connects, but you can't surf the web almost at all (apple.com loads in about a minute, on a 30MBps connection in this scenario), but on Windows, i can even stream videos or download stuff (not at the max speed ofc, but at least 3-4mpbs).
I noticed that Terminal ping timeouts 80 out of 100 times, and dos 10 out of 100.
And in the first scenario, here is my Console output:
MacAuthEvent en1 --- Auth request tx failed
directed SSID scan fail
Now, i am aware that this is solvable - buy an AirPort Express as an extension.
I'm not asking because of that, i have bought a bridged express...
I'm asking because i would really like to know what makes it tick the way it does?
Is there a way to "fix" this?
And if someone has any ideas on why would Apple "underclock" our wifis on osx?
The only answer to this third question that i have found, would be "battery conservation" - i have noticed a huge battery drain when on weak wifi signal.
But what if i don't care about the battery consumption, if im on an iMac, or if i REALLY don't care about the battery....
It would be cool if someone wants to discuss this with me