[kiskynet]

Im now enjoying 56k modem style speeds with Airport courtesy of 10.4.8 update, some other guy also has the exact same issue. Proceed with caution if you don't fancy having to get an Ethernet cable out.

http://discussions.apple.com/thread....39762&#3239762

Any network geniuses make any sense of the ping results between the crippled MBP and a Powerbook G4 both next to each other connected Wirelessly to the same router.

--- MacBook Pro 10.0.1.1 ping statistics ---
116 packets transmitted, 113 packets received, 2% packet loss
round-trip min/avg/max/stddev = 264.554/1620.275/3283.362/1080.869 ms

--- Powerbook 10.0.1.1 ping statistics ---
80 packets transmitted, 80 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.919/1.118/3.202/0.362 ms

-- Sample of the Results from the MacBook Pro --
64 bytes from 10.0.1.1: icmp_seq=101 ttl=64 time=3265.906 ms
64 bytes from 10.0.1.1: icmp_seq=102 ttl=64 time=2265.797 ms
64 bytes from 10.0.1.1: icmp_seq=103 ttl=64 time=1266.032 ms
64 bytes from 10.0.1.1: icmp_seq=104 ttl=64 time=265.984 ms
64 bytes from 10.0.1.1: icmp_seq=105 ttl=64 time=3267.308 ms
64 bytes from 10.0.1.1: icmp_seq=106 ttl=64 time=2267.246 ms
64 bytes from 10.0.1.1: icmp_seq=107 ttl=64 time=1267.472 ms
64 bytes from 10.0.1.1: icmp_seq=108 ttl=64 time=267.364 ms
64 bytes from 10.0.1.1: icmp_seq=109 ttl=64 time=3266.137 ms
64 bytes from 10.0.1.1: icmp_seq=110 ttl=64 time=2266.060 ms
64 bytes from 10.0.1.1: icmp_seq=111 ttl=64 time=1266.267 ms
64 bytes from 10.0.1.1: icmp_seq=112 ttl=64 time=266.264 ms

it goes on like this consistently cycling through the 3000's down to 200 something then back to the 3000's

[sknapp351]

Odd. I actually think my connection to my Linksys network has become faster with 10.4.8. I am on a MBP. I will try with the school's wireless later to see if there is any change.
SAm

[JKT]

For Airport issues, read this report at MacFixIt

[ghporter]

...and network related issues go in the Networking forum. Moving...

[kiskynet]

Originally Posted by JKT

For Airport issues, read this report at MacFixIt

No fixes for this particular issue yet, beware, it's amazing how suddenly downgrading to incredibly slow connections ruins a lot of things you take for granted, basically I'm f***Ckd till I get a fix from Apple. It may just be me but I'd wait a little longer to update if you've got a MBP

(Thanks for moving to correct forum btw...)

[kiskynet]

AAAHHH feel my pain ; )

[kiskynet]

Oops sorry Apple, the culprit was Coconut Wifi, turned it off and everthings back to normal again, now I can put the ugly greeen ethernet cable back in the cupboard.

[Eriamjh]

I wonder if it is related to this issue?

Mac OS X 10.4.8: AirPort does not auto-connect to existing networks after restart or wake from sleep

[zerroeffect]

The coconut wifi program was my problem, too. Thanks for sharing.

[Matthew Attoe]

And mine too!!!

Thank very much!

Matthew

[n8236]

Yes, had the same issue w/ at two different locations. The airport speed is VERY slow but perfectly fine on ethernet. But once I got rid of Coconut Wifi, speed ran back up to normal speeds. I like Coconut Wifi, i hope this problem gets fixed.

[ghporter]

The "problem" is that surfing at "normal speed" takes ALL the wireless network card's capacity. Coconut WiFi soaks up about half of that capacity (the card basically switches between surfing and Coconut constantly) and you wind up with much slower everything. Once Coconut has told you what you need to know, just stop it; after all, if you're USING a wireless network, what more do you need to know? It's obviously there.

[n8236]

Well, some of my problems have resurfaced. Connection is noticeably slower and whenever I restart, Airport does not remember my network, ugh, so frustrating. This is happening only on my mbp. I tried Apple's resolution, but no go since i dun have a wpa2 connection