2 hours to setup Airport Express!
After a couple of weeks delay, my Airport Express finally turned up. As with all Apple kit, the packaging is great and the contents consist of the Airport Express unit and plug, installation CD and user guide. That's it. Whack the CD in the drive to install the AE configuration software and a few minutes later you are asked to reboot your Mac/PC.
So far so good but now it all went a bit pear-shaped for me. In theory you're supposed to be able to run the Airport Express Assistant that gets installed into /Applications/Utilities. Following the steps, it asks you whether you'd like to create a new network or connect to an existing one. Since I already have a wireless network I opted for the latter. The problem here is that my wireless network didn't show up. I see my neighbour's (really should tell them about that one day!) but not mine. Hmmm. I click back and next a few times to refresh the list and still nothing. After a switch back to my wireless network (from the Airport Express default network) I do a Google, only to discover that this seems to be fairly common. Basically, the assistant software isn't picking up my network because it's running with WEP.
Plan 2 - use the Airport Admin Utility that is installed next to the assistant software. This tool gives you the ability to search for Airport base stations on your network and configure them. Well, the express is not yet on my network so I switch my Mac to use the default express network and rescan for base stations. Hurary! The express pops up and I can open the window to configure it. Essentially, the admin utility lets you manually setup the stuff that happens behind the scenes with the assistant. Just as when you connect to an existing WEP-enabled wireless network, the admin utility lets you enter the name of the network and the password/passkey. Great. Click Update and wait for the express to restart. Fire up iTunes. Look around iTunes for any indications of AirTunes. Nothing. Go back to the express user guide. Scan the guide and pick up a tiny bit at the back that says you should choose your express from the speakers popup. What? Where's that? Back to Google and I find the AirTunes page has a screenshot with the popup. Check iTunes version is 4.6 - yep. Restart iTunes. Nothing. Hmmm. Read express user guide again. Unplug express from power and plug it back in again. Status light goes green, then amber, then flashes amber. Look in user guide - amber light means there is a problem with my ISP. Great, thanks for that useful insight, Apple.
So far I'm about an hour in and still nothing. Next I decide to check whether the express works by using the assistant to create a new network. Oh, the assistant doesn't see the express anymore. In fact, neither does the admin utility. Oh, that's because the express can't join a network. Hunt round the house for a staple and force a reset by holding the reset button in for a few seconds. Express restarts and the default network is back again. Follow assistant and after a few minutes I restart iTunes with my new network. Speaker popup appears! Choose the express and enter password. Error - express isn't plugged into any speakers. Very true - it isn't (how do they know that?!). Dig out cable, plug into line out and amplifier kicks into action. Hurray, the Airport Express works but I have to switch networks, which means I can't do anything like surf or get e-mail while streaming music.
Plan 3 - try the admin utility again. Reset express. Reboot mac. Join default express network. Start admin utility and scan for base station. Choose configure from the menu and ask the express to join an existing network. I've had problems with WEP passwords before so I decide to enter the full hex value. Click to update the express and the status light goes green to amber to flashing amber again. Hmmm. Perhaps the hex password needs to be prefixed with 0x. Restart admin utility and no express. Here we go again. Grab staple, reset express, rejoin default network, rescan, reconfigure and enter new password. Ditto the status light story. Time for Google again. Oh, perhaps the hex password needs to be prefixed with $. Admin utility doesn't see express. Grab staple...
Restart express and mac. Status light green to amber to flashing amber. B*llocks. More Googling followed by the Airport Express forum. Read that lots of other people are having grief with WEP. Read about prefixing with 0x. Read about prefixing with $. Scroll through a few pages. Read about people moaning about DHCP not working. Hmmm. Grab staple, join default network, open admin utility, configure base station, prefix password with $, go to Internet tab and enter static IP address information (see screenshot). Click to update express. Status light goes green, stays green, I try not to look away, light stays green! Quickly boot up iTunes and I can see it in the speaker popup. Damn, by now I've moved the express so that's it sitting next to me to poke the reset button easily. Unplug power and move next to the amplifier. Plug back in. Hold breath while express starts up. Green light again! Choose express from iTunes and at last we have music!
I can safely say that setting this thing up is a pain in the a*se. Now it's working, it works a treat. Very cool but more "plug and pray" than "plug and play".
PLEASE HELP -- Airport Express only
However, the Airport SetUp application only describes connecting to a new Airport "Base Station".
I was told that you do not need a base station -- that an Airport Express can work by iteself. Is this incorrect?
If Airport Express does work by itself, how can I configure it?
--Parthage
Re: 2 hours to setup Airport Express!
easy directions to install airport express for home stereo stuff
(very easy directions)
http://discussions.apple.com/thread.jspa?messageID=3695083�
hopefully this will alleviate some stress...and swearing!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express
Re: 2 hours to setup Airport Express from Billy McKeown
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
In the middle none of our Powerbook would connect anymore due to problems with the Ciscos Web-Interface (what we learned later)
Learned a lot about Cisco and Apple quality, about a "$" being better than "0x" since changes are always good and about all the different styles and some funny bugs in Mac OS WEP password interfaces. Listening to music now.
After reading your blog and disabled DHCP, which was the problem and the fact we didn't want to believe.
Used a ballpen, though.
Thanks
-Stefan
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
I ended up finding that all I really needed to do (besides entering the hex WEP key) was to enter a machine name on the internet options.
My Linksys access point/router requires a distinct machine name before it will hand you an IP address via DHCP, apparently; DHCP works fine now.
Incidentally, I did not have to enter a $ before my WEP key, and this was BEFORE getting the software update.
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
I feared the worst after reading this and was very pleasantly surprised!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
In the end I remembered that I had the IPnetShareX (Natd software router) set-up and disabling this solved all my problems - now it works great!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Safari and Explorer crash after awhile
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
-- Joe Posted by Anonymous on 23 August 2004 00:59:54 BST
I had to plug some cat 5 already connected to my network into my APEx after resetting it. Launch APEx Assistant, and not make any changes except let it change my settings to DHCP. Then, close it, load AP Admin Utility, do the "create network" hack to set the real ip. Now select "join network" instead. And it almost worked. I never heard the thing about prefixing the WEP passwords with 0x or $ before... but one thing I had learned in past was my D-Link DI614+ on 128 WEP, did not agree with Apple 128 WEP... My solution there was to simply drop to 40 bit, and voila it worked.
Now, here is the real fun part. My APEx arrived in the mail today. I plug it in, I don't have APEx Assistant... So I slap in the CD... "Can't install, newer version exists" Riiiigh. So I call Apple. An hour and a half later he told me I would have to do a clean install of OS X. Like hell, I seacrhed for every AirPort file, and deleted every last one (including the Receipts he told me not to). Slapped the disc back in, installed the older AP 4.0 software. But now software update doesn't work... ARRRRRGGH!
PS: Guess who took credit for solving the problem? ;) The Apple tech of course.
If anyone gets as frustrated as I, drop me a line I'll do what I can to help - cls@clubnet.org
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 6 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Beside myself with frustration
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
Re: 2 hours to setup Airport Express!
PowerBook with Mac OS X 10.4.2 and one Airport Express using WAP connected to a corporate Windoze network.
My only goal was wireless networking. No USB printer sharing. No music. Three hours down the tubes.
I coaxed the AX to grab an address via DHCP from the server on the corporate Winpooch LAN, but I was unable to get AX to serve IP addresses via its own DHCP server including passing through the DNS servers' addresses.
After getting an IP address from the AX's DHCP server, I was able to ping the gateway, the corporate DHCP server, and the AX only by IP address from the PowerBook, but not by name as no DNS servers were made known to the PowerBook. I was also unable to ping a well connected entity such as cisco.com via its IP address; so, the AX was not forwarding anything to the gateway although it identified it as one. The PowerBook never picked up the DNS servers' addresses when AX served an IP address.
My solution was to turn the AX into an 802.11g only bridge. The PowerBook has two network ports: wired Ethernet and wireless Airport. I shut off its Ethernet port and turned on only its wireless Airport. Because the AX was merely a conduit, i.e. a wireless bridge, TCP/IP configuration was completely under the PowerBook's control.
I was able to tell the PowerBook to ask the Winpooch DHCP server for an IP address through the AX bridge, and that worked well. I did have to set the DNS servers' addresses by hand, but after that the PowerBook runs almost as fast as it does when it is wired into the corporate LAN. By the way, I also had to set the DNS servers' addresses by hand when the PowerBook is wired into that LAN.
That LAN has multiple T3s going to the net, and surfing was subjectively as fast through the AX as it is when wired. Also, tunneling an X Window System session through Mac OS X's ssh client from the net through the corporate LAN and the AX worked well enough to be usable although noticeably slower than when the same is done locally.
I see nothing but woe ahead of me as I still have to configure another AX to serve several IP addresses via the AX's own DHCP server, and turning that one into a bridge won't be enough, but maybe some of the experiences above will come in handy.
Simon is a hands-on software architect and a senior consultant at 
