Airport Express network suddenly no longer visible -for one Mac..but wait

Hi everyone
Setup isDSL modem>ethernet>"downstairs" AX...."upstairs" AX connects fine to it as a WDS remote station with 128-bit hex password....
The two ibooks, one G3 one G4 connect fine, and so did the PowerMac g4 desktop that was formerly the software base station (range was too short, so got the AX's). The desktop suddenly stopped seeing the network. Then, it came back on, for about an hour and the internet connect infor showed it being connected for the 60 hours elapsed since that seeming disappearance. Then it went away... 60 hours later, up it popped again, again for an hour, and I downloaded pics from AOL, browsed etc. Come back to find it gone again and has not returned.
Problem is either software/configuration based or intermittent hardware -- how can I find out without replacing the part? (The solution to the very similar problem posted a few days ago had to do with a channel switch... my WDS system base stations are on channel 6 (their choice, I guess).. does not seem to apply.
Does anyone think the Security Update 2006-005 would help, and how would I get it to my non networked desktop?
Thanks for help!

Well, from reading some other posts, and trying my own experimenting, I have gotten it to work.
Deleting the keychain did nothing, manually connecting to the network by typing the name in etc.. nothing.
What DID work was using my G3 iBook (which could see the network) to use the Airport Administrator to change the channel from Automatic to manual - in this case channel 7 (a completely arbitrary choice).
The thing I cannot work out is why it had this issue in the first place. It worked fine for months then one day decided that it apparently didn't like automatic channel selection.
The problem is solved but the cause is still a mystery.
Hopefully though, this might help others with the same problem.
20" iMac Core Duo 2.0GHZ Mac OS X (10.4.7) 2GB RAM, 500GB HDD, 256MB Graphics

Similar Messages

Airport Express network suddenly no longer visible - but only for one Mac..

What the..?
My 20" iMac Core Duo can no longer see my Airport Express network. It happened yesterday after restarting the AE a few times.. (I do this and also restart the modem from time to time if the net connection stalls - or I want to boot of my housemate's PC from the network cause she's hogging bandwidth)..
Anyway.. The first restart caused it to not re-appear on the list of available networks, so I restarted again.. then it was fine - it came back. All good.
I reset it again this morning because the net connection was not meeting my expectation and now the iMac no longer sees the AE network.
I can connect to other Wi-Fi networks around me (there is a neighbour with no WEP) but cant see hide nor hair of my own network.
The puzzling thing is that my girlfriend's Mac Book, my other iBook G3 and my housemate's PC can all see it and use the network fine - as normal..
So what has happenned? And what do I need to do?
Between you and me ..This intel iMac has been a bit tempramental ever since I got it.. weird things like this happen to it from time to time.. never one thing that you can point at and say AHA! Faulty [something] but just weird stuff like this... Hmmmm..
Some help would be much appreciated.. Thanks!
20" iMac Core Duo 2.0GHZ Mac OS X (10.4.7) 2GB RAM, 500GB HDD, 256MB Graphics

Well, from reading some other posts, and trying my own experimenting, I have gotten it to work.
Deleting the keychain did nothing, manually connecting to the network by typing the name in etc.. nothing.
What DID work was using my G3 iBook (which could see the network) to use the Airport Administrator to change the channel from Automatic to manual - in this case channel 7 (a completely arbitrary choice).
The thing I cannot work out is why it had this issue in the first place. It worked fine for months then one day decided that it apparently didn't like automatic channel selection.
The problem is solved but the cause is still a mystery.
Hopefully though, this might help others with the same problem.
20" iMac Core Duo 2.0GHZ Mac OS X (10.4.7) 2GB RAM, 500GB HDD, 256MB Graphics

Report visible for one user but not for other user

Hi all,
We have a situation where a report is visible to one user but not to some other user. What could be the possible explanation for this? Please let me know.
I need quick responses.
Thanks in advance,
Sananda

Hi Sananda,
Just assign the saem roles as the other user who can view ..
You can inform the Auth/basis team and they shud be able to do this..
The T Code is RSECADMIN>user Tab>Assignment>user.Display and BView the roles here..
or goto SU01 and check for the Roles Tab.....
The New user must have the same roles as that of the other..
Rgds
SVU123
Edited by: svu123 on Sep 22, 2010 7:14 AM

Airport express bases station no longer visible after W7 upgrade

Hi - I just upgraded my Dell Inspirion 530 to Windows 7 Ultimate. Since doing so, I can no longer "see" my Airport Express Base Station (1st generation). It is not visible via Airport Express Utility (5.5.3), nor as a connected device through Devices and Printers. I believe there may be a firewall or network security (Symantec anti virus) setting that I need to configure, but do not know where to start. The device worked fine in my Windows Vista configuration prior to upgrading, so I am confident that it is not a Express device issue. The device shows Green, indicating that it is working properly. Help appreciated!!!

do you still ahve signal!! i mean are you able to find the signal when you try to connect to it and use the internet?
if you are able to connect to the intenet on the same machine, did you try updating the untility software?

Time Capsule and Airport Express network extension

Hello,
I have a time capsule using 5GZ network. However i have an issue, as in my bed room the signal is too weak.
I also get an airport express and would like to use it in order to make the signal reach my bed room.
Would you please tell me how i could do so ?
I checked WDS but this option is not available for my time capsule.
Thanks for your reply.

Hello both,
thanks for you reply.
Actually Tesserax, it's what i did from my Time Capsule + Airport Express.
However in my room i cannot get enought signal and only see the Time Capsule wifi network.
Is this normal or shall the airport express network appears differently ?
Thanks for your reply,
Pierre

Macbook no longer detects Airport Express Network

I've been using my macbook to connect to my Airport express base station for my home wireless daily for like a year now. Today however, my macbook refuses to connect to the network. After a few scans it detects the network, then when I try to connect it brings up the "this network requires a WEP password" which I put in, and then the connection times out on every attempt.
I tried using the Airport Utility which fails to even detect the base station.
Yes I've restarted my MB, yes I've restarted the express/modem. Thing is, I'm connected to the same network right now on my iPhone which doesn't seem to have any problem.

Update: my macbook can connect to the wireless network at my university, but still not the airport express network.

Airport Card for G3 to use on current Airport Express Network

I have a G4 PowerBook, a gray G4, and most recently a hand-me-down blue (green?) G3. I have an Airport Express that the two G4s use for wireless internet. I'd like to add an airport extreme OR old airport card to the G3 to include it in our home network wirelessly as well. Can this be done? What, exactly, do I need?

Hello Owen,
Yes, but the Antenna is built-in. Alternative if it doesn't have an Airport card right now...
http://eshop.macsales.com/item/Newer%20Technology/MXP2802GU2/
It's possible to run as high as 10.5.8 on it.
Leopard requirements/10.5.x...
    * Mac computer with an Intel, PowerPC G5, or PowerPC G4 (867MHz or faster) processor
minimum system requirements
    * 512MB of memory (I say 1.5GB for PPC at least, 2-3GB minimum for IntelMacs)
    * DVD drive for installation
    * 9GB of available disk space (I say 30GB at least)

WRT54G as client for Airport Express Network?

I know this can be done in reverse, with the airport express becoming a client for the WRT54G, but I want the 54G to connect to the airport express network I've already set up. Is there a way, and how?
Thanks!

It is not possible to set up a Linksys WRT54G as a client on a wireless network created by an Airport Express.
Others have noted here (in past discussions) that they have also been unsuccessful at configuring the WRT54G as a remote base station in a wireless distribution system (WDS) where the Airport Express is the main base station.

Solution to Airport Extreme Base Station + Airport Express networking probs

I've been investigating this for 3 straight days after inadvertently destabilizing my network. There are tons of posts discussing a variety of issues, all of which seem related. My goal here is to provide links to other relevant posts and explain what I ended up doing to get things to work.
First, the background. You can skip below to SOLUTION if you don't really care... However, I highly recommend you take the time to read everything, as you'll get other useful information in the BACKGROUND section. I'm guessing many of you have similar, related problems so BACKGROUND might help provide context (and solutions) to some things you are seeing...
MY SETUP:
AirPort Extreme Base Station (AEBS) of type b/g (round one, not square one), connects to the cable modem, and creates a WDS network that is then shared across two standard AirPort Express (AEX) units (100megabit, not the gigabit ones). One AEX serves as a relay unit that accepts clients, the other serves as a remote unit that also accepts clients. The intent is to show a single network throughout the house and let users log on to one network and move between networking units without having to switch from network to network.
I have a variety of networked devices throughout the house all running on the same network (2 Mac Pros, a Powerbook G4, a Mac Mini, an Apple TV, a Windows XP laptop, two iPhones, two wifi printers, and a 5-unit Sonos system, plus the AEBS and two AEXs). Yeah, I'm a geek.
The Mac Pros are both running 10.4.11, and the Powerbook is running 10.5.2.
AEBS is running firmware 5.7
AEXs are running firmware 6.3
All Macs were initially accessing configs via the recently released AirPort Utility 5.3.1. More on that later.
BACKGROUND:
I've had this network setup working for about a year now. Recently, I've been having poor network performance problems and came to the conclusion it was a LAN problem (ie. problem with my home network, as opposed to with my ISP). Upon initial investigation, I began by looking at my networking logs (via AirPort Utility 5.3.1). You get to those by selecting the unit in question, choosing "Manual Configuration", the selecting the "Advanced" tab up top with the "Logging and SNMP" sub-tab. Click the "Logs and Statistics" button therein for log details from that unit.
The first thing I noticed was "Administrative access denied to ff80::xxxxxxxxx" messages - a lot of them. I didn't recognize the ff80:: address in question, and so became concerned it was someone outside the network trying to hack one (or all) of the AEBS/AEX units. You can see threads discussing that investigation here:
"Hack or panic?" - http://discussions.apple.com/thread.jspa?threadID=1438486
"Administrative access denied" - http://discussions.apple.com/thread.jspa?threadID=1438865
Long and short of it is that the recent AirPort Utility 5.3.1 release (current as of March 13) seems to have problems (keychain) when attempting to access the AEBS and AEX units. The "Administrative access denied" logs actually refer to the client machine you are using when you try to read the logs. The ff80::xxxxxx address is simply the IPv6 address for the machine you are using; if you turn off IPv6 on your client machine, that address should switch over to begin showing a regular IP address instead (something like 10.0.1.xxx), which makes it easier to associate the IP to the machine. I explain how to deactivate IPv6 on both Tiger (10.4.x) and Leopard (1.5.x) here:
http://discussions.apple.com/thread.jspa?messageID=6814978#6814978
Anyway, in the process of investigating the "Administrative access denied" problem, I began tinkering with my AEX settings. Specifically, I ended up performing a hard factory reset (unplug unit, plug back in while holding down the little button with paper click/pen for ~10-15 seconds until light flashes green 4x then reverts to amber/yellow/orange). I began reconfiguring my entire WDS network using the newly updated AirPort Utility 5.3.1, and that's when the trouble started.
(If you are having problems seeing either your AirPort Extreme Base Station or AirPort Express, read this:)
In short, each time I thought I had properly configured things and then confirmed settings (kicking off a reboot on the AEX unit) the unit would restart with new settings but not properly join the WDS and not show up in the AirPort Utility list of units. More specifically, I would start with a "wiped" AEX and see both the AEBS and the AEX in my AirPort Utility list, but upon confirm/reboot the AEX would disappear and the AEBS would remain. However, that's not 100% correct. It seems that sometimes I would end up with the AEX and NOT the AEBS. Because both the AEX and AEBS were theoretically "hosting" the same network name (remember, WDS shares the network name across units) my auto-login feature for my client computer's wifi seemed to "jump on" whichever unit it first saw hosting the default network name for my house. In other words, it seems what was really happening was that I was ending up with two separate networks in my house, both with the same name but not talking to each other (as opposed to two units sharing the same network name and internet connection). The AEX would continue to blink orange/amber/yellow (whichever color it is to your eyes ) because it could not grab an internet connection -- and if I was on the network through that AEX unit I would not get internet. But if i was connected through the AEBS I would continue to have internet access. As far as my client computer (my Mac Pro) was concerned, I was on the home wifi network even if I was on the AEX rather than the AEBS -- it would show the home wifi network name as the name of the network it had connected to. But when I opened the AirPort Utility 5.3.1 I would see only the AEX (if I was connected through it) or the AEBS (if connected through it) -- a clear indication that the units were not truly sharing the same network.
I tried rebooting and reconfiguring the AEBS and AEX about 50 times (literally). I even tracked down an older version of the AirPort Utility 5.2.1 via this thread (see Tesserax post):
http://discussions.apple.com/thread.jspa?threadID=1067565
One interesting thing re: 5.2.1 is that the "Administrative access denied" errors summarized above disappeared. As explained in a post reference above, the going theory is that this a permissions/keychain problem new and unique to AirPort Utility 5.3.1. However, even though 5.2.1 does have a slightly different interface with different settings, I still couldn't get the WDS to work.
EVENTUALLY, I came across this post:
http://discussions.apple.com/thread.jspa?threadID=1422527
MuaddibOfArrakis walks through setting up a WDS from scratch, and the workflow is different than what is possible with either AirPort Utility 5.3.1 or 5.2.1. He's doing it with the old version of AirPort Admin Utility, which I fortunately saved a copy of many moons ago when I had somewhat-related problems with my WDS (since forgotten). In fact, it's a lot easier. What's nice about this older app is that it literally does the heavy lifting of "connecting" the AEBS and AEX units during the configuration -- it reboots both at the same time as the config is happening, and lets you choose from a list of available units to "add" to your WDS network. In short, it's a FAR SUPERIOR workflow even though some of the GUI isn't as intuitive as the newer AirPort Utilities that were designed to replace it.
SOLUTION:
If still have a copy of the AirPort Admin Utility follow the instructions from MuaddibOfArrakis here:
http://discussions.apple.com/thread.jspa?threadID=1422527
If not, try setting up your WDS network using AirPort Utility (hereafter AU), with these configs (take from my now-working network), as viewed through AirPort Utility 5.3.1.
I. Configure your AEBS.
Select the AEBS from AU, and choose "Manual Setup"
1. Under the AirPort tab up top:
a. Under "Base Station" sub-tab:
i.) assign a name for that specific unit, so you can later identify the specific unit from the list of units -- this is the name that will show up beside the unit in the AU list of configurable units. You can name it something like "kitchen", or "office". I have mine numbered, so XXXXXv1, XXXXXv2 etc where the XXXXX is the name of the shared network and the numbers help me tell the units apart. Just be sure you name each uniquely, and if you have several you might write the name on the unit itself.
ii.) pick a password for logging into that unit. This is different from the network password, its a security check to get in and change the configs on this unit later. Be sure to remember it in your keychain for the sake of simplicity, and write it down somewhere secure.
iii.) if you choose to set time automatically, pick a location that you will use consistently across all your units. I use time.apple.com.
iv.) uncheck "Allow configuration over Ethernet WAN port" unless you want to be able to remotely mess with settings -- which you almost certainly do not need to do.
v.) I left the "Options" button alone - no settings there.
b. Under the "Wireless" sub-tab:
i.) Wireless Mode: "Participate in a WDS network"
ii.) Network Name: this will be the name of your wifi network shared by all units, so be sure to remember what you pick. If you are already connected to this AEBS via wifi while you are making these changes, then you can use the same wifi name you already have set up -- you don't have to change it. Note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
iii.) pick a Radio Mode. I'm using b/g compatible. You'll want to do the same, unless you are on the new gigabit AEX. I'm pretty sure about this, but not 100% -- others post if I'm wrong.
iv.) choose a Channel. This can be a more complicated procedure, but for now just pick something consistent across all your units. If you get everything working and find that you're having intermittent network problems, you could later try changing your Channel -- it can pick up interference from phones, microwaves, etc and changing it can help.
v.) I have wireless security set to WPA/WPA2 Personal.
vi.) Wireless Password is the password for access to your wifi network (not your unit itself). If you are connecting to your AEBS via wifi while doing this config, then you can use the same password you have already set up. Pick a good one unless you want other folks jumping on your wifi and stealing your bandwidth and/or credit card numbers . Remember it in your keychain and write it down someplace secure, because you'll need it for the other units too. As noted above, note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
vii.) Click the "Wireless Options" button. I have my multicast rate set to 2mbps, transmit at 100%, timeout at 1 hour, and i have checked the "Create a closed network". This last step keeps your network from advertising itself to the outside world. Users can only find it by explicitly typing the network name into their wifi settings (e.g. AirPort -> Other... then enter Network Name, Security and Password). I leave interference robustness unchecked.
c. Under the "WDS" sub-tab:
i.) the AEBS should have it's WDS Mode set to "WDS main".
ii.) Check the "allow wireless clients" box on the AEBS; this lets you connect client machines to it directly too.
iii.) hit the plus button to add the Remote system (AEX). There are two types of configs for the AEX's - "remote" and "relay". Assuming you have 3 units like me (2 AEX and 1 AEBS) the key question is whether you will place each AEX within direct reach of the AEBS (remotes), or if you will have one AEX in the middle connecting to an AEBS on one side and an AEX on the other -- where the furthest AEX is out of reach from the AEBS (remote) and connects only to the AEX in the middle (relay). I'm using a relay setup. If you are using relay, you can still set up the AEX relay to serve client computers too -- it doesnt have to JUST relay. More on that later. For now, you want to add only AEX units that will talk DIRECTLY to the AEBS. So if you have a setup like mine, just add one (the one in the middle - the relay). If you have two remotes connecting directly to the AEBS, you will add them both here. When you hit the '+' button it will ask for both an ID and description. For description I use the name I'm assigning to each unique unit (as above, "kitchen" or XXXXXv1 or whatever you use). For AirPort ID, use the number listed on the AEX unit itself (not the number for "Ethernet", also on the AEX unit).
d. Under the "Access" sub-tab:
i.) I have it set to "Not Enabled". I'd suggest you start that way too, and you can go change it later if you get everything working correctly.
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: Ethernet
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Share a public IP address
b. Under the "DHCP" sub-tab:
i.) DHCP Beginning Address: 10.0 . 1 . 2
ii.) DHCP Ending Address: 10.0.1.200
DHCP Lease: 4 hours
c. Under the "NAT" sub-tab:
i.) nothing should be checked;
ii.) nothing under Port Mappings either
3. Under the "Printers and Advanced" tabs up top:
Nothing special needs to be configured there.
THAT'S IT.
=============
I. Configure your AEX(s)
Select the AEX from AU, and choose "Manual Setup"
1. Under the "AirPort" tab up top:
a. Under "Base Station" sub-tab:
i.) pick a unique name for this unit, same logic as for AEBS
ii.) pick a password specific for accessing this unit, same logic as for AEBS
iii.) Set time automatically: be sure to use the same settings used on your AEBS
iv.) Options: no need to set any
b. Under "Wireless" sub-tab:
i.) Wireless Mode: Participate in a WDS network
ii.) Network Name: same name used for AEBS, this is the name of your wifi network
iii.) Channel: same as AEBS
iv.) All settings here (those above, plus Security and Password & in Options button) should be the same as for AEBS settings on this tab
c. Under the "WDS" sub-tab:
...if AEX is "in the middle" (as described above):
i.) WDS Mode: WDS relay
ii.) Allow wireless clients: check (unless you only want to bridge between the edges without letting folks connect on this AEX in the middle)
iii.) WDS Main: set to the AirPort ID (aka MAC address) for the AEBS. You can find it on the bottom of the AEBS, either labeled as such or at the bottom beside the logo of a wireless signal (square logo, with semi-circles mimicing a radio signal).
iv.) WDS Remotes: click the '+' to add any AEX's that will connect to this relay rather than directly to the AEBS. Same deal as above, use the name in the description and use the AirPort ID from the side of the AEX (not the Ethernet ID).
.....if AEX is connecting to a relay ("on the end", as above) or if there is no relay and AEX connects directly to the AEBS:
i.) WDS Model: WDS remote
ii.) Allow wireless clients: checked
iii.) WDS Main: if connected to a relay, use the AirPort ID of the relay AEX. If connected to the AEBS directly, use the AirPort ID of the AEBS
d. Under the "Access" sub-tab:
i.) MAC Address Access Control: Not Enabled (for now, you can change later)
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: AirPort (WDS) -- should be selected and gray'ed out.
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Off (Bridge Mode)
3. Under the Music, Printers and Advanced tabs up top:
Nothing special needs to be configured there. You can worry about AirTunes settings later...
That should be it. I'd recommend setting up the AEBS first, then the relay (if applicable), then the remotes. Initially, you can bring each unit in the same room with you for configuring. After configured and restarted the AEX should blink then turn solid green. If it turns green you should be good to go.
HOPE THIS HELPS. As noted above, I did not config through AirPort Utility 5.3.1 so I haven't tested this procedure through that app. However, after getting my network to work I went back and transposed all settings into this post to help others. Please provide feedback on whether or not this is working, so we can collectively try to move towards a setup procedure that works for everyone....
Good luck!
Message was edited by: b.byrd

