DrayTek Vigor 120 + Airport Extreme Base Station? I have queries.

Ok, so my 3 or 4 year old USR 9108 router went down today-- again. I'm fed up and want a new one. It dies on me once or twice a month. It has decided it doesn't like my powerline adapters lately. and I'm fed right up. I run an internet radio station and what I need is stability.
At the moment, I'm thinking of setting up a DrayTek Vigor 120 ADSL modem (modem-only) with the Airport Extreme Base Station for my router. (I already have an Express on my network.)
First of all, can anyone please comment on whether they have this set-up and whether it's solid? I've heard good things about both of these devices, and I need something that's not going to flake out as regularly as my USR has been doing of late. Rock solid is a good thing for a 24/7 stream.
Second, can I just confirm a few questions that I think I know the answer to, but want to be sure before shelling out?
I am in the UK using an ISP that uses PPPoA; so I need to be sure the modem has a PPPoA to PPPoE bridge in order for the Airport to talk to the outside world. (Right?). I gather the DrayTek will do this. Will it therefore be just a question of setting the Airport to connect via PPPoE and then entering my ISP login settings in Airport Utility?
I need a setup ideally that, like the USR, will allow me to assign IP addresses manually to some machines or devices on my network but allow DHCP on other things (like my iPhone). It's particularly important that the radio stream should have a static IP. I gather, from having a play with my Express's settings, that I'll be able to accomplish this either directly or by DHCP IP-reservation. Directly would be preferable. Therefore, if I, e.g., assign my computers an IP address on their local network settings and then just shift the Airport's DHCP range so that it starts with (say) 192.168.1.10, rather than, 192.168.1.2, will the Airport be happy with that?
I also need port forwarding / port mapping. This should be o.k., right?
Thanks for help, people.

I'm running a very similar setup here in the UK. I use a Netgear DG834 rather than the Draytek 120 which I was looking at. I use a Time Capsule connected to the router which is in half-bridge mode and this allows me to connect using PPPoE, which is possible on the BT ADSL network, which I didn't know before! - there's no need to get an expensive PPPoA-PPPoE bridge. I guess the Draytek would do an even better job than the Netgear, but mine was the free solution
I use the TC to give out addresses to a network of various kit, with one fixed IP for a specific device. I find the TC and my airport express very easy to set up and run, if slightly light on the details of what's actually going on. That said, if it doesn't work, then they're probably broken!
Nothing you've asked for is out of the ordinary / impossible on the apple kit.
Hope that helps!

Similar Messages

I have an airport extreme base station and have no clue how to set up a private wireless network instead ton open one i have now.

I have an airport extreme base station and have no clue how to change to a pawword type network from the network i have now that is free to the neighbor hood.

Which version of the AirPort Utility are you using?

I have an Airport Extreme Base Station and have recently upgraded to Mountain Lion. Now airport utility won't work with my base station so I bought a Time Capsule. For the life of me I can't make the substitution work and only see a blinking amber light.

I have an Airport Extreme Base Station and have recently upgraded to Mountain Lion. Now airport utility won't work with my base station so I bought a Time Capsule. For the life of me I can't make the substitution work and only see a blinking amber light. Can anyone who has made this change offer some advice?

apikoros wrote:
The Utility transferred all of the AE's settings, so I still have to change the password, which leaves me with only 2 other questions, I think:
1) I assume it's just a matter of using the Utility, entering a stronger password and checking for it to be remembered in Keychain Access. But do I have to change the password for each individual unit-- the TC, the Extreme and both Expresses-- or will changing it just for the TC alone work for the entire network?
Resetting the password you will need to do for each device... the utility cannot even see those old units.
So you will have to do it for each one.. think it through.. because as you change passwords the others will lose connection.. so start from the express which are wireless extending .. change those first.. and go back up the chain.. as each one changes it will drop off the network.. until you reach extreme and change that. Then you might need to reboot the whole network to get everything talking again. If something goes wrong.. just pluck that one out of the mix and plug in ethernet.. reset and redo the setup. That is my preferred method anyway.. do everything in isolation one by one. By ethernet and then nothing goes wrong.
2) Who's the treasonous SOB who spilled the beans to you about the ICBM in my back yard?!?
N.Korean hackers.
[Edit] Whoops-- one more question: I want to partition the TC's disk, but Disk Utility doesn't see it. What do I need to do?
You cannot partition a network disk. And apple provided no tools for it in the TC itself. You can pull the disk out and partition it but that voids your warranty. (although done with care who is to know).
Look at Q3 here.
http://pondini.org/TM/Time_Capsule.html
Mixing TM and data on the TC is worth planning carefully. They don't necessarily sit happily together.

