Wireless issues hooking up 3 airports as extenders

Hi everyone,
I am really in a bind, I need to hook my wireless router downstairs (motorolla wireless router hooked up to vista {newest beta}) to my airport extreme base station upstairs (wirelessly) and have the base station act as both my wireless extender for my macpro and a wired extender for my ps3. What am I doing wrong? I can get the internet from the router downstairs to work on my macpro so the problem cannot be anywhere there it has to be with the airport extreme base station is there something I am not doing? do I need to set the wireless network up downstairs as a host and well I will just let you respond and hope I don't need more details. Thank you very much.

Check this out.
http://docs.info.apple.com/article.html?artnum=120061. Use Airport setup assistant to set up the extreme as a WDS wireless access point. Connect the extreme to your Macbook with an ethernet cable temporarily for the set up process. During the setup make sure the motorola wireless router is working so the extreme will find its network ID during the setup.

Similar Messages

MacBook wireless issue (ongoing) & DIY airport card replacement

Hello,
With reference to the ongoing MacBook/OSX (10.5.3) Leopard intermittent wireless issues discussed in this forum has anybody gone ahead and taken matters into their own hands and purchased and installed a new Airport card for their MacBook from www.ifixit.com?
Further details at: http://www.ifixit.com/MacBook-Parts/MacBook-Core-2-Duo-Santa-Rosa-Penryn-802-11n -Airport-Extreme-Card/IF186-062
If so, did it resolve your intermittent Airport issues?
It seems to me that when the MacBook is running on battery power only the Airport card does not realise that the MacBook has come out of sleep sometimes and therefore does not always function correctly. Maybe the Airport card does not receive sufficient power when the MacBook comes out of sleep mode whilst running on batteries only?
Typically when I run the MacBook connected to power the intermittent wireless problem does not occur.
This issue has been a recurring problem for me for 6 months now and unfortunately I have not seen Apple address this issue.
My MacBook is 6-months old and is a black MacBook using a 2.2GHz processor running Leopard OSX 10.5.3.
Cheers,
treaders

Visit Apple Store and replaced the Airport card.

Macbook airport wireless issue

Hello,
I have a macbook from around 2006/2007, and up until last year has been very reliable and something that is still quite speedy.
I have an issue with the airport/wireless on the mac, whereby the signal is so intermitnent and sometimes non-existent. My internet (virgin internet super hub) works perfectly with all my other devices (iphones, ipads etc) so it's just this one device.
When I start the mac up, first of all it stats that the connection times out and unable to connect. It also wont connect when I'm around 10 feet away or further so I have to sit quite close to the router.
After around 5 minutes the signal builds gradually in strength, and gets to 1 bar, then jumps up and down from full (4 bars) to 1 bar whilst connected, never stable - this allows me to connect (just about).
I have just done a test with my iPhone and set my iphone perso
I am running Mac OS X 10.5.8 and have done all the updates for airport and software.
Right now whilst I'm writing this message the wireless strength has dropped from 3 bars and I'm now on the lowest bar.
I have had a few people look at this and the airport card (to my knowledge) has been replaced yet we still have this issue.
I also have an issue where if I unplug the power the computer instantly dies so I presume the battery is dead and needs replacing, however it works fine as long as it's plugged in. The main issue is this wireless issue which would be amazing to fix and get this old beast working perfectly again.
Any thoughts on what we can do? As stated, the internet works perfectly for all other devices and we've switched since and still have the same problem so I;m 99.9% sure it's the computer.
Many thanks for your help and look forwawrd to some feedback
James

Update:
I have since added a new user to the account and the problem still persists on the other user account.
I have also ran a 'network diagnostic' however because the internet kept dropping, it either stated that there was no problem or it wouldnt run at all. I have installed iStumbler and it shows signal strength ranging between 24% - 32% and the graph shows it is dropping out quite frequently.
I have seen people recommending i switch from channel 11 to channel 6, but not sure it will be this simple as we have changed routers and internet numerous times...
Any thoughts?

My wireless iBookG4 sees my new Airport Express, but my PowerMac G5 won't!

My wireless iBookG4 sees my new Airport Express, but my PowerMac G5 won't!
I find this really strange. I have a cable modem coming in. There is an Airport Express hooked up to it. I use this to allow free movement about the house for my iBook, bhile my PowerMac g5 stays wired via ethernet.
Now I have purchased a second Airport Express for the living room, hooked up to BOSE speakers. The iBook sees the new Airport Express and can brpadcast iTues to it, no problem. The problem IS, I can't get the PowerMac to see the new Airport Express AT ALL--- it only sees the original one (the one that has the ethernet connected to it) PLUS--- the new Airport Express LCD flashes amber, not green... what is going on???

