HT4262 Can I extend a wired remote base station network via wireless WDS Remote to a Wireless WDS main base station?

I have a wired nework in a remote closet (3 PC's to a 100/1000 Linksys switch). I have an Apple Extreme network connected to the Internet in another remote closet allowing wireless PC's and wired PC's access to the internet and printers. I do not have the ability to connect the two networks together via wired although they are 50' apart.
My objective is to configure two Airport Extreme devices so the remote wired PCs can connect via the remote/relay Airport Extremen to the main Airport base station for DHCP, internet and intranet.
One Aiport Extreme base station is Model # A1034 and the other is Model A1408.

Can I extend......?
Yes, this is possible. But sometimes, the fact that something can be done does not necessarily mean that it should be done. In a case like this....Upsides are far outweighed by Downsides.
Upsides
You will have more wireless coverage (but 50 feet is a long way if there are multiple walls or ceilings in the signal path...I am not optimistic about this)
The Ethernet ports will be enabled on the remote Extreme.
Downsides
The required WDS configuration will drop the performance of your newer "n" Extreme down to wireless "g" levels.
In addition, the bandwidth on the entire network will drop by 50%. In effect, you will have a "g" wireless network running at half speed
WDS is difficult for most users to configure. It is very easy to make a mistake and literally impossible to recover without starting all over again with the configuration attempt
It might work. But things are going to be extremely slow. Might be OK for general Internet browsing or light email. Any file transfers or copies from one device to another are going to take a very long time.
You also might want to review the WDS setup required to get an idea of what is involved here:
http://support.apple.com/kb/HT4262
As you know, a far better way to do this would be to connect the two AirPort Extremes using an Ethernet connection. If you cannot run the Ethernet cable, you might want to consider a pair of Ethernet Powerline Adapters.
These devices send an Ethernet signal over the existing AC powerlines in your home. So, you already have the wiring in place....you just need the adapters. I've used these devices for runs up to 70-80 feet or so with good results. But, you need to understand that there are number of factors that can affect performance here.
So, if you want to try the powerline adapters, I would strongly recommend that you understand the store's return policy in advance. The bottom line is always this.....you won't know how they will work until you install them in your home.
Apple's instructions for a setup using Ethernet are here:
http://support.apple.com/kb/HT4260

Similar Messages

HT4262 Can I extend a WiFi Network, using a 802.11n Airport Base Station with a 802.11g Airport Express?

Having a new Apple AirPort Extreme (802.11n) I need to extend the network since even the AirPort Extreme provides after about 30 Feet maximum only 50% signal strength in 2.4 GHz and maximum 41% signal strength in the 5 GHz band.
I have an Apple Airport Express (802.11g) but I am not sure that it can extend with it the network to get a better signal strength?
I know I can only use the Apple Airport Utility 5.6 to access the AirPort Express, but I can see also the AirPort Extreme though it (5.6).
Also, it seems that my "old" Wireless Motorola Cable Modem (SBG900) for the same distance (about 30 Feet), which is a 802.11g, gives still a better signal strength (62%) than the Apple Airport Extreme...
I guess I need the proper instructions how to, if it is possible.
Any intelligent answers available? Thanks.

This is very confusing. The AirPort Express Base Station has three settings (under "Wireless" in the AirpPort Utility 5.6) "Create a wireless Network", "Participate in a WDS network" and "Join a wireless network".
Whereas the first is self-explanatory the second and third seem to indicate, that a relation with an existing Network can be created. This is also indicated, when selecting as the "Wireless Mode:" "Join a wireless network" and then selecting "Wireless Network Name:" where then all available networks 802.11 b/g/n pop up you can choose which to use.
Now, it does not make any sense, that if all these settings and selections are available, that the AirPort Express cannot extend an existing network, considering that the AirPort Extreme, which is a 802.11b/g/n can be connected to. Even the AirPort Utility 6.0 sees the AirPort Express 802.11b/g but when selected alerts that "This version of AirPort Utility doesn't support this base station. Use AirPort Utility 5.6 to configure or manage this base station. AirPort Utility 5.6 is available at AirPort Service and Support." And as said, that AirPort Utility 5.6 sees everything and has said setting options.
The way as I see this it is, that if I can pickup an existing network, created with an AirPort Extreme 802.11b/g/n with an AirPort Express 802.11b/g and have the option to "Join a wireless network" such AirPort Express should be able to broadcast the picked up and joint network. Otherwise the setting options for the AirPort Express are nothing else than a distortion of reality to me.
Also, before I got the new AirPort Extreme 802.11b/g/n I had an AirPort Extreme Base Station 802.11b/g (gray) and there I was able to extend the network via the AirPort Express 802.11b/g.
So the above comments do not make sense to me.
Hope you understand that and have a better explanation available.

Can I connect a wired device to access network?

I have an Airport Express set up as "Join a Wireless network" Can I connect a wired device to the ethernet port of my AE so that it can access the network?

The Ethernet port is normally enabled in the "Join" mode, if you have one of the newer 802.11n models of the AirPort Express.
If you have an older "b/g" version of the Express, the Ethernet port is not enabled in the "join" mode. Check the model number on the side of the Express. If you see A1084 or A1088, this is an older version of the Express.
Test your current Express to see if the port is already enabled by temporarily turning off the wireless on a laptop and connecting the laptop to the Express using an Ethernet cable. See if you can get an Internet connection. If you can, you know the Ethernet port is working.

How can I extend the range of an Extreme network with Express when my mac won't find the Express???

Cable modem. Properly working Apt Extreme router (g), but inadequate range to upstairs home office. I want to entend with an Apt Express and have a networked USB printer working off the Express unit placed in my office. Mac mini running Lion can't/won't find the Express.
Can you help me? Thanks in advance.
SULLOQUY

If you were able to access the AX using the AirPort Utility but your PC is still not able to connect. I would try performing a "factory default" reset on the AX to see if that helps before going to the store. This type of reset will put the AX back to its "out-of-the-box" configuration which would broadcast an unsecured wireless network with a network name of something like: Apple Network NNNNNN. If your PC still cannot "see" or connect to this network, then a visit to the store would be in order.

Accessing Xserve Desktop Out Of Network via VPN or Remote Desktop

Hi everyone,
Thanks a lot for taking the time to look at my question.
I'm trying to figure out how I would set up an Xserve so that it could operate on a work network while allowing users to access it away from work (at their houses) with a login and password that I've set up in the Xserve. That way they can access specific applications on the server.
I've searched through the forums and other documentation already with moderate success. Apparently I don't NEED a static IP address for my Xserve but it would make it easier. It seems that the most highly recommended solution is setting up a VPN.
So after some further research, I found that the VPN can be set up directly within the OSX server but I'm unclear on how to actually allow it to do what I'm trying to do. I don't want my external users to be able to have any admin rights -- I basically want them to remote desktop into a user account on the xserve with no ability to change any settings, but to access one application on it so they can run that application on the server.
Any help would be greatly appreciated.
Thank you!

If I understand your request correctly, what you want cannot be done out of the box.
Despite Mac OS X Server's ability to support multiple users, it's still limited to one GUI environment/desktop. That means that there's only one set of GUI apps that can run at a time.
You could have multiple users log on using Remote Desktop, but they'd all see the exact same thing. In addition, actions (key presses, mouse movements, etc.) by any one user would be reflected on every other screen, so it's not practical to have multiple users trying to use the same GUI environment.
You need to more clearly define what it is you're trying to achieve. Why, for example, are you trying to run applications remotely over the internet, given the additional latency inherent in this kind of setup)? What do you expect to gain?
More importantly, what application(s) are you trying to run?
Some applications support remote processing (e.g. an application you run locally on your machine submits a job to the server for processing, based on the idea that the server is a more powerful machine).
Other apps support collaboration where multiple users can share the same data and updates are dynamically reflected on other clients.
There are some hacks that emulate multiple desktops, and they might work for you, but you need a better understanding of what you're trying to do.

WDS remote 10x faster than WDS base?

I have a Time Capsule (802.11n) set up as a WDS base, and an Airport Express (802.11g).
The setup is as follows:
DSL ]====[ Time Capsule )))((( Airport Express
My DSL modem serves as the router and DHCP host. Both the Time Capsule and the Airport Express are in bridge mode.
Now, if I hop on the wireless network with my PowerBook, I get downloads in the 500kbps range when it's going through the Time Capsule (looking at connected devices in Airport Utility). But I get upwards of 5000kbps when it goes through the Airport Express. What gives? Why would the Time Capsule, even running in compatibility mode, be an order of magnitude slower?

"1. Should I have set the AEX up as a WDS remote or a WDS relay? Which is the correct setting for what I am trying to do? Does it matter?"
It was correct to set up the AirPort Express Base Station (AX) as a Remote Base Station in the WDS. A Relay would be used between a Main and Remote to extend the wireless even farther. Typically, a Relay wouldn't have wireless clients.
"2. Secondly, with my AEX set up as a WDS remote, I see two networks with the exact same name as my AEBSn (main base station) according to istumbler. The AEBSn shows as 49%, while the AEX shows as 60%. But since they both have the exact same network name, which connection is my wireless client (macbook) receiving? The 49% or the 60%? I can't tell."
That's correct, because with the WDS you extended your original wireless network. To which base station your MacBook will connect to would be the one providing the stronger signal. Most likely the one it's closest to.

PIX 501 config - access to internal network not working from remote VPN users - everything on the inside is OK

One other thing - I had a problem with the key pairing so I rebuilt the rsa 1024 and the unit started working. Unfortunately I reloaded without the config in place and now I cannot get it to work again. Any help will be greatly apprecaited although I did review a dozen other posts of people having similar problems and for some reason there is never any conclusion as to the solution and I am not sure why.
Some other info from the client end:
I just ran the stats on the client and packets are being encrypted BUT none are decrypted.
Also Tunnel received 0 and sent 115119
Encryption is 168-bit 3-DES
Authentication is HMAC-SHA1
also even though the allow LAN is selected in the Cisco VPN client it states the local LAN is disabled in the client stats
also Transparent tunneling is selcted but in the stats it states it is inactive
I am connecting with the Cisco VPN Client Ver 5.0.07.0440
This config works. It is on the internal net 192.168..40.x and all users obtain dhcp and surf the web. It has required ports opened.The problem is that you can connect remotely via the VPN and you receive an IP address from the remote-vpn pool but you cannot see any machines on the internal network. The pix is at 40.2 and you cannot ping the pix and the pix from the remote PC connecting via the VPN and youcannot ping the remote PC from the PIX console when the remote is connected and receives the first IP address in the VPN pool of 192.168.40.25
I need to see the internal network and map network drives. I have another friend that is running the same config and it works but his computer is on a linksys wireless and has an IP of 192.168.1.x and the IP he receives from the VPN pool is 192.168.1.25 so I do not know if the same network is allowing this config to work even if there is an error in the config. In my present case I obtain the ip of 192.168.40.25 from the VPN pool and my connecting pc on 192.168.1.x I really am not sure how the VPN virtual adapter works. I am assuming it routes all traffic from your connecting PC to and from the virtual adapater but I really do not know for sure.
Other people have had similar issues with accessing the internal network from the VPN. One solution was the split-tunnel, another was the natting and another had to do with the encrption where there and an issue with the encrypt and ecrypt which was stopping the communicaton via the VPN.
I still cannot seem to find the issue with this config and any help will be greatly appreciated.
This is the config
interface ethernet0 100full
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password somepassword
hostname hostname
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
object-group network internal_trusted_net
network-object 192.168.40.0 255.255.255.0
object-group icmp-type icmp_outside
icmp-object echo-reply
icmp-object unreachable
icmp-object time-exceeded
icmp-object source-quench
access-list OutToIn permit icmp any xxx.xxx.xxx.0 255.255.255.248 object-group icmp_outside
access-list no_nat_inside permit ip 192.168.40.0 255.255.255.0 192.168.40.0 255.255.255.0
access-list split_tunnel permit ip 192.168.40.0 255.255.255.0 192.168.40.0 255.255.255.0
access-list OutToIn permit ip any any
access-list outbound permit ip any any
(NOTE: I had many more entries in the access list but removed them. Even with the above two allowing everything it does not work)
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside xxx.xxx.xxx.xxx 255.255.255.248
ip address inside 192.168.40.2 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpn_client_pool 192.168.40.25-192.168.40.30
pdm history enable
arp timeout 14400
global (outside) 1 interface
I had this statement missing from the previous posted config but even with the nat (inside) 0 access-list no_nat_inside it still does not work.
nat (inside) 0 access-list no_nat_inside
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group acl_outside_in in interface outside
access-group outbound in interface inside
route outside 0.0.0.0 0.0.0.0 xxx.xxx.xxx.xxx 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
http server enable
http 192.168.40.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community $XXXXXX$
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set 3des_strong esp-3des esp-sha-hmac
crypto dynamic-map clientmap 50 set transform-set 3des_strong
crypto map vpn 50 ipsec-isakmp dynamic clientmap
crypto map vpn client configuration address initiate
crypto map vpn client configuration address respond
crypto map vpn client authentication LOCAL
crypto map vpn interface outside
isakmp enable outside
isakmp identity address
isakmp client configuration address-pool local vpn_client_pool outside
isakmp nat-traversal 20
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash sha
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup remote-vpn split-tunnel split_tunnel
vpngroup remote-vpn idle-time 10800
vpngroup remote-vpn password ANOTHER PASSWORD
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh 192.168.40.0 255.255.255.0 inside
ssh timeout 30
console timeout 60
dhcpd address 192.168.40.100-192.168.40.131 inside
dhcpd dns xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd enable inside
username AUSER password PASSWORD privilege 15
terminal width 80
****************** End of config
I have been searching docs and other people's postings trying to obtain the info to make this work. It appears pretty much boiler plate but I believe my problem is in the natting. I am using a range in the internal network for the VPN pool and I have tried switching this to other networks but this has not helped. Unfortunately I have been unable to get the PDM to work and I believe this is a PC config thing and I did not want to waste the time on it. I read a post where a person using the PDM interface with the same problem (not being able to access the internal network) was able to go to a section in the VPN wizard and set the Address Exeption Translation. They said they originally set the VPN subnet when they did not have to. Many of the other blogs I read also stated that if the natting is not proper for the VPN pool- that it will not work but I am confused by the examples. They show as I do the complete range for an access-list called no_nat_inside but I believe it should only have the VPN pool IP range and not the entire network since the others do require natting - not sure if my thought process is correct here. Any help will be greatly apprecaited. Also this morning I just tried a boiler plate example from CISCO and it also did not do what I need for it to do. And I also connect a PC to obtain an IP to see if I can see it - no good. The PC can ping the PIX and viceversa but no one can ping the remote PC that connects via the CISCO Remote VPN client even though it receive an address from the vpnpool. Also include LAN is checked off on the client. This was mentioned in anther post.
Thank you once again.

Hi,
PIX501 is a very very old Cisco firewall that has not been sold for a long time to my understanding. It also doesnt support even close to new software levels.
If you wanted to replace the PIX501 the corresponding model nowadays would be ASA5505 which is the smallest Cisco ASA firewall with 8 switch port module. There is already a new ASA5500-X Series (while ASA5505 is of the original ASA 5500 Series) but they have not yet introduced a replacing model for this model nor have they stopped selling this unit. I have a couple of them at home. Though naturally they are more expensive than your usual consumer firewalls.
But if you wanted to replace your PIX firewall then I would probably suggest ASA5505. Naturally you could get some other models too but the cost naturally rises even more. I am not sure at what price these are sold as used.
I used some PIX501 firewalls at the start of my career but have not used them in ages since ASA5505 is pretty much the firewall model we use when we need a firewall/vpn device for a smaller network/branch site.
Here is a PDF of the original ASA5500 Series.
http://www.cisco.com/en/US/prod/collateral/vpndevc/ps6032/ps6094/ps6120/prod_brochure0900aecd80285492.pdf
Here is a PDF of the new ASA5500-X Series
http://www.cisco.com/en/US/prod/collateral/vpndevc/ps6032/ps6094/ps6120/at_a_glance_c45-701635.pdf
I am afraid that its very hard for me atleast to troubleshoot this especially since I have not seen any outputs yet. Also the very old CLI and lack of GUI (?) make it harder to see what the problem is.
Could you provide the requested outputs?
From the PIX after connection test
show crypto ipsec sa
Screen captures of the VPN Client routing and statistics sections.
- Jouni

How can I extend a wireless network with my AirPort Extreme Base Station?

Today I purchased a brand new, dual-band base station to replace my Belkin N router, as I have had a handful of firewall, coverage, and other networking problems in my house lately. First off, I really like this router and it was very easy to setup. My MacBook Pro could use both bands and established a 300 Mbit/s link very quickly. After tweaking various settings to my liking, I was also able to maximize the connections on many of my non-Apple machines and devices. I noticed that the range of its network was better than my Belkin's, but unfortunately, it failed to completely saturate the area sufficiently. Since the Belkin still works well enough, I was hoping I could bridge them together one way or the other.
The Belkin router does not support any bridge mode that I know of, but the AirPort Extreme should be able to join a wireless network and then extend that over WiFi and Ethernet, correct? I would like to place them at opposite ends of my home so I can get strong WiFi signals everywhere inside. However, when I try to get the base station to connect to my preexisting WiFi connection, it tells me that I can't extend the network and fails to join.
So is this possible? And if it is, how would I go about setting it up? I know it would probably be easier if I had a simple range booster such as an AirPort Express, but I didn't buy one while I was at Fry's since I hoped I could make use of the older Belkin. This is its product page, if needed. Thanks for any suggestions.
-MacUser

The Belkin router does not support any bridge mode that I know of, but the AirPort Extreme should be able to join a wireless network and then extend that over WiFi and Ethernet, correct?
Sorry, but no. The AirPort Extreme Base Station cannot "join" a network like the AirPort Express or Time Capsule, but you wouldn't want to do this anyway because in this configuration these devices will only perform as wireless clients ... not routers.
Instead, the AirPort Extreme can either be extended or can extend another 802.11g or 802.11n AirPort ... or a very very few non-AirPort devices.
One option for your Belkin would be to connect it to the AirPort Extreme by Ethernet but this may not meet your requirements or be a desirable situation. Otherwise, you would need to get another AirPort to extend your current one.

Can I extend a network with an AirPort Extreme Base Station Rather than with an Express?

Topic title pretty well sums up the question.
I have a TimeCapsule Base Station with two Expresses for extending the network through the house.
We're doing a 3 room addition, and there is not a convenient place to put an Express in a wall outlet in the middle room of the addition, but there's a perfect place to put an Extreme on top of a piece of furniture.
So, can the Extreme act as an "extender" only, in lieu of using an Express?

pcbjr wrote:
Topic title pretty well sums up the question.
I have a TimeCapsule Base Station with two Expresses for extending the network through the house.
We're doing a 3 room addition, and there is not a convenient place to put an Express in a wall outlet in the middle room of the addition, but there's a perfect place to put an Extreme on top of a piece of furniture.
So, can the Extreme act as an "extender" only, in lieu of using an Express?
Hiya.
You can absolutely extend a network with an Extreme. I've got a 5th gen. Extreme extending a network created with a 3rd gen. Time Capsule. On the Extreme, you'll have the option to allow (or not) WiFi clients. I recommend having all units updated to the current firmware (7.6.1 as of this writing). Note that extending doesn't work in daisy-chain fashion, meaning that your Expresses or Extremes will each connect to and extend from the TC. As such, you'll want the TC to be in as central a location as possible to offer the best coverage.

Can you run a wired router from the base station?

I have a Airport Extreme base station, I bought it about 6 months ago so it's not too old. My question is can you plug a wired switch, hub or router into it? I was told no at the apple store but I don't see why you could not. All I want to do is run a 8 port switch from the base station so I can connect my other wired comps to the net. Thanks!

My question is can you plug a wired switch, hub or router into it?
Yes, just connect it to the LAN port on the AirPort Extreme base station (AEBS).
I was told no at the apple store...
They gave you incorrect information.

Am I right in thinking that you can't extend your network wirelessly with a time capsule unless your base station is an apple one?

My new time capsule will only allow me to extend my network via ethernet cable.
What I really want to do is use it wirelessly as an extension wirelessly.
The option is there (under other options in airport utility) but when I select it and move on it reverts back to create a new network.
Why is this?
Am I trying to achieve the impossible?
I have an airport express and that be added to my network wirelessly with no issue at all.
Please help
Russell

Can I just "join" the network with my time capsule like I have with my airport express?
Apple does not present this option....but, even if they did.....this would be the worst possible option to use for backups.
Can I use my airport express as a base (connected via Ethernet to the router) for my time capsule to extend from wirelessly?
Yes, you can. The AirPort Express would be configured to "create a wireless network"......then.....the Time Capsule could be configured to "extend a wireless network".
It is critically important that the Time Capsule be located where it can receive a very strong wireless signal from the AirPort Express in this type of setup. The more that you have line-of-sight between the AirPort Express and Time Capsule, the better your network performance will be and the faster that backups will occur to the Time Capsule.
A better option in terms of performance would be to connect the Time Capsule to your current modem/router using an Ethernet connection and have the Time Capsule "create" the network. Then, use the Express to "extend" the network.
Here, I am assuming that you have a new Time Capsule.

I used Airport Base station and I was able to extend my network using airport express and connect my printers. Now I am using Extreme and I can't extend the network (Express) or the printers nothing shows up. I am using utility 6.3 and Mt Lion What is

I had an Aiport Base Station and extended using Airport Express, where I also connected my printers (network). Now using Airport Extreme off Mt Lion 10.8.4 and Utility 6.3.
I can't extend the network (express) or connect my printers (USB) nor will it find my one wifi printer.
What's up?

For now, leave the AirPort Express powered off.
Power off the entire network....all devices.....in any order that you want
Wait a few minutes
Power up the modem first, and let it run 2-3 minutes by itself
Power up the AirPort Extreme next, and let it run a full minute
Keep powering up devices one at a time about a minute apart until everything is powered up (leave the Express off for now)
Open AirPort Utility and check to see if the AirPort Extreme is visible.
If it's not, click the AirPort Utility menu at the upper left of the screen, then click About AirPort Utility. Post back with the version number of AirPort Utility that you see there....which should be AirPort Utility 5.6.1.
Post back on your progress.

Why can't I extend my wired TC port with linksys switch?

Why can't I extend my wired TC port with linksys switch?

Temporarily, connect a laptop to one of the LAN <-> ports on the TC using an Ethernet cable. Turn off wireless on the laptop. Can the laptop connect to the Internet?
If yes, you know the port is working and the Ethernet cable is working.
If yes, connect the switch to the same Ethernet cable. I assume that you are using an "unmanaged" switch. Some switches may need to be powered off and restarted.
If no on the first test, try another Ethernet cable that you know is working. Try another LAN <-> port as well.
The whole idea is to start at the TC and work outward step by step, checking each connection and step along the way.

HT4145 I have an Airport Extreme bas station now and I want to know if I can use an Airport Express to extend my network or do I have to use another Airport Extreme base.

I have an Airport Extreme Base Station now and I would like to know if I can use an Airport Express to extend my wifi network or do I have to use another Airport Extreme Base Station.

This AirPort Express:
http://www.apple.com/airportexpress/
It is the only Express with 2 Ethernet ports. All others are "old"
Apple does not specify a model number in their product information, but it is A1392 in the U.S. I do not know if Apple uses different model numbers in other countries.

Can't extend my existing Express b/g WDS network with new Express n

Hi all,
For the past 2 years I have been using a very simple Airport Express b/g wireless network setup. I have two of the older generation b/g Expresses and I've created a WDS network where the main Express is connected to my broadband modem and participates to my WDS as "main" and the relay Express is configured to participate to this WDS as "relay". This setup works flawlessly and I was very happy with it. Note: the firmware version on both units is 6.3.
Recently, I wanted to extend the range of this network. I've bought and received the newer generation Express n. To my surprise, setting it up to extend my already existing b/g WDS is simply impossible. Below is a summary of the situation:
1) The firmware was updated to 7.3.1 as soon as I opened the Airport Utility.
2) The automatic setup wizard in Airport Utility was incapable of extending my current b/g WDS with the Express n. (Green light on but no wifi coming from the new Express n).
3) I've tried countless times to reset and manually reconfigure the new Express n as "remote" in the WDS configuration panel and connect it to either my "main" Express (b/g) or the "relay" Express (b/g). Both "main" and "relay" Expresses (b/g) were also configured to extend WDS to the new "remote" Express n. I've tried to scrupulously follow instructions found in other posts/discussion forums on how to do that.
4) I then tried to make the new Express n as the "main" base station in the WDS. I could successfully connect it to the Internet (Express n connected to broaddand modem via ethernet) and receive wifi from it, but it was impossible to establish a working WDS with my other two b/g Expresses, both reconfigured as "relay" and "remote" in the WDS (again using the instructions from people who succeeded in having both b/g and n units in the same WDS).
5) Adding to all the difficulties in configuring, hard-reseting and reconfiguring each Express, I would very often be in a situation where Airport Utility only sees 1, 2 or none of my 3 Expresses. Rebooting my Mac was the only thing that enabled me to see them again.
6) After about 7 hours trying to figure out how to work this thing without any good results, I've decided to call out for help. In my situation, there seems to be an intrinsic incompatibility between older b/g Express and the newer Express n, at least for WDS network setup.
If anyone is in the same situation and has found a solution to the problem your help will be much appreciated.
Thanks in advance.