Airport Extreme Base Station N and Buffalo Linkstation

I want to set up a Buffalo Linkstation with my Airport Extreme Base Station
I have two options on the linkstation
1. ethernet
2. USB (female port)
Can I use the NAS over ethernet? Or do I have to use USB? If I use USB will it work if both the linkstation and the base station have female ports.
Will a USB with both male ends work? Who makes that?

I've decided to use the drive as a network drive and I've gone into the control panel and changed all the folders to Mac/PC
Can I use Backup to backup to a network drive? Or is there a better program?

Cannot Connect Airport Express to Airport Extreme Base Station

I have just purchased a new Airport Extreme Base station and have it configured and running properly.
I would like to use my Airport Express to play Air Tunes and have tried to join my Airport Express's network. I have not managed to get this to work.
I have tried to configure the Airport Express manually and in Assist Me mode but every time it reboots to reconfigure the unit, it continues to flash amber. I have done numerous hard resets and followed the methods discussed in other posts but cannot get the unit to connect.
I am running the latest firmware on both units.
Has anyone solved this problem? If so, please help!

Shallers...you are not alone.
I spend several hours this past weekend trying to get a brand new Express to work with a brand new Extreme station using all Apple computers.
Still no luck, after a gazillion permutations.
I really like the Extreme, it works very well, even with non-Apple devices.
The Express is going back....gawd awful thing from the Darkness.

How do I open the same ports on an Airport Extreme Base Station for multiple computers at the same time?

As the title suggests...
I have a mix of five Mac and PC's at home using an Airport Extreme Base Station as the router.   I need many ports opened on the AEBS for all of the computers- not just one computer. (for example: three people want to play TF2 on Steam at the same time; each machine needs the correct ports open on the router).   Port forwarding only allows me to forward a given port to a single IP, yet I need that port open for five differnt IP's, all at the same time.
How do I do that on an AEBS?
In the same way, I have a small office of four iMacs using an old airport with the same exact issue.   I would like to be able to connect to all of them remotely with Apple Remote Desktop, but the port forwarding on the airport only allows a port to forward to a single IP.   I want to be able to tunnel into the office network and log onto any machine behind the Airport extreme... not just a single IP.    I currently have it set up where I can tunnel into the office from my house, I can find the one machine that the port forwarding has been assigned to, I can log on and everything is just fine... with one machine.    How do I open the firewall for the other machines?
TL,DR version: How do you open ports on an Airport Extreme Base Station instead of forwarding ports?   Forwarding ports doesn't work for multiple IP's.

You can open a single or multiple ports to a single device or different ports to different devices, but you cannot open the same port to multiple devices via the AirPort Utility for the Apple routers.

How do I find a hard drive connected to Airport Extreme Base Station?

*Apple Says:* "If your base station supports it, you can connect a USB hard disk to the USB port on your base station and computers on your network (both wired and wireless) can connect to it to access, share, and store files and data."
Cool. So I followed the instructions. The drive is recognized by the base station and listed in the Airport Utility. It looks like it's ready to go...
So... How do I access the drive? I don't see it on my desktop, it's not under network. I've tried "Connect to server..." and browsing, I can't see the drive, anywhere. Yeah, I've searched the crap out of this issue on google and this message board as well as apple support knowledge base. I'm sure this is a simple issue and I'm just missing the obvious. Help me out.

