Apple TV 2 stalls over extended Airport network?

Hello. I have an Apple TV 2 in my basement, right next to an Airport Express (802.11n) that extends my Airport Extreme (802.11n) network - which originates upstairs, in my office. ATV2 reports a signal strength of "five bars" in this configuration. However, if try to access a large video file on my computer (via Home Sharing), it chokes.
Now here's the fun part.
If I unplug my Airport Express, the file plays perfectly. Starts in a few seconds, no skips, no hitches, nothing. Plug the Express back in, and ATV2 chokes on the large file again. I can reproduce this every time. My iPhone/iPad tell me that the signal strength is one tiny bar (and are faster over 3G from this location), yet the files stream seamlessly to Apple TV 2 via home sharing.
Anyone experience similar? Anyone able to configure a similar network that works in this capacity?
I've tried reconfiguring my network, playing with multicast rate, googled for solutions. Can't figure it out. I'd really like to have the Express working with the Extreme; my network coverage in my basement (on the laptop, iPad, iPhone, I mean) is spotty otherwise.
Any thoughts would be appreciated.
jjd

Although the "extend" feature does not impact overall bandwidth significantly, it does use up some bandwidth for extended network administration. What you may be experiencing is that there just enough of a bandwidth loss using the extended network that is affecting the quality of the streams to the Apple TV.
If you prefer to use the Express to extend your wireless network, I would suggest that you try relocating the Express. Even a small distance (inches) can make a difference. At 2.4 GHz, the wavelength is around 5 inches. Better still, to help find the "sweet spot" of where to best place the Express, you can calculate the Signal to Noise Ratio (SNR) of the Extreme's signal at the Express' location.
SNR (in dB = Signal (in dBm) - Noise (in dBm). You will want the SNR value to be 25-30+ for the best performance. If you have a Mac laptop (running Leopard or Snow Leopard) handy, you can easily make this calculation using OS X's System Profiler.

Similar Messages

Mac to mac copy slows down over internal airport network

This is a strange problem but here goes...
Some useful background info:
I have recently downloaded through the new Airport Express network I just created a file that was 212MB from a site on the internet in about 12 minutes or so which is pretty fast for a DSL connection.
The issue:
When I try to copy files from a PowerBook G4 running Leopard 10.5.2 to an iMac G5 running the same version of the OS, I see the same odd behavior (copying from Public folder to any folder on the iMac):
The copy starts in the finder just fine and seems to be going very fast as expected by an internal network copy but after some arbitrary amount of time, the copy slows down and eventually fails. The time to complete the transfer starts out really fast and eventually hits a brick wall where it slows down further and further.
Other notes: the copy I've been attempting is files and folder that are about 1GB total but I've tried it with small and large copies and this has worked fine in the past with Leopard and other OS'.
Sometimes, this slowdown occurs at 5MB into the copy, other times it doesn't happen until it gets about 50MB into the copy. Thew strange thing is, large files over the Internet are just fine as I mentioned above.
There's plenty of free space on the machine that I'm copying to but this happens repeatedly when I try to copy from one computer running Leopard to another.
I don't think this issue is related to the Airport Express because I recently created a new network to test this issue called Bedroom Airport Express. Previously, when I'd been successful performing these types of transfers, I was using the LinkSys WRT54G's built in wireless capabilities and had no issues using Go To and entering the computer's IP address.
When this issue started to occur, I was baffled so I hooked up the extra Airport Express I had lying around and I'm still seeing the same issue despite the Internet transfers working like gangbusters.
The router is still the WRT54G on AT&T's DSL network using DHCP and there's no special config., other than that I had to re-IP the internal network to 192.168.199.1 for work related reasons but that's about it.
The MTU had to be increased to 1492 for the internet to work properly when I got my first WRT54G [an older version of this device that I replaced very recently with a new one]. The firm ware version of the router is v8.00.2 and the Airport Express has been recently updated to the latest firmware available (and this issue was occurring before the firmware upgrade as I added the Airport Express as an troubleshooting method).
Does anyone know where I should begin to try to resolve this issue? I've tried LinkSys tech suppport and I still get "we're not able to provide Mac tech support" reply despite the fact that addressing the router is done via a webpage and the BSD guts under the hood. If anyone knows what if anything I can do to troubleshoot what the issue is, I would greatly appreciate the assistance.
This networking stuff is a bit of a black art to those of us that are dilletantes in this arena and I certainly qualify as a dabbler in this stuff.
Thanks in advance,
<DM/>

I'm new to the Apple discussions, although not new to Apple computers and I've seen that this post has received quite a few views but no responses. Maybe someone could direct me to the right place to post this, if this is not that place, or, suggest some terminal tools that I could use to troubleshoot the issue with the Airport network or LinkSys Router I'm using [WTR54G v.8.0.0.x]? Thanks in advance for any assistance anyone can provide to a networking noobie.

Doubly extended Airport network has become unstable

I have an ethernet-wired Airport Extreme generating a wireless network, extended twice by Airport Express units, with a TiVo wireless adapter getting feed from the 2nd AXpress. TiVo is located about 120' from AXtreme; that's the full length of the network. TiVo currently is receiving an IP address most of the time but is not receiving TiVo information, reporting "Gateway not found" (it has connected reliably in the past). All the Apple equipment is glowing green, both on the equipment itself and on the Airport Utility. All AX are running v7.6.3, my OS is 10.6.8 on a 2008 Mac Pro.
All stations are n-capable. AXtreme is currently set up to "Create a wireless network"; "Allow this network to be extended" is checked, Wireless security is WPA2 Personal.
Relay AXpress is set up to "Extend a wireless network." Should it be "Join a wireless network" or "Participate in a WDS network" instead? "Allow wireless clients" is checked. Security is WPA/WPA2 Personal.
Remote AXpress is set up identically to Relay; should it be different?

I have an ethernet-wired Airport Extreme generating a wireless network, extended twice by Airport Express units, with a TiVo wireless adapter getting feed from the 2nd AXpress.
You cannot extend twice. Apple's "extend a wireless network" function works like the hub and spokes of a wheel.
Your AirPort Extreme is the "hub" and each AirPort Express resides at the end of a "spoke". The devices at the end of a "spoke" communicate directly to the "hub".....not to another device at the end of another "spoke".
You can have multiple devices extending, but each one resides at the end of a separate spoke, since it must communicate directly to the hub.
In your case, the 2nd AirPort Express cannot "extend", but it can "join" the network. It provides no additional wireless coverage when it joins, but the Ethernet port is enabled if you clicked that option in AirPort Utility.
The Express that is "joining" is going to have a tough time unless it is quite close the 1st AirPort Express so that it can get a good signal. If you think about it, you will realize that the wireless signal has to make two separate "hops" to get to the 2nd AirPort Express. Not good.
If you want the 2nd AirPort Express to "extend" the network, it must be physically located closer to the AirPort Exteme than it is to the 1st AirPort Express.
Never use the WDS option, (which Apple tries to hide for good reason) as it only operates at slower "g" wireless speeds and each relay or remote on the network cuts the bandwidth on the entire network in half. So, with a base station, relay and remote in a WDS setup, your network runs at about 14 Mbps. That's about where wireless "b" operates....very, very slow....about 10 times slower than a basic "n" network.

Extended Airport network

A=TimeCapsule connected to Internet
B= AirportExtreme, connected to A, secondary station
C= AirportExpress, new secondary station
According Apple http://support.apple.com/kb/HT4259?viewlocale=en_US
any secondary station must connect to the primary base station, hence to A
Problem:
when for C the signal of B is stronger than from A, then C connects with B. So connection is A -> B -> C.
When this happens C becomes useless, even when its LED turns green. Any device, even when in closest neighbourhood of C, does not connect with C, it tries with B or even A if possible.
C could connect with A, but B overrides with better signal strength and establishes the connection.
How can I force a network where C connects with A, not B?

@Tesserax - I am sure you are correct. I ran iStumbler on one of my MacBooks and found that in the area of the house where the AXn is located, signal strength from the AEBSn was somewhat weak - around 35% or so on both 5Ghz and 2.4Ghz bands, with a good deal of noise from external sources (neighbors' phones and access points, etc.).
It's a bit of a quandary as I'd also like to have the AXn located near a sound system in that part of the house for Airtunes. BTW, streaming over Airtunes (via iTunes or Airfoil) works, but the noise will occasionally knock it out for a few seconds as well. The noise spikes are clearly visible in iStumbler.
I see that the only iron-clad solution is to run an Ethernet cable from the AEBSn to the AXn, but unfortunately that entails a nasty trip into the crawl space under the house, which just creeps me out - all that fiberglas, dirt and spider webs - yuck! It might be worth it in the end, as it would certainly do the job.
For right now, I am just using the AXn for Airtunes, joined to but not extending the network. I'll crawl under the house when the weather is hot and I've had a few beers...

Computer to computer copy slows down over internal airport network over time

This is a strange problem but here goes...
Some useful background info:
I have recently successfully downloaded a 212MB file from a site on the internet through a new Apple Airport Express network I just created as a troubleshooting method in about 12 minutes or so and I don't seem to have any slowing down issues with internet connections to websites and downloads.
The issue I seeing with internal network copies:
When I try to copy files from an Apple PowerBook G4 running Leopard 10.5.2 to an iMac G5 running the same version of the OS, copies over the internal network exhibit a very odd behavior. The copy is from the Power Book G4's Public folder to any folder on the iMac.
The copy starts in The Finder just fine and seems to be going very fast as expected by an internal network copy but after some short arbitrary amount of time, the copy slows down, the estimated times grows slowly but consistently for the copy to complete and eventually the OS says there was a problem and the copy fails. There's no error number of message other than the copy couldn't be completed. As I mentioned above, the time to complete the transfer id initially estimated as a very short amount of time but eventually, the copy action hits a brick wall where it slows down further and further until it fails.
Other notes: the copy I've been attempting consists of files and folders that are of various sizes but I've tried it with small and large copies and this has worked fine in the past with Leopard and other, older OS' over the WRT54G's wireless network. I created the Airport Express network to see if that would solve this problem but it hasn't which makes me think the issue is with the router and not the wireless network.
Additional details:
Sometimes, the reported copy slowdown occurs at 5MB into the copy, other times it doesn't happen until it gets about 50MB into the copy. What's strange to me is, large file downloads over the Internet are just fine. There does appear to be some burst that degrades a bit over time but not like the internal network copy's speed which just drops off really quickly.
I have been successful in the past copying from Mac to Mac over this exact same router using the WTR54G's wireless network but I started having problems fairly recently and now the copy doesn't finish over the WRT54G or the Airport Express network that I recently created to see if the issue was with the WRT54G's wireless network settings or hardware.
There's plenty of free space on the machine that I'm copying to but this happens repeatedly when I try to copy from one computer running Leopard to another.
I don't think this issue is related to the Airport Express because I recently created a new network to test this issue called Bedroom Airport Express. Previously, when I'd been successful performing these types of transfers, I was using the LinkSys WRT54G's built in wireless capabilities and had no issues using Go To and entering the computer's IP address.
The router is still the WRT54G on ATT's DSL network using DHCP and there's no special config., other than that I had to re-IP the internal network to 192.168.199.1 for work related reasons but that's about it.
The MTU had to be increased to 1492 for the internet to work properly when I got my first WRT54G; an older version of this device that I replaced recently with a new one [although this copy worked with the new one as well prior to the issue I'm posting about coming up].
The firmware version of the WTR54G router is v8.00.2 and the Airport Express has been recently updated to the latest firmware available (this issue was occurring over the WRT54G's wireless network before the firmware upgrade to the Airport Express).
If anyone knows what if anything I can do to troubleshoot what the issue is, I would greatly appreciate the assistance.
This networking stuff is a bit of a black art to those of us that are dilettantes in this arena and I certainly qualify as a dabbler in the art of network configuration.
I've been using a LinkSys router for a long time with a Mac/PC internal network that connects to the internet and computers inside the internal network for many years now and have had few issues.
Thanks in advance,
Darin

I'm new to the Apple discussions, although not new to Apple computers and I've seen that this post has received quite a few views but no responses. Maybe someone could direct me to the right place to post this, if this is not that place, or, suggest some terminal tools that I could use to troubleshoot the issue with the Airport network or LinkSys Router I'm using [WTR54G v.8.0.0.x]? Thanks in advance for any assistance anyone can provide to a networking noobie.

Why won't my WPS printer and Tbox connect to my extended AirPort network?

I have an AirPort Extreme (7.6.4) in my home network and recently added an Airport Express to improve the signal coverage. Most devices connect quite happily to the extended network (iPad, iPhones, iMac, Windows PCs).
However, my Epson XP-200 (WPS) printer and Telstra Tbox refuse to connect when the Express is on. If I turn off the Express they both connect fine.
What do I need to do in the AirPort Utility to allow these devices to connect with the Express on?

Are you using the guest wireless network?
Sorry but the solution to some of these things is usually arcane.. if you are not prepared to reset and try again.. it is really hard to suggest other things to do.
But here are some of them.
1. Set specific channels for 2.4ghz wireless.. Do not use 12 or 13 even though allowed in Australia because often US drivers are unaware of those channels.
2. Remove all wireless security.. only as a test.. do the printer and Tbox work if there is no security. You are only testing briefly and do not need to reset everything.
3. Do not use WDS to setup the printer. Plug the printer in by USB to the computer and redo its setup manually from scratch using the utility that came with the printer. This is often much more successful than using WDS with apple stuff. You will need to remove all the existing setups of the printer in the computer and start over.
4. You can also always export the settings.. just change the AE and Express back to factory defaults.. and do as little setup as possible.. you don't have to change anything else except the one computer you use for the setup.. if it fails.. simply restore the settings. If it works you can then change the settings on all the rest of the equipment.. is it really that big a hardship??
5. Why don't you extend using ethernet.. and see if you have the same issue?? You setup using the roaming network method.
http://support.apple.com/kb/HT4260
If the issue is only when you extend wireless then it at least gives you a headstart to complain to Apple about their multiple incompatibilities.

Trouble extending Airport network

I have an Airport Express that works great. I bought an Airport Extreme (mostly for the storage connection). The Extreme is a refurbished unit from Apple. When I configure the Extreme to extend the Express, "bad things" happen. I've been through this several times, resetting the Extreme to factory settings.
The last time the Airport Utility lost touch with the Airport Express entirely. When I reset the Extreme, I have no access to the Express at all. I have to power cycle the Express to get back to a working state. I think this has happened more than once, but I'm not sure.
1) Do I have a bad Extreme?
2) Should I be able to use Airport Utility to configure devices over the ethernet?
3) What else should I be trying?
FYI: Both devices are connected to an internal LAN behind a firewall. I've tried the Extreme connecting to both the "single port" and the "set of ports".
Thanks
David

Well, they warrantee them, but that doesn't mean it that's perfect. Given the "it just works" nature of most Apple products, it's been a less than happy experience, so I want to consider that possibility.
Well, as long as I have two wifi units, I'd /like/ to have them make a larger wifi. Granted, I haven't noticed a range problem before with my Express, so maybe I shouldn't care about that. The primary goal is to have the extreme provide hard-disk storage for Time Machine.
Yes, the computer I'm using to configure them (MacBook Pro) is behind the firewall. It's normally not on the ethernet, but I have connected it at various times during this adventrue.

Extending airport network - Express as Base/Main and Extreme as client

Hi,
I have looked around on these forums and can't find the answer to these questions, so apologies if they have been asked and answered elsewhere.
I have an Airport Express 802.11n which I want to plug in to my cable modem as the base station. I have a Windows PC and network storage drive (ethernet cable connection only) in the other room that I want to join to my network (and can't move the NAS for various reasons).
I am considering purchasing a dual band Airport Extreme 802.11n Gigabit router to put into the second room to allow the NAS to be shared with the PC (NAS and PC connected via Ethernet cable to the Extreme) and a laptop connected over Wifi.
I believe I may be able to use the Extreme to extend the wireless network (is this correct? - do I have to hit control in the Airport Utility to get the Extend option?), but am not sure if this will disable the Ethernet ports on the Extreme. Are the Ethernet ports still enabled if the Extreme is in 'extend' mode? (I have downloaded the PDF of the Extreme manual and it doesn't mention this). If so I will need to configure the Express as a WDS Main and the Extreme as a WDS remote(?) - but I believe I will lose bandwidth doing this - correct? In either of these configurations will I still be able to use the Express to stream music to my hifi in room 1?

Welcome to the discussions!
If you configure your AirPort Express(n) (AX) to "Allow this network to be extended", the AirPort Extreme (AEBS) can be configured to "Extend a wireless network" from the AX.
There is some bandwidth loss in this type of configuration, about 10-15%, but far less than an WDS configuration which will result in a 50% loss of bandwidth. The AEBS will need to be positioned in an area that receives a good wireless signal from the AX
The ethernet ports on the AEBS will be active in the "extend" configuration.
Since the AX creates a single wireless network, you will be losing some features on the AEBS, namely its ability to create dual band networks and a guest network. In the type of configuration you propose, the AEBS would only act as an extending device for the AX and provide 3 ethernet ports for devices.
I'm confused by your question on streaming AirTunes to your stereo with the AirPort Express. If your AX is connected to the modem, the stereo connects to the audio port on the AX, so the stereo will need to be close to the AX.
If you need to stream AirTunes to a remote location, it would make more sense to use a 2nd AX and configure it to "extend a wireless network". Then you could connect your stereo to the 2nd AX. If you need more than 1 ethernet port, you could add a simple ethernet switch to the 2nd AX.

Apple TV no longer connects to Airport Network

I operate an Airport WDS network composed of 2 A. Extremes and 1 A. Express. Several Macs (10.4.11) are connected to the network. So far, the Apple TV used to work fine.
Added a new iMac running 10.5.1. Everything works fine EXCEPT the Apple Network which sees the network but cannot connect to it (Error -3) when I enter the network pwd. Still, this pwd works for every other computer.
I tried everything on the ATV, including a complete reset ("menu" + "-" keys on the remote). Same error again and again.
ATV diags say the device is ok.
How could this be related to my adding one single Leopard computer on the network?
Any ideas or suggestions?
Thanks,

Here's what I found and how to get it working again.
What I found: The TV has network address that is wrong (not the same subnet) as the host mac running iTunes.
The fix - and this depends on your network configuration - you must ensure both Tv and the host computer have acquired IP addresses on the same subnet, say 10.1.1.x and 10.1.1.x+1, or 192.168.2.x and 192.168.2.x+1.. Otherwise iTunes will not connect to the TV.
You will have to force this by setting the IP addresses manually, as I have done.
The clues....
I first looked at the TV to find its network address and tried to ping that from the mac (use the Network utility or the Terminal). This failed which immediately implies the IP addressing is all screwed up.
In my case I have my iMac directly connected to the AppleTV via a wired ethernet connection.
From the iMac to my ADSL is wireless (Airport), and this internet connection is shared to the ethernet connection.
The TV was configured to use DHCP and the network settings shows it expected to find the iMac at 192.168.2.1, ditto the DNS and router.
What I discovered is this. Turn on the TV screen and set TV to show its network settings, then shut down the iMac. In my case ATV then shows N/A for all the IP addresses.
As the iMac is rebooted, the TV is assigned an address in the 192.168.x.x range, and is given 192.168.2.1 for the DNS and router in this range also.
But if I open the iMac's network panel it has self-assigned an address in the 168.x.x.x range, so its no wonder the TV and iMac are not communicating - they cannot because they aren't in the same subnet.
In my case:
iMac: open the network control panel, and set the IP address to "Manual with DHCP". Assign an address - I used 192.168.2.1.
TV: set the network settings to manually adopt an address of say 192.168.2.4, and set it to look for the router and DNS (the iMac) at the iMacs address as above.
Hey presto TV and iMac connect again.
I'm not sure whether the TV or Leopard is at fault, but that I had it working fine in Tiger and that in Leopard, ping failed with the error "unable to allocate resources" leaves me to suspect Leopard is at fault.
Message was edited by: iLuxo
Message was edited by: iLuxo

Can you mix roaming and extended airport networks as such:

I have my main aebs connected to the cable modem. I want to conenct several airport expresses to the aebs via powerlien adapters to form a roaming network. One airport express I cant connect conveniently to powerline so I want to set it up to extend the wireless network as well as acting as a a wireless to ethernet bridge (to connect a Tivo). Any pdroblem mixing these two types of networks?

Several is a lot.. there isn't really enough wireless channels free to make several viable unless you are running 5ghz. You can extend wireless and use the express as ethernet bridge. But it might be worth thinking if you use roaming network naming for the rest of the network.. at least use a different name for the unit you extend.

Question over extending home network

Quick question please: I use a Time Capsule connected to a BT Home hub 3 for wifi at home. Works generally fine though patchy signal downstairs - question is, if I want to extend coverage indoors as currently some poor signal areas, would using Airport Extreme in addition to the time capsule be my best bet? It is not practical to run an ethernet cable so am I am right that I would site the Airport extreme in area of good signal downstairs and that should boost downstairs signal?
Thanks
Andy

Either an AirPort Express or AirPort Extreme could be used to extend the wireless network provided by the Time Capsule.
The only real advantage to using the AirPort Extreme would be that you can connect a hard drive to its USB port. The USB port on the Express will only support a compatible printer.
so am I am right that I would site the Airport extreme in area of good signal downstairs and that should boost downstairs signal?
Correct. The general rule of thumb would be that an extending device should be located approximately 1/2 to 2/3 the distance from the Time Capsule to the general area that will need more wireless coverage.
Depending on walls, ceilings, or other obstructions, you may need to experiment with the placement of the extending device for best results.

Extending Airport Network w/ DVD??

Ok, I've been able to set up a wireless network at home that connects my Apple hi/fi to our Airport Express w/ Airtunes. What I'm wondering is if I can connect my hi/fi to my optical connection on my DVD, then use an RCA out Y cable to the Airport Express unit so I can play both Itunes and my movies.
Anyone?

The Express mini-plug is for connecting either to the audio of your stereo or to audio output for powered speakers.
At this point, and someone may prove me wrong, there are several products out there like Miglia or El Gato, ADC that will allow you to provide a signal to your computer which you can view. I have a Miglia Max TV that takes cable input and allows me to watch it on my television. I am sure that it can be adapted to allow DVD input but no to stream wirelessly to a television. The only system that I know that allows you to do that is Apple TV but you must use iTunes as the source or the iTunes Store but you can stream directly to Apple TV from your DVD player at least not today.

Why am I having trouble mapping a network drive over my airport network?

Unfortunately, all of the computers in our office are Windows machines; so I have some problems getting things to work. I have three computers connected to the network, wirelessly, and 2 computers connected via ethernet. I need all of these machines to be able to access an airport disk. I had all of them working; then I had to change the network name and password because of a security breach. Now, 2 of the wireless connections cannot establish a connection to the disk. I have tried mapping the drive, with no luck. Please advise.

Windows can be very sensitive to changes in network.. it can ram up the firewall and disallow network connections even when internet is still working.
So on the computers that have access issues.. open a command window and ping the IP of the Airport.
If it responds.. try doing a direct connection by typing,
\\10.0.1.1 into the address bar of windows explorer. (replace that IP with the actual IP of the airport).
If it refuses to open when the ping worked.. you can still have firewall issues.. and it is worthwhile turning it off to test.
Also do you have bonjour for windows service running.. check the administrator details in control panel for bonjour??
Do you have the airport utility for windows installed? That can help and at least if the airport utility works then the disk should be accessible.
However other rubbish happens..
Tell me if the two computers with issues do have internet access.. and can ping the Airport.. if you cannot get the disk to open.. !!

Can't print over Airport network while in Windows XP SP2

My printer works fine over my airport network while in OS X, but I can't print when booted in windows XP SP2. I CAN get on the internet over the Airport network while in XP. Can any body help?

Install Bonjour for Windows this fixed my ablity to print via an Airport Base station from Windows.
Search Apple Downloads for Bonjour download for Windows.

Extending Wireless Network with Airport Express / DLink Wireless

I have a DLink wireless router WBR-1310. I own two Airport Express 802.11n's. Can anyone help me out with how I can properly set-up an extended network with these products? All help is greatly appreciated.

You would need one AirPort Express located near the D-Link router and connected to the D-Link with an ethernet cable. This Express would be configured to "create a wireless network" and "allow this network to be extended"
If you have two areas that need more wireless coverage, you would locate an AirPort Express approximately 1/2 the distance between the "main" AirPort Express and the area that needs more wireless coverage.
Then do the same with the second area that needs more coverage.
Without knowing your room layout, I can't honestly tell you whether you need only one "extending" Express or more than that.
It will help to remember that the "extend" setup works like the hub and spokes of a wheel. Your "main" Express connected to the D-Link would be the "hub". Each of the "extending" Express devices would be at the end of a spoke. The Express devices at the ends of the spokes communicate directly to the hub, not to another Express at the end of another spoke.
So, to work well, hopefully your D-Link router and Express will be located in a central area of your home so the extending devices will work around the perimeter.
I would recommend that you study Apple's support document on extending wireless networks before you make a final decision on what to do.
http://support.apple.com/kb/HT4145
Finally, consider if you can connect the two Express devices you have now back to the D-Link using ethernet cables. This would provide much better performance than a wireless only situation.

Apple TV 2 stalls over extended Airport network?

Similar Messages

Maybe you are looking for