super slow (wifi) networking

arri

arri

Registered
hi

i have a mac mini (intel) on which wifi-networking is really flaky when booted into osx.

- it's not so much the actual transfer speed, but rather the "connection responsiveness". by this i mean that sometimes connections time-out, while a next attempt to connect succeeds in a few milliseconds.
- the issue doesn't appear to be DNS-related, because it's not there when i use a cable to connect to the same router.
- for clarity i made sure there's only 1 nic active when connecting to the router.
- the issue is not there when i boot the mini into linux.
- in all cases the network uses DHCP
- all other machines (mac/win/linux/ppc/x86/802.11b/g/n) don't appear to suffer from this. it seems specific to the combi mini+osx.

any ideas?

arri
 
First of all what wireless security and on what wireless frequency on what router?

Well try some of these steps:

1. Open System Preferences->Network and at the top of the pane select a New "Location" and connect to the wireless.
2. In System Preferences->Network hit the "Advanced" button and in the TCP/IP tab turn off IPv6.


Super Geek Airport card reset:
1. Navigate to /System/Library/Extensions and move the files (you will need an Admin password to move) AppleAirPort.kext to the desktop and then immediately restart. It will take a while to startup because it is re-writing the driver again.
2. Startup airport to see if this fix works. If it doesn't rebuild the AppleAirPort.kext file then you can move it back and then restart again.


Hopefully one of these tricks might help. Good Luck
 
thanks for your responses,

i think i tracked down the cause.
it seems the mini just doesn't like it when there's a 802.11b client on the network.
theoretically this would only bring down the entire network to a max of 11Mbit/s,
but somehow the mini has a hard time understanding what's going on...
as long as the (only) b-client is offline, everything works like a charm.

interesting suggestion thought, removing the .kext.
does osx actually re-create the kext on the next boot from firmware or something?


gr
arri
 
arri said:
interesting suggestion thought, removing the .kext.
does osx actually re-create the kext on the next boot from firmware or something?
Click to expand...

Nope I screwed up! I will post the actual article.

1. Download the Mac OS X combo updater directly precedent to your current system version if you applied an incremental Mac OS X update (e.g. Mac OS X 10.4.9), or your current system version if you applied a security update from Apple's download page.

2. Download and install the shareware application Pacifist.

3. Drag the Mac OS X combo installer package (e.g. MacOSXUpd10.4.9Intel.pkg) onto the Pacifist application icon.

4. Click the triangle next to System to expand it

5. Click the triangle next to Library to expand it

6. Click the triangle next to Extensions to expand it

7. Scroll down and find the file AppleAirPort.kext. Drag it to your Desktop or another location (you will have to enter your administrator password)

8. On your Mac OS X startup drive, navigate to /System/Library/Extensions and locate a similarly named file (AppleAirPort.kext). Move it to another location for safe keeping.

9. Now drag the file from step 7 (the one that you retrieved from the Mac OS X combo install package) into the /System/Library/Extensions directory on your startup, in effect replacing the newer file (installed by the AirPort updater) with and older copy -- you will have to enter an administrator password.

10 .Restart your Mac
Click to expand...
 
ok…well,

i didn't try removing the .kext anyways.
in my case it's really something between the wifi-router and different connected clients. i'm not so what exactly, but i just setteled with a cat-6 cable. i'm not so fond of wifi anyways. a cable just works.


as a side note, to test something (embedding font in an .app package) i deleted HelveticaNeue.dfont from /System/Library/Fonts and discovered that osx will actually re-create it.
 
You must log in or register to reply here.
Back
Top