Hello Timothy Uhl. Welcome to the Apple Discussions!
Try the following to mount the disk...
o Click on the Desktop to enter Finder
o Go > Connect to Server...
o Enter 10.0.1.1 for the server
o Enter Disk Password
o Connect
If this still doesn't solve the problem, let's double-check your disk sharing settings...
AirPort Extreme Base Station (AEBSn) - File Sharing Setup
Either connect to the AEBSn's wireless network or temporarily connect your computer directly (using an Ethernet cable) to one of the LAN ports of the AEBSn, and then, using the AirPort Utility in Manual Mode, check these settings:
Disks - File Sharing
o Secure Shared Disks: <With disk password | With base station password | With accounts >
(Note: Choose "With a disk password," or "With base station password" if you want to secure the shared disk with a password, or choose "With accounts" if you want to secure the disk using accounts.
If you choose to use accounts, click Configure Accounts, click the Add "+" button, and then enter a name and password for each user that will access the disk.)
o Guest Access: <Not allowed | Read only | Read and write>
o Share disks over Ethernet WAN port: (unchecked)
(Note: Select the "Share disks over Ethernet WAN port" checkbox if you want to provide remote access to the disk over the WAN port.)
o Advertise disks globally using Bonjour: (unchecked)
o Workgroup: <Windows workgroup name>
o WINS server: <WINS server IP address>

Have 2 airport extreme base stations connected in chain. Airport utility shows slave unit without power. However, power is on slave unit, but status lights do not show up at all. Small green lights at each back port blink. Anyone have any ideas?

Have 2 airport extreme base stations connected in chain. Airport utility shows slave unit without power. However, power is on slave unit, but status lights do not show up at all. Small green lights at each back port blink. Anyone have any ideas?

Unfortunately, you are describing the symptoms of an AirPort Extreme with a failing (or failed) internal power supply.
As a last resort, try a Factory Default Reset on the AirPort Extreme as follows:
Power off the AirPort by pulling the power cord
Wait a minute or two
Hold in the reset button first, and keep holding it in for an additional 8-10 seconds while you simultaneously plug the power back into the AirPort
Release the reset button and allow a full minute for the AirPort to restart
Now try to configure the AirPort again. If you continue to see the same symptoms as before, the AirPort will need to be replaced.

Setting up airport extreme base station with Mac and PC

I have an '02 iBook with an airport card installed and an airport extreme base station. my roommate has a PC and has the DSL connection in her room. i want to wirelessly network my iBook via the airport base. how do i do this? (my base was given to me without any manuals/disks etc)

Your Netgear wireless router is your network's base station. Your parent's PC will not be "serving as a base station" - its presence on the network isn't at all relevant to what you want to do.
To connect your G5 to the Netgear wireless router's network - click on your Mac's Airport menu, click on the name of your Netgear wireless router's network (it will appear in the list when you click on the Airport menu), and enter the wireless network password (if applicable) when prompted by the MacOS. That's is - you are connected!

Configure TC and Airport Extreme Base Stations with different channels