I'm not convinced that the problem lies in Airport Utility. This same thing was happening to me, nearly exactly as you describe it. The thing is that with me, the problems clearly started when I updated the firmware in my Airport Express (n). That's when all the wacky stuff started happening. Sometimes it would show up in AU, sometimes it didn't and even if it didn't, I could still access the internet through it.
But as you said, the problems got really bad when another Express (b/g) was put on the network with it. Even when it did work, the (b/g) would make it impossibly slow.
You know more about this than me, and clearly have more patience if you've restarted the network fifty times. I gave up at about ten.
In any case, your solution is more of a work around and if you're still having that slow connection problem, I'm not sure you've got it. But thanks for your reporting of this. At least I know I'm not crazy.

The Airplay menu shows an Airport Express that is no longer in use.

The Airplay menu in iTunes shows an old Airport Express that is no longer in use. How do I remove it from the list?

That is live, it's not a history of the device. The network you are connected to may have connection with an Express, somehow.

I have a airport time capsule, an older airport extreme, and an airport express. I want to hard wire my Mac Mini to the network. What is the best arrangement of the devices? which ones should be hard wired to optimize extending the network?

I have a airport time capsule, an older airport extreme, and an older airport express. I want to hard wire my Mac Mini to the network. What is the best arrangement of the devices? which ones should be hard wired to optimize extending the network?