Good news everyone: don't despair, there is hope! After nearly 10 hours of configuration, I finally have a WDS with all three AXs (two b/gs and one n). woohoo!
OK, so here's how I did it:
The main idea here was to replace my "relay" b/g AX with the new n AX.
1) The first thing I did was to reconfigure my "main" b/g AX (the one connected to my modem) so that it can transmit to the new n AX: I simply added the Airport ID of my new n AX in the WDS "remotes" list inside the WDS configuration panel of the "main" b/g AX. I then did an Update Reboot on the "main" b/g AX.
2) After that, I did a Hard reset on the new n AX and plugged it near my old "relay" b/g AX. I then went in Airport Utility, scanned for the new n AX and asked the wizard to "Replace an existing Base Station". It gives you a list of all the base stations your computer has interacted with. I selected the old "relay" b/g AX. The wizard then asked to unplug the base station that is going to be replaced. Did that, and then I did an Update Reboot on the newly configured "relay" n AX.
3) I've rechecked the configuration of the new "relay" n AX, and to my surprise, it wasn't exactly the same as the one for my old "relay" b/g AX. Specifically, I had to manually reconfiguring the whole WDS settings. I had to tell it to "Participate in a WDS", re-input the Aiport ID of the "main" AX and also put the Airport ID of the "remote" AX (the old b/g I'd replaced see below - 5) in the "remotes" list. Once that was re-configured, I updated and rebooted.
4) At that point I had wifi coming from: my "main" b/g AX and now my new "relay" n AX. Yeay! that was the first time I had interaction between b/g and n units.
5) I then went to reconfigure the old "relay" b/g AX and set it up as "remote" and connected it via WDS to the new "relay" n AX. Configuring a b/g AX is a piece of cake compared to the newer n AX!
6) I am very happy to report that it all simply works now! All three AXs are happily talking to each other now. Hooray!
I am almost clueless on why performing these specific steps made it work but it did. My reasoning is that by letting Airport Utility automatically configure the n AX with the configuration data of an old b/g AX it might have changed some settings that were too hidden from view when done manually.
Thanks to dchao99 for input, and Mike hang in there. Try to follow my steps, it might also work for you!
Good luck to all of you.

HT4262 Can I extend a wired remote base station network via wireless WDS Remote to a Wireless WDS main base station?

Similar Messages

Maybe you are looking for