Hi,
my problem is that a while after I got my MBP (15", 2.53GHz, OS 10.6.2), my old PowerBook G4 (12", 867MHz PPC, OS 10.4.11) lost its ability to see my AirPort Express wireless network.
I've been googling for a while, and I've found lots of people with airport express connection problems, but noone where one computer can connect and another can't.
My MBP had problems reconnecting to the network after sleep mode, but that seems to be fixed now after I reconfigured the airport from scratch (soft reset).
But my powerbook can't see my wireless network at all. It used to: I've copied a lot of the files from my old powerbook to my new MBP over the wireless network, where both computers showed up in each other's Finders so that I could connect to the old one from the new one. One problem I had copying files this way that may be relevant here is that when I tried to copy very large folders (i.e. iTunes music library), the connection would usually fail in the middle of the file transfer.
Anyway, as I say, now I can't even get my powerbook to see the network - it doesn't show up in the airport menu in the status bar, and it doesn't show up in airport admin utility.
I've tried a couple of the remedies suggested in CNET's article "Tutorial: Fixing Wireless connectivity (including AirPort) problems: Dropouts, slow speed, more" (http://reviews.cnet.com/8301-13727_7-10331876-263.html):
- Turn "Distribute IP Addresses" off (not relevant, since the AE is set to share one IP Address)
- Delete all "Preferred Network" listings then re-establish (tried that, didn't help)
I haven't tried "Reverting to older AirPort kernel extensions" because I'm nervous about the warning they give: [WARNING: This workaround is risky because you should not generally mix and match kernel extensions after updates. You will also lose any AirPort-related refinements brought about by the most recent update and new conflicts can ensue. Still, in a bind, it can restore wireless connectivity where other workarounds fail.] - and I haven't tried any of the other remedies suggested on that page, since they don't apply to my problem.
Any advice?
Thanks.
my problem is that a while after I got my MBP (15", 2.53GHz, OS 10.6.2), my old PowerBook G4 (12", 867MHz PPC, OS 10.4.11) lost its ability to see my AirPort Express wireless network.
I've been googling for a while, and I've found lots of people with airport express connection problems, but noone where one computer can connect and another can't.
My MBP had problems reconnecting to the network after sleep mode, but that seems to be fixed now after I reconfigured the airport from scratch (soft reset).
But my powerbook can't see my wireless network at all. It used to: I've copied a lot of the files from my old powerbook to my new MBP over the wireless network, where both computers showed up in each other's Finders so that I could connect to the old one from the new one. One problem I had copying files this way that may be relevant here is that when I tried to copy very large folders (i.e. iTunes music library), the connection would usually fail in the middle of the file transfer.
Anyway, as I say, now I can't even get my powerbook to see the network - it doesn't show up in the airport menu in the status bar, and it doesn't show up in airport admin utility.
I've tried a couple of the remedies suggested in CNET's article "Tutorial: Fixing Wireless connectivity (including AirPort) problems: Dropouts, slow speed, more" (http://reviews.cnet.com/8301-13727_7-10331876-263.html):
- Turn "Distribute IP Addresses" off (not relevant, since the AE is set to share one IP Address)
- Delete all "Preferred Network" listings then re-establish (tried that, didn't help)
I haven't tried "Reverting to older AirPort kernel extensions" because I'm nervous about the warning they give: [WARNING: This workaround is risky because you should not generally mix and match kernel extensions after updates. You will also lose any AirPort-related refinements brought about by the most recent update and new conflicts can ensue. Still, in a bind, it can restore wireless connectivity where other workarounds fail.] - and I haven't tried any of the other remedies suggested on that page, since they don't apply to my problem.
Any advice?
Thanks.