I am using TM Unifi with an ASUS RT-N18U Wi-Fi router. I would like to know could I use Apple AirPort Time Capsule to extend (repeater, booster) my Wi-Fi to a part of the house where the Wi-Fi signal is poor
Yes,, if you plan to connect the AirPort Time Capsule to the ASUS router using an Ethernet cable connection that will remain fixed and permanently installed at all times.
No, if you were planning to have the AirPort Time Capsule connect wirelessly and extend the Asus WiFi signal, since it would not be compatible with another manufacturer's router for that purpose.
Another way of saying the same thing here would be that if you want to extend the network wirelessly, it will take two Apple routers to do so

The network on my airport express works, have wifi on the ipods,etc. But when I open airport utility on my mac and on the iphone nothing exists. Why?

The network on my airport express works, have wifi on the ipods,etc. But when I open airport utility on my mac and on the iphone nothing exists. Why?

Reboot the modem. Just pull the power for a few seconds. No settings are lost. The laptop getting through to the internet is not relevent.

Connecting Wireless Samsung BluRay Disc to Airport Express Network

I am trying to connect my wireless capable Samsung BuRay Disc Player to my Airport Express Network. The Samsung keeps telling me to check my IP Address, DNS Server, Gateway etc. I have tried to set it up using the auto option and using the manual option. Neither is working. How do I check that my IP address, etc. is correct for connection??