I had to do some serious workarounds to use the Airport Extreme Base Stations as an access point with the same wireless network name primarily due to channel overlap. I thought I would post my results here since I didnt' find a good article online.
Also, I found the Snow Leopard verison (5.4.2) of the Airport Setup Utility far superior to Lion's Airport Utility (6.x) in terms of advanced setup.
Setup is a 3 flloor house where the 3 wired network locations have wireless overlap. The problem was that the access points would not hand off the wireless signal because the channels for each airport/TC were automatically set to the same channel. In non-apple setups, this is how you force a wireless client to switch access points (since the wireless software on your client/mac/windows can detect which access point is stronger and moves to the alternate channel.
Using apple's "Extend this wireless network" option removes any ability to manually configure wireless channels. I am writing this from memory, so feel free to ask questions and I will track this topic:
Procedure
Setup time capsule as your base station. Do all the setup for your wireless and guest networks. Manually configure the network and change the wireless channel to a specific channel for a/b/g networks (e.g., 3) and n networks (e.g, 167).
Plug your first airport extreme/access point into your wired network. Do not plug it into the "internet" ethernet plug, use one of the 3 ethernet switch locations
Use the airport utility to first configure it to "extend" your wired network.
Then, go in and reconfigure it manually in the airport utility. Choose the option to setup a "new network" and name the network the same as the TC wireless network name, security, etc.
Change the channel from "auto" to a different channel than the TC (e.g., 6 and 137).
Now go to the top tab and click on the "internet" icon
Go to the DHCP tab and change it to "bridge mode." This will tell the AE to not give out IP addresses (the TC will do this for you). If you get an error that the IP ranges conflict, you have not done this
Note that if you have a guest network setup, you will need to set this up on the AE as well.
Now test your airport setup. Take your client (macbook, iOS device) and connect to your network. Move to a spot near the TC and pull up a web page. Keep an eye on the signal strength and beginv moving toward the AE. Refresh the page as you move around. You should at some point see the signal strength increase. Refresh your page again. You should be now connected to to the AE. I have found that Macbooks do a better job than iOS devices because you get an extra signal bar to measure strength, and they have larger antennas which allows you to better measure problems with handoff
Another test you can do is to start backing up on your TC and then test the move. The handoff will truly show you that the TC is handling the process but the AE is relaying to the TC for backup.
If you need to setup another AE, simply follow setups 3-10.
I hope this helps others. I've done this setup 100 times on Linksys devices and although they are cumbersome, they at least allow me to do this setup much more quickly and easily than the apple products.

I had to do some serious workarounds to use the Airport Extreme Base Stations as an access point with the same wireless network name primarily due to channel overlap. I thought I would post my results here since I didnt' find a good article online.
Also, I found the Snow Leopard verison (5.4.2) of the Airport Setup Utility far superior to Lion's Airport Utility (6.x) in terms of advanced setup.
Setup is a 3 flloor house where the 3 wired network locations have wireless overlap. The problem was that the access points would not hand off the wireless signal because the channels for each airport/TC were automatically set to the same channel. In non-apple setups, this is how you force a wireless client to switch access points (since the wireless software on your client/mac/windows can detect which access point is stronger and moves to the alternate channel.
Using apple's "Extend this wireless network" option removes any ability to manually configure wireless channels. I am writing this from memory, so feel free to ask questions and I will track this topic:
Procedure
Setup time capsule as your base station. Do all the setup for your wireless and guest networks. Manually configure the network and change the wireless channel to a specific channel for a/b/g networks (e.g., 3) and n networks (e.g, 167).
Plug your first airport extreme/access point into your wired network. Do not plug it into the "internet" ethernet plug, use one of the 3 ethernet switch locations
Use the airport utility to first configure it to "extend" your wired network.
Then, go in and reconfigure it manually in the airport utility. Choose the option to setup a "new network" and name the network the same as the TC wireless network name, security, etc.
Change the channel from "auto" to a different channel than the TC (e.g., 6 and 137).
Now go to the top tab and click on the "internet" icon
Go to the DHCP tab and change it to "bridge mode." This will tell the AE to not give out IP addresses (the TC will do this for you). If you get an error that the IP ranges conflict, you have not done this
Note that if you have a guest network setup, you will need to set this up on the AE as well.
Now test your airport setup. Take your client (macbook, iOS device) and connect to your network. Move to a spot near the TC and pull up a web page. Keep an eye on the signal strength and beginv moving toward the AE. Refresh the page as you move around. You should at some point see the signal strength increase. Refresh your page again. You should be now connected to to the AE. I have found that Macbooks do a better job than iOS devices because you get an extra signal bar to measure strength, and they have larger antennas which allows you to better measure problems with handoff
Another test you can do is to start backing up on your TC and then test the move. The handoff will truly show you that the TC is handling the process but the AE is relaying to the TC for backup.
If you need to setup another AE, simply follow setups 3-10.
I hope this helps others. I've done this setup 100 times on Linksys devices and although they are cumbersome, they at least allow me to do this setup much more quickly and easily than the apple products.

Problem consistently printing via new (summer 2011) AIRPORT EXTREME BASE STATION and Brother wireless printer (model HL5370DW). What am I doing wrong?

Thanks in advance for any help you folks can offer. I'm a newb here and will try to offer as much detail as I can about the dilemma at hand.
Scenario: Home network has been recently set up for wireless internet access via NEW Airport Extreme Base Station (purchased September 2011). Units accessing the network include: 2011 Macbook Pro, 2011 Macbook Air, 2007 Macbook, 2009 Macbook Pro, 2 iPhone 3GSs, and a 1st-gen iPad (and a partridge in a pear tree AEBS is configured to run WPA2 encrypted network, as well as a WPA2 guest network. I am attempting to yoke a BROTHER HL5370DW wireless B or G/ ethernet / usb-capable printer to the main network such that any and all units can print wirelessly or its equivalent (i.e., via printer hooked to AEBS through USB hub)
Problem: Despite configuring the Brother printer to recognize the main WPA2 network I created, I am unable to get wireless printing to work. My workaround was to physically connect Brother printer to AEBS via USB, specifically using a Belkin USB hub (after all, I wanted access to usb drives, as well as the printer). This workaround works ONLY SOME OF THE TIME. Generally, after a fresh boot of any computer or after a restart of the AEBS, any given computer will be able to print (i.e., any computer wirelessly connected to the main WPA2 network recognizes the printer). HOWEVER, at random times, printer access is gone (as is access to USB drives connected to AEBS's usb hub). Wireless networks are still up and running when that happens. IS THERE A WAY TO GET THE USB HUB's devices (i.e., printer and usb drives) to ALWAYS REMAIN AVAILABLE AS LONG AS THEY STAY CONNECTED TO THE AEBS? In other words, what accounts for the intermittent loss of the usb peripherals?
Sometimes, I just shut the airport off on whatever computer is having this problem, and the problem goes away. Sometimes, the problem is present across all computers in the house, sometimes only a few are affected. I can ALWAYS see the AEBS in the Airport Utility if the AEBS is connected to the particular computer via ETHERNET CABLE.
My theories:
- true wireless printing (i.e., without usb hub workaround) doesn't work because the N network somehow isn't backwards compatible with the Brother printer, which, i believe, is B/G. Although...isn't Wireless N networking supposed to work with BG devices? I did find a thread (https://discussions.apple.com/thread/2570774?start=0&tstart=0 ) that explains some of the particulars of WPA2 encryption and Wireless B/G issues, but it was beyond my level of comprehension (I'm a psychologist, but not an Apple Genius
- The usb workaround is only intermittently viable because of some flaw in the Airport or Airport Utility that causes dropouts to happen when a Macbook Pro or Air's lid gets closed or one gets opened after having been at a different network (e.g., at my office).
QUESTIONS:
- Should I try to use my old router (7 year old Linksys WRT54G) as an access point and connect the Brother printer to that G-router? How do I do that?
- I wouldn't mind just relying on the usb hub method if I could just insure more consistency (i.e., no random dropouts of peripherals). How could I do this?
Rule out:
- wireless printing works on my printer - it was being recognized back before the AEBS. I had the Linksys router running a WEP network and had the wireless printer talking with no cables to the router and the computers. (I just don't want to revert to using WEP encryption given its lack of security and my trying to protect HiPAA related health information on behalf of patients)
Any help will be greatly appreciated.
Thanks in advance!

13 ASCII characters = 104 (aka 128)-bit WEP
encryption
If turning off WEP works, then you just need to
provide the cameras with the "Equivalent Network Password".
One of the problems with WEP is that the actual
standard relies on a 10 character HEX key for 40bit
WEP and a 26 character HEX key for 128bit WEP.
In order to make things easier, vendors use certain
algorithms to convert simple alphanumeric passwords
(or passphrases) into HEX keys, thus enabling the use
of simple easy to remember WEP password rather than
lengthy HEX keys. The problem is that different
vendors use different algorithms to generate the HEX
key and therefore a ASCII password on an AEBS will be
hashed differently on a non-Apple client and vice
versa.
You may find the following article helpful:
- Apple article, especially the part about
"Third-party client to Airport".
Brilliant idea about trying the system with No encryption on... that DID solve the problem... almost.. once I turned off the encryption option, and restarted the Airport, I got a dialog box showing that the "Base station needs attention" but it didn't indicate WHAT kind of "assistance" it needed. Nonetheless, I closed out of the Airport program only to find that the indicator light, which had been Green, was now, flashing Yellow and I could not connect anything, including my computer. I opened the Airport program again and found the ONLY way I could get the Green light on was to select some sort of encryption option... then the light would go Green again but my cameras would not hook up again, and when I went back in and ONLY changed the option to NO encryption, I got the yellow flashing light and the "this base unit needs attention" warning...
I think your suggestions are almost on the mark... is there any way of reconciling the WEP coding between the cameras and the Airport??? Or turning off the encryption option and STILL have Airport work?
Thanks again for your help and suggestions... I really appreciate it.
geoff

Mac Book pro can't connect to Internet through Apple airport extreme base station

I had problems connecting to the internet in the past with my macbook pro. One day it suddenly started working again but then I bought a second apple TV I lost connectivity. I have tried changing the IP address manually and while it shows me connected to the wifi I am still with out internet. When I hooked up the new Apple TV that I bought it booted my computer from it's ip address. The apple TV though wouldn't work and now nor would my computer. I ended up setting the Apple TV's ip address manually and now it works fine. My computer on the other hand does not no matter if I set it manually or not. Even if I plug in the ethernet cable from the base station it doesn't work. It show that it has a self assigned IP address. After I set it manually it shows that I am connected both via wifi and the ethernet cable but I can't connect to the internet. If I plug the modem directly into the computer bypassing the base station I get internet and it is using the IP address that worked originally.
It has something to do with the connection from the base station to my computer but this is odd considering every other device I have: iPhone 4, apple tv, apple tv, apple mini with retina display all work perfectly via wifi (newest apple tv had to be set manually as I stated above but now works fine). When I check the ip of the base station itself it seems to be different from the ip of the computer when the computer was connected directly to the router. I don't understand why my computer now can't connect to the internet via the base station whether it be wifi or by ethernet. Can you please help me trouble shoot this?
I have an AirPort Extreme base station which allows up to 50 users and a 30 meg connection speed.
I have a MacBook Pro (17-inch Early 2009), OS X Mavericks (10.9.2)

It has something to do with the connection from the base station to my computer
I don't think so..
I just posted a reply which totally vanished.. strange strange website now.
Please post some screenshots of your AE setup from the airport utility.. I want to see the summary page, then the network and internet tab.
Please tell us what modem you use.. is it a router??
If you have satellite or 3G wimax etc service they often are limited to 5 IP addresses... the AE takes one and then 4 more devices can join .. no more.
You need to also give us the screenshot of the IP you are getting in a computer that works.
EDIT
Sorry this is half double post.. the previous page refused to display.. now it has returned..

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.

How do I set up a wireless network with an AirPort Extreme base station and two airport extreme but between apple devices either by ethernet

How do I set up a wireless network with an AirPort Extreme base station and two airport extreme but between apple devices either by ethernet

This Apple support document provides good general information on configuring different types of neworks using multiple AirPort routers.
http://support.apple.com/kb/HT4145
In particular, you would want to focus on the information regarding a "Roaming Network"

Ghost Drives on my Airport Extreme Base Station.

I have connected 4 external hard drives to my Airport Extreme Base Station via a powered USB Hub. The drives are recognized under he Airport in my sidebar, and I can double click on them and they mount to my desktop. The problem is that none of my data shows up. They appear to be blank. However, when I disconnect the hub from the airport, and plug it directly into an open USB port on my laptop, all the drives come up and mount automatically, and all data is accounted for. Now I'm not a wirless network guru by any stretch, but I assumed it was sharing preferences. I went through and enabled to share connected drives via accounts and entered all required criteria and updated the settings to my Airport. Still to no avail. Also, just for kicks, I opted to Connect to Server from the Go menu in Finder, and attained the network address by mounting the drives individually and gettting info on them, copying the address and entering them into the Server Address, clicking to add them as favorite Servers. Still same result. They mount as an Airdisk, but no content is shown. I know it's an easy fix, but I just do not know what I'm missing???? Any thoughts would be greatly appreciated.
P.S.- MAC for President 2012!

What troubleshooting steps have you already performed?
For example, If you do not connect the powered USB hub to the AirPort and connect only a single drive to the USB port on the AirPort, what happens?
If the drive works, then add the powered hub back in to the setup and connect the drive again. What happens?
If the drive works, add another drive. What happens?
If the drive does not work when you plug in into the powered hub...but it does work when you plug it in to the USB port on the AirPort directly, then you likely have a bad hub. They do fail. Some cheap USB calbles will work, others won't.
If you plug the hard drive directly into the USB port on the AirPort and you still cannot "see" the drive, that suggests a problem with the USB port electronics. Have the AirPort checked out at the Apple store or a servicer.

DrayTek Vigor 120 + Airport Extreme Base Station? I have queries.

Similar Messages

Maybe you are looking for