The new Express is not really on your network but is able to communicate with the laptop using Bonjour. Here's Apple's explanation for the flashing amber:
Startup is complete, but AirPort Express didn't get an IP connection. Depending on your setup, it may mean AirPort Express is out of network range, unplugged from Ethernet, lacks a path to the Internet (or local router), or that there's an issue with your Internet service provider.
Does your PowerMac G5 have an Airport card? If it does then it isn't associated with the new Airport. Both should be listed under the Airport menu but only one has a checkmark. If it doesn't have a card it won't be able to see the new Airport until you configure the new Airport as an extension of the first wireless network, called WDS or Wireless Distribution System.
Start here for more info:
http://www.apple.com/support/airport/

New MacBook Pro 13 i5 Wireless Issues.

I got the new MacBook Pro i5 2.3 the day it came out. So maybe a week and half ago.
I`m having intermittent wireless issues. I have done some testing and even replaced my older AirPort Base Station with the new Dual-Band one, but still seeing a drops from the network. I have a ping going to my router and to the ABSE. I tried changing the channel and using 5GHZ or 2.4GHZ. I also have a AirPort express and seen similar results. I tried reseting the PRAM, repairing permission, I did not reinstall the OS but I dont see how this would help. I think there is a hardware issue with the wireless card/antenna.
I did upgrade RAM and HDD was changed to SSD (intel G2 SSD). There are no other issues, machine is fast, no lock ups. Other devices on the network do not seem to drop any connections (ATV, ATV2, iPhone4, iPad etc..)
The network drop outs are short but are noticeable and if a ping is going I can see the drops
*-- 192.168.1.1 ping statistics ---*
*1527 packets transmitted, 1505 packets received, 1.4% packet loss*
*round-trip min/avg/max/stddev = 0.779/12.203/396.084/42.274 ms*
Any help is appreciated as I`m really frustrated but this issue.

Here are some of the pings.
+*64 bytes from 192.168.1.3: icmp_seq=2190 ttl=255 time=1.138 ms*+
+*Request timeout for icmp_seq 2191*+
+*Request timeout for icmp_seq 2192*+
+*64 bytes from 192.168.1.3: icmp_seq=2193 ttl=255 time=1.701 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2194 ttl=255 time=1.653 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2195 ttl=255 time=1.723 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2196 ttl=255 time=1.470 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2197 ttl=255 time=1.435 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2198 ttl=255 time=1.217 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2199 ttl=255 time=1.115 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2200 ttl=255 time=1.433 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2201 ttl=255 time=1.002 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2202 ttl=255 time=1.057 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2203 ttl=255 time=1.222 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2204 ttl=255 time=0.769 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2205 ttl=255 time=0.821 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2206 ttl=255 time=0.723 ms*+
+*Request timeout for icmp_seq 2207*+
+*64 bytes from 192.168.1.3: icmp_seq=2208 ttl=255 time=54.892 ms*+
+*Request timeout for icmp_seq 2209*+
+*Request timeout for icmp_seq 2210*+
+*64 bytes from 192.168.1.3: icmp_seq=2211 ttl=255 time=1.313 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2212 ttl=255 time=0.936 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2213 ttl=255 time=1.839 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2214 ttl=255 time=0.879 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2215 ttl=255 time=63.446 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2216 ttl=255 time=24.384 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2217 ttl=255 time=105.923 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2218 ttl=255 time=41.322 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2219 ttl=255 time=1.853 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2220 ttl=255 time=0.811 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2221 ttl=255 time=0.721 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2222 ttl=255 time=0.791 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2223 ttl=255 time=3.816 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2224 ttl=255 time=1.052 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2225 ttl=255 time=0.688 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2226 ttl=255 time=89.272 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2227 ttl=255 time=49.459 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2228 ttl=255 time=15.891 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2229 ttl=255 time=0.745 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2230 ttl=255 time=0.724 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2231 ttl=255 time=0.680 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2232 ttl=255 time=1.950 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2233 ttl=255 time=0.600 ms*+
+*Request timeout for icmp_seq 2234*+
+*64 bytes from 192.168.1.3: icmp_seq=2235 ttl=255 time=0.725 ms*+

This is a workaround for the MBP wireless issue