kalh wrote:
I am trying to connect my wireless capable Samsung BuRay Disc Player to my Airport Express Network. The Samsung keeps telling me to check my IP Address, DNS Server, Gateway etc. I have tried to set it up using the auto option and using the manual option. Neither is working. How do I check that my IP address, etc. is correct for connection??
Welcome to Apple's discussion groups.
I looked at a manual for a Samsung Bluray Disc player. They seem to have left out an important capability: the ability to choose a wireless network and supply its password.
You may be able to use the WPS (Wi-Fi Protected Setup) capability, although that is said to be tricky between Apple and non-Apple equipment. Use AirPort Utility to put your AirPort Express into "manual setup" mode. Invoke the menu option Base Station -> Add Wireless Clients. Then follow the player's instructions for "PBC (WPS)". Use the AirPort Utility option "First attempt". The AirPort Express' status light will turn blue while it waits for a connection from the player.
I have no direct experience with this. All the above information came from the electronic book "Take Control of Your 802.11n AirPort Network" (http://www.takecontrolbooks.com/airport-n).
I have no relationship with Take Control Books other than that of a customer.

Airport Express and Airtunes no longer work error -15006

This is killing me, I feel at my wits end.
I have an airport express that has been in use for two years. I use it only for airtunes from itunes through my wireless network.
I have an apple TV that I added 2 months ago and use occasionally for airtunes, but mostly for all the fine things that apple TV does.
About a week ago, sometime after upgrading to Snow Leopard and before iTunes 9 I have completely lost airtunes connectivity. At first it was just the airport express, but today it is also the apple TV.
When I choose either speaker (apple TV or Airport) from iTunes it just tries to connect forEVER. Sometimes I get the error -15006.
What I have:
24" iMac running snow leopard (wireless)
13" Macbook Pro snow leopard (wireless)
Cisco Router WRT110
Airport Express version 6.3 (wireless)
AppleTV latest software (wireless)
What I have done:
Reset and reloaded the Airport Express a dozen times. It worked for a minute after I changed the settings to require a password, but quickly went back to the same symptoms.
The airport shows up fine in Airport Utility, but will not work for airtunes.
The Apple TV shows up in iTunes and syncs properly, but will not respond to Airtunes. I have checked airtunes settings in the AppleTV and it is on. I even tried turning it off to see if it would improve the airport to no avail.
Please help

Any advice out there? I've even taken bypassed my main Extreme base to plug the ethernet connection directly into the Mac desktop to do software updates that might have been missed by going through the Extreme and wifi. While it did install one security update, it didn't affect the Express units.
I'm wondering about firmware. I have checked over and over for software updates, and my system assures me that everything is up to date. However, I'm concerned that somehow I'm missing a firmware update. My Airport Utility tells me my Extreme is running on Version 5.7, and on the few times one of the Express units shows up, it shows as running Version 6.#.
Do I need to manually install a firmware update, and if so, how? I terrified that I will mess up the ONE wifi unit that is functioning.
Ironically, my Extreme base is the oldest in my batch-both of the Express units are newer than it.

Airport Extreme Killed My Airport Express Network!!!

I have been an apple user since 1992 - NEVER HAVE I FELT SO FRUSTRATED!!!! Sorry to shout, but this is as bad as it gets - my kids are screaming at me and my wife laughing!! I have had a reasonably good Airport Express network running in my house with an Express as the primary and internet connected to it by the ethernet port. I worked fine for my Intel iMac and my daughters Intel MacBook, but my son had problems in his room. We then got an xbox 360 and wanted to connect that so I upgraded to an Airport Extreme - Disaster!. Firstly the net went intermittant! Then I rebuilt from scratch restting all devices to factory defaults; worse and worse, the network kept failing to find various base stations. Finally I cut the Extreme out of the loop and tried to rebuild the original network; now Airport utility won't see any base station after I configue it!! Please help if you can!!!

If nothing works, try a factory reset: disconnect the Extreme from power, press the reset button, plug in power while still pressing the reset button, release reset button after 5 seconds or so.
This method usually helps me with problems with my Airport Extreme and Express (this happens seldom by the way). The only disadvantage is that you have to set it up again completely.

Airport Express network suddenly no longer visible -for one Mac..but wait

Similar Messages

Maybe you are looking for