There have been many topics on the MBP wireless issues already, but I thought some people might find this workaround helpful.
Firstly, my system is a 2.2Ghz MBP, running 10.4.10, and also airport extreme update 2007-04. I am using an airport express base station. My previous Powerbook never had any wireless problems, so I really couldn't blame the basestation for the MBPs poor wireless.
Warning - The workaround requires a little bit of work in the terminal. A little bit of understanding of how networks work is assumed here as well. So it is probably not for everyone ...
What I have observed - whenever the MBP loses connection, the airport basestation IP and MAC addresses are missing from the ARP table.
- To view the ARP table, type (in a terminal window) arp -a.
So, when the MBP wireless hangs, open up the terminal and type that in.
Do a Cntrl-C if the arp command is hanging and not returning anything.
In normal situations, a list of IP addresses and MAC addresses will show up.
As others have already noted, clicking on the airport icon in the menubar, will magically bring the wireless back to life. When this happens, the ARP table also gets magically populated correctly. Coincidence? I think not!
So, the workaround is to store a PERMANENT entry in the ARP table for the airport basestation IP and MAC address. In my case, I can use the Airport Utility software to confirm what the basestation IP and MAC addresses are (note MAC address = Airport ID in Airport Utility). I found the basestation IP=10.0.1.1 and the MAC=0:11:24:07:d7:f
To create a permanent ARP table entry for my airport basestation, I opened up a terminal window, and did the following -
1) login to my administrator account
2) type in the following command sudo arp -s 10.0.1.1 0:11:24:7:d7:f
3) type in my administrator password to authorise the change
4) type in (to confirm the changes have been made) arp -a
5) logout of my administrator account (from the terminal)
Ever since I did this, my MBP wireless performance has been flawless.
Note, if you shutdown or restart your computer, the arp entry disappears. This is ok for me as I hardly ever power down my MBP. As insurance I have added an account startup item to remind me to do the arp table entry.
This workaround is great for me because I don't have a need to use multiple wireless networks. It might not be practical for people who roam around onto different networks.
Give it a go and see if it works for you.
Message was edited by: michael louey

OK, after some further experimenting, I changed the multicast rate on my airport express. It was set at 6Mbps, and I changed it to 2Mbps.
I have read that the default multicast rate for previous 802.11g versions of Airport basestations is actually 2mbps. Excellent results so far !! I have set up a terminal command to continuously ping my airport router address every 15 sec, and there have been virtually no dropped packets so far over many hours.
ping -i 15 10.0.1.1
Interestingly, in Apple's Airport Admin software in my MBP there is no option to set the rate at less than 6Mbps (!!!!), so I had to use the Windows XP version of Airport admin software to make this change using a windows machine. Using the XP software you can set the muticast rate as low as 1Mbps.
If you are using Apples airport admin software (Tiger and Leopard) and you commit any sort of change in settings, the multicast rate will be re-set at a minimum of 6Mbps. My understanding of the multicast rate is that setting it too high is similar to shrinking the coverage area of the basestation, and limiting access only to clients who can transmit at the required multicast rate.
So my new theory is that the dropouts are caused by the MBP dropping off the airport due to not being able to achieve the set multicast rate. (this could be due to factors such as low signal strength, excessive interference or noise).
If you are using Apples more recent Airport admin software, you are having a minimum 6mbps muticast rate set, and this might be too high for your particular environment.
Just a theory.
(oh yeah, I enabled interference robustness on the MBP and the basestation just for good measure)

How can i hook up my airport to my play station 3?

how can i hook up my airport to my play station 3?

Sorry, there are two versions of the 802.11n AirPort Express. The older version has a single Ethernet port; the newer one has two. Which do you have? Is your goal to connect the PS3 to the Express by wire or wireless?
Regardless of model, if you plan on connecting the PS3 by wireless, then please check out the following PS3 Support article for details on how to do so.

Are there any compatibility issues with Sonos and Airport extreme??

are there any compatibility issues with Sonos and Airport extreme??

Sonos uses its own priopietory wireless protocol SonosNet to distribute audio data among all its products, thus it should not affect other network devices which use standard WiFi 802.11a/b/g/n protocol at all though they may share the same radio channel for wirless signaling.
On my dual-band (5 GHz / 2.4 GHz) Airport Extreme staion, I select the option "802.11n Only (5GHz) - 802.11n (2.4GHz)" and turn on "Use wide channels" in Wireless configuration in order to use only 802.11n protocol and more radio channels to achieve maximum wireless bandwidth of 400 Mbps. This bandwidth is necessary for quick Time Machine backup to NAS connected to the Airport Extreme station through Ethernet cable. So my iMac and MacBook Pro always connected to the Airport Extreme through 5 GHz radio channel with 802.11n protocol whereas my iPhone 4S always connected through 2.4 GHz radio channel with the same protocol.
In my living room Sonos ZP-90 (same as new CONNECT model) zone player is connected to Airport Extreme directly through Ethernet cable (recommended by Sonos) and Sonos S5 (same as new PLAY:5 model) zone player in bedroom is connected wirelessly through SonosNet protocol to the ZP-90 zone player in living room.
These devices are in operation simutaneouly most of the time. Music is playing through the Sonos ZP90/S5 zone players througout the day, I am streaming viedo through Internet (fibre broadband 25 Mbps) on my MacBook Pro in bedroom or iMac in living room or reading news on my iPhone. So far so good and have no encounter any interference problem for about three years. Further more bandwidth for 802.11n protocol does not seem to be affected at all.
In fact with a low power Fujitsu USB drive (2.5" / 500 GB, designed for notebook) plug into USB port of Airport Extreme, it can be used as NAS drive for Sonos music distribution system without any problem. Just transfer all files from Music folder in my home directory on iMac into this NAS drive and set it up as music source in "Manage > Music Library Settings" in Sonos Controller for Mac application will do. Though the same drive can be served as Time Machine's backup disk as well, an independent full-fledged NAS drive for Sonos and Time Machine backup is better long-term solution for reliability and performance. With the NAS configured as sole music source, you do not need to keep any computer powered on all the time in order to play music through the Sonos system.

So my airport extreme recently had some nat/dns issue and in the airport utility displayed a warning about it and to correct it. I wasn't sure what to do so i pressed the resolve icon and now my guest network is not working.

So my airport extreme recently had some nat/dns issue and in the airport utility displayed a warning about it and to correct it. I wasn't sure what to do so i pressed the resolve icon and now my guest network is not working.

Anytime you change networking hardware, it is always a good idea to perform a complete power recycle of your networking components.
I would recommend that you do the following as a minimum:
Power-down the modem, AirPort base station, and computer(s).
Disconnect the AirPort base station from the Internet broadband modem.
While all of the devices are powered-down, perform a "factory default" reset on the base station. This will get it back to its "out-of-the-box" configuration and make setting it up much easier, especially if you use the "Assist me" process within the AirPort Utility. (ref: Resetting an AirPort Base Station or Time Capsule)
After the base station resets, go ahead and power it back down.
Reconnect the AirPort base station to the Internet broadband modem. For the Extreme and Time Capsule, be sure to connect the cable to the base station's WAN (circle-of-dots) port.
Power-up the modem; wait at least 10-15 minutes to allow it adequate time to initialize.
Power-up the AirPort base station; wait at least 5-10 minutes. Note: The AirPort's status light may continue to flash amber after it has intialized. That is because, there may be some additional configuration items necessary, like setting up wireless security, before the overall setup is completed to get a green status.
Power-up your computer(s).
In this basic configuration, the AirPort base station will broadcast an unsecured wireless network with a Network Name (SSID) of Apple Network NNNNNN. Network clients, connected to the base station either by wire or wireless, should now be able to access the Internet through the ISP's modem. Once Internet connectivity has been verified, you can use the AirPort Utility to configure the base station for wireless security and any other desired options. Please post back your results.

Extending g wireless from Time Capsule using Airport Express...

Hi,
My Time Machine is working well and I have two old Airport Express units that I'd like to use as wireless extenders.
The Airport Expresses are the older type (i.e. only do 'g' wireless) and, according to the AirPort utility, they can't see the Time Capsule. My iPhone can connect OK so the 'g' network must be working.
Am I doing something wrong? Can I use my Airport Expresses to do this?
Thanks!

Thanks for the info. Your iPhone is connecting to the Time Capsule, not either of the AirPort Express devices.
In order to configure the AirPort Express devices to extend the wireless network, your Time Capsule Wireless Mode would need to be set to "Participate in a WDS network". You probably did not see this choice because it is "hidden". Hold down the "option" key on your computer while you click on the selection box to see if it appears.
I'm not necessarily suggesting that you try the WDS setup. It's an older technology that places a heavy bandwidth penalty on your wireless network in return for greater wireless coverage. The first Airport Express that you configure will cut the bandwidth of your network in half. The second will cut the bandwidth in half again. In other words, you are down to 50% of the original bandwidth with the first Express and down to only 25% with the second.
If you are getting acceptable wireless performance with the Time Capsule now, I would be tempted to leave well enough alone until you could add an AirPort Express "n" version, which would allow you to use the "extend a wireless network" setting. This is a much better performing arrangement and much easier to configure.
The WDS configuration is quite complex and frankly difficult for many users. To get an idea of the process, read over pages 42-44 in the Designing AirPort Networks Guide.
If you want to try this anyway, you will need reconfigure your Time Capsule and both Express devices to work in the WDS setup.

DNS Server Issues with Comcast and Airport Extreme wifi routers

I am having significant challenges with 3 Airport Extreme (latest gen) wifi routers and my Comcast Xfinitity service. It once worked just fine, but now I continually get the blinking amber lights stating "No DNS servers" for each of the Airport Extreme (AE) routers. My configuration is:
Coax cable -> Comcast Xfinity cable modem -> ethernet to 16-port gigabit ethernet switch ->->-> ethernet to 3 Airport Extremes around the house direct connected with switch
I have many wifi devices throughout the house (iPads, MacBooks, home automation devices) as well as direct-connected devices via ethernet (one PC connected to AE router).
Each Airport Extreme router is set with these settings in the Airport Utility app:
Internet tab= Connect using: DHCP
Wireless tab= Network mode: Create a wireless network
Network tab= Router mode: Off (Bridge Mode)
I have attempted to put the Xfinity cable modem in bridge mode, and use the Airport Extreme to serve up the IP addresses, but still lost internet connectivity.
I have also attempted to set the Network tab=> Router Mode to "DHCP and NAT" but get "Double NAT" error issues as well.
I have tried using the Comcast DNS server addresses (75.75.75.75;75.75.76.76) setting on the Internet tab for the routers and do end up getting a green light, but NO internet connectivity.
Lastly, I have tried using the Google DNS servers (8.8.8.8;8.8.4.4) setting on the Internet tab the routers giving me the No DNS servers amber light error and again, no Internet connectivity for either wifi-connected or even ethernet connected (directly to Airport Extreme router) devices (like my PC) despite getting a green light on the router.
Any this point, it really seems that these AE routers are NOT compatible with the Xfinity cable modem or service… (and yes, I've tried power-cycling and restarting the modem, and then the AE routers, MANY times to little avail).
Should I move one of these Airport Extreme wifi routers to before the switch, and have the other 2 in Bridge mode after the switch? Do I need to setup a specific range of DHCP reservation addresses for each different AE router?
Appreciate any insight anyone can share with this aggravating DNS server issue between Comcast & multiple Airport Extreme wifi routers.

I do not see anything wrong with your basic setup.. the issue is indeed the WAN ports of the AE.. AC version are having problems with some network equipment.
You have listed a stack of things you have tried.. but I want you to move the ethernet patch cable you use on each AE to its LAN port instead of WAN.
Restart the airport when you do that.. and then see if it becomes stable.
In bridge mode the airport moves the WAN port to LAN.. but the WAN port setup itself seems more problematic than the LAN ports.
There are other methods we can try if this does not work.. but in the end.. I would be tempted to take the whole lot back to apple.. they need to start making equipment that works with standard modems and switches.
BTW what brand is the 16 port switch?? Does it happen to be managed (smart type)?

When I hook up my airport express I loose internet, but it shows I'm connected and my printer is connected. It does not work though!!!

I set up my airport express and it shows it is properly set up, green light and all... However, it shuts off my internet and does not print through the printer it shoes hooked up. Bummer!!! Help???
Kim

I had similar issues setting up my airport express this afternoon. Finally got it to work by unplugging my cable modem and the airport express at the same time. Then plugged in cable modem, once it was running, plugged in the airport express, and it finally started working.
Per Apple's poor documentation, I had already restarted them individually many times, but doing them together finally got mine working. I was getting very frustrated though.
Hope it works for you too.
Robert

THis Wireless Issue is a Head Scratcher

As some know, I bought 2 Macbooks in Dec '06 and was experiencing all sorts of wireless issues early on. Dropped connections, SLOW transfer speeds while networked to my Imac, etc.
At some point Netgear released new firmware for the 824, and all seemed right in the wireless world for at least 2 months.
No issues with OS updates or airport updates, it seemed.
Al of a sudden last week, I went back to the extremely slow speed when networked from the macbook (wireless) to the iMac G4 800 (wired) and nothing so far will fix it.
The wireless transfer happens in 500K packets and a 4 meg file takes 4 minutes to transfer. Yet if I plug in the ethernet cable to the macbook - it works as it should.
What I can't figure out is what happened to make this annoying issue return out of the blue.
I am also back to slow page loads via Safari and page hangs.
Of course I have rebooted the router -
I can't figure out why for at least 2 months everything worked perfectly after months of sub par wireless performance and then back to **** - with everything back to sub par except not dropping connection anymore.
Thoughts?

I think the first thing I'd check for is if some source of interference returned after a few months of absence. I have a 2.4 GHz cordless phone that will nuke my 2.4 GHz WiFi connections - but only sometimes - when the phone happens to pick a channel that coincides with my WiFi. It could well be that a phone in your neighbor's house gets on your channel, and if the the phone doesn't experience any trouble may sit on your WiFi channel for a long time. In my case, my Panasonic phone bothers the WiFi, but the WiFi never bothers the phone.
The other thing you might want to look for is how many IP packets are being discarded by your Mac's network interface. You can do that my opening a terminal window and doing "netstat -s | more" The -s option gets you a rather extensive list of Ethernet statistics. What you want to look for is anything related to retransmitted packets. If you are experiencing more than a 1% IP packet loss, Ethernet performance can degrade rather ungracefully. (Note, I'm talking about layer 3 and above IP packets). It isn't unusual for 15-20% frame loss at layer 2 in the WiFi connecdtion.
There are a lot of variables here, and it is difficult to give you an answer that would be a one-step magic pill. There could be several problems at once. The best test would be: does one computer have lousy web page load times over WiFi, but the other computer has quick web access.
If both computers are having problems loading web pages, then there is something wrong with the router and/or WiFi interference. If just one computer has poor performance, then you need to look at the software on that computer.
Best wishes for finding it.
Bill

No Wireless Issues - Post Your Router

There is a "Wireless Issues - Post Your Router" thread, so this one will take a look at all routers that do NOT have any issues at all with any model of MacBook Pro. Unfortunately I can't add to it personally since Airport won't connect to my Linksys WRT54G intermittently. I was looking at the DLink DI-634M, so if anyone has any experience with that one, please post that as well.

Linksys WRT54GX4... A great router that supports 4 Windows XP systems (3 desktops and 1 laptop) and 1 Macbook Pro. Since I've had my MBP, I've had no connectivity problems whatsoever...
MBP (2.0Ghz) Mac OS X (10.4.6) Also running WinXP Pro on MBP...
MBP (2.0Ghz) Mac OS X (10.4.6) Also running WinXP Pro on MBP...

I am trying to setup wireless using my old dome Airport ExtremeBase station. I had previously used it about 5 years ago when I had dial up but have now switche to DSL with Windstream. I can not get connecte as ABS keeps trying to dial up(the phone number)

I am trying to setup wireless using my old dome Airport Extreme Base station. I had previously used it about 5 years ago when I had dial up but have now switched to DSL with Windstream. I can not get connected as the ABS keeps trying to dial up(the old phone number). When I tried to change my network settings an annoying popup window says "your network settings have been changed by another application'. I have no idea what the message is all about and when I close this window it immediately pops up again and prevents me -as far as I can tell -from changing my Airport settings? I need advice on how to get this wireless setup done. Maybe a reset? or something else? I have the DSL phone line plugged into WIndsteam Seimens Speedstream 4200 modem and then the ethernet (yellow) wire from the WIndsteam Seimens Speedstream 4200 modem to the port on the dome that is a circle of dots.

1)Can you explain how using the AEBS as a bridge will work with the Seimens Speedstream4200?
As a bridge, the AEBS will basically become a wireless access point. This will allow the AEBS to provide a wireless network, but still allow the Speedstream to provide NAT & DHCP services for the wireless clients connected to the AEBS. If the AEBS was left as a router, you would have a double-NAT condition which isn't necessary bad in itself, but would create a second subnet. That would make it more difficult for clients connected to the AEBS to access clients connected to the Speedstream.
2) Is there a link that will guide me through the steps to set the AEBS as a bridge?
You can easily reconfigure the AEBS as a bridge using the AirPort Utility.
ref: AirPort Utility > Select the AEBS > Manual Setup > Internet > Internet Connection > Connection Sharing = Off (Bridge Mode)
3)Can I just connect the DSL phone line to the AEBS and eliminate the Speedstream4200?
Unfortunately no. The AEBS does not have a built-in DSL modem. You will still need the Speedstream to provide this function.

Wireless issues hooking up 3 airports as extenders

Similar Messages

Maybe you are looking for