Extending wireless network - allow wireless clients or not?

Hi,
sorry if this is a stupid question but I cannot find the answer on the internet.
I have a setup with 3 level house, 3 airport extremes, the one in the middle connected via ethernet to router and acting as DHCP server.
The other two are setup to 'extend network'
Question I have is should I check "allow wireless clients" or not because when I do it seems to make the main AP extreme a client of the other two as well. This seems strange to me. any help would be appreciated.

do you work in entertainment industry at all? I know a bob timmons...
That would not be me.
any ideas why my extension airport extremes see the main DHCP extreme as clients?
This is normal. The "main" base station is a client of the "extending" Airport....and the "extending" AirPort is a client of the "main" base station. You would not have any extension if they were not clients of each other. In simple terms, they are communicating with each other at all times.
also any idea of the actual range of the AP extremes?
They usually check out at about 45-50 meters or 150 feet or so....but range measurements are made in "free air" in a large space....like an airplane hangar......with no obstructions in the signal path. Most homes are laid out a bit differently.
I've seen installations where the signal would barely go through one wall to a computer that was no more than 10 feet away from the router. The wall was metal lathe and plaster, so in effect the very weak signal was being asked to power though metal. Not much signal was getting through.
In very general terms, a typical wall of sheetrock or wallboard and 2 x 4s will absorb on average 15-20% of the wireless signal. A ceilng will absorb much more because it is much thicker. In most homes, after 3 or 4 walls, or a ceiling and a wall, there won't be much signal left.
Now, if you have adobe walls or cement walls or ceilings, everything changes dramatically. You get the idea.
My home is about 2400 sq ft, single level, of typical construction. I use 3 AirPort Extremes....all connected by Ethernet....not wireless....to get full speed, fast coverage virtually everywhere. I use an AirPort Express to "extend"....using wireless only....if I want to take my laptop out on the patio.
Older iPhones can connect at maximum 54 Mbps if they are literally right on top of the router. Typically,they might be at 25-35 Mbps or so with a good signal in the next room. The 180 and 270 numbers signify that these connections are 5 GHz...probably a newer Mac laptop or iMac.
If you have a Mac laptop and don't mind a $3 investment to get a good utility, WiFi Explorer can reveal some very useful things about your network. Post back if you are interested and we will take this up on Thursday.

Similar Messages

Network Policy Server windows 7 non domain wireless clients could not connect (Event id 6273 reason code 265)

Hi,
We have successfully configured network policy server on windows server 2012 and all wireless clients could connect to our network except windows 7 and xp non domain clients.The clients that are successfully authenticated includes windows 8,mobile users
(andriod + iOS) domain as well as non domain clients.If we join windows 7 pc to the domain it successfully connects but non domain clients could not connect.We have large number of windows 7 users that have their own laptop machines and we dont want
each laptop to join the domain.
On server event 6273 generated with reason code 265 "The certificate chain was issued by an authority that is not trusted".Plz help how to resolve this issue.I have searched on the internet but no proper solution found.

Hi,
According to the error message, it seems that you used certificate-based authentication methods and the non-domain computers has no Trusted Root Certificate for the CA that enrolled the certificate for the NPS.
For more detailed information, please refer to the links below:
Certificates and NPS
Manage Trusted Root Certificates
Best regards,
Susie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

AP1200 as Root Bridge: Accept wireless clients or not?

Cisco's docs precisely contradict themselves on this topic. In some places they state clearly that configuring an AP1200 as a root bridge means it will NOT accept connections from normal wireless clients. In other places they state just as clearly that in root bridge mode an AP1200 WILL accept connections from both non-root bridges and normal wireless clients.
Which is correct?

Yes, I discovered that after setting up several units and running some experiments. At first all I saw were the options offered in the "express setup" area. The root-bridge choice there says nothing about wireless clients, and the help screen it invokes says it won't work. But on the radio interface config screen the option you mention is offered and ITS help screen notes wireless clients will be accepted (as its name implies).
The telnet interface offers all the options as well.
I can confirm that it does work: In root-bridge with wireless client mode the unit will accept associations from non-root bridges, other AP1230's in WGB mode, and even non-Cisco clients.
The testing continues... thanks!

"add wireless clients" functionality --not working

I'm hoping someone can help me figure out the Add Wireless Client functionality in the AirPort utility. I can't seem to get it to work, and even Apple support appears to be stumped.
I have tried using the "add wireless clients" functionality in the Base Station menu of Airport Utility. When the "Wireless Client Setup Assistant" window opens, there are two choices: PIN or First attempt. Neither option seems to work. In fact, if I try to enter a PIN, I am able to enter a series of numbers, but the continue button does not become enabled.
Is anyone able to get this to work? I called Apple support and they were supposed to get back to me but they as of yet haven't offered a solution.
I have an airport extreme 802.11n and express configured in a WDS. Everything else is working perfectly.

James,
This topic has been previously discussed - the URL to one such thread which may assist you is http://discussions.apple.com/thread.jspa?threadID=855971
Regards,
Chris

Flexconnect AP(Local Switching) Wireless clients are not able communicate eachother

Hi,
Scenario : We are deployed the WLC in Corparate Office and Access Points are placed in Branch Office with FlexConnect Local Switching mode.
In this case, I am not able to Ping the Wireless clients eachother . Peer to Peer Block Option also Disabled.
Some time Wireless clients Ping eachother & some times not. Both Wireless clients are associated with Same AP & Same WLAN SSID.
Please help me urgent ..
Devices :
1)WLC 2500 series , Software 7.2
2)Cisco 1400 series APs
3)CISCO ACS server for AAA authentication
Regards,
Shanmugam Nachimuthu

Hi Shanmugam,
Please apply following steps to configure P2P setting for WLAN:
Step 1 Choose WLANs to open the WLANs page.
Step 2 Click the ID number of the WLAN for which you want to configure peer-to-peer blocking.
Step 3 Choose the Advanced tab to open the WLANs > Edit (Advanced) page.
Step 4 Choose one of the following options from the P2P Blocking drop-down list:
• Disabled — Disables peer-to-peer blocking and bridges traffic locally within the controller whenever possible. This is the default value.
NOTE: Traffic is never bridged across VLANs in the controller.
• Drop—Causes the controller to discard the packets.
• Forward - Upstream — causes the packets to be forwarded on the upstream VLAN. The device above the controller decides what action to take regarding the packets.
NOTE: To enable peer-to-peer blocking on a WLAN configured for FlexConnect local switching, select Drop from the P2P Blocking drop-down list and select the FlexConnect Local Switching check box.
Step 5 Click Apply to commit your changes.
Step 6 Click Save Configuration to save your changes.
Thanks,
Prashant Gondaliya

Why do some devices show up as wireless clients and not DHCP clients

When looking at the 'Logs and Statistics' section it shows me the MAC addresses of 3 wireless devices I have on my W/LAN (Macbook and 2 wireless PVR's) in the 'wireless clients' section but no info on the 2 wireless PVR's in the DHCP clients section. Only the Macbook appears there with its ip address shown. Can anyone tell me how to find out the ip addresses of these 2 other devices. I tried connecting one of the PVR's via a cat 5 but that one still doesn't show up in the DHCP clients section.

Esterhazyinoz wrote:
Can anyone tell me how to find out the ip addresses of these 2 other devices. I tried connecting one of the PVR's via a cat 5 but that one still doesn't show up in the DHCP clients section.
Try scanning with WakeOnLan to get a list of all devices and their IP addresses. If the devices got fixed IP addresses at the factory, they won't show up under DHCP.

New Wireless clients certificate not verified

Whenever a new clients login using SSID Green,using cisco WLC 4404, there is a prompt saying certificate is not valid. No doubt, clients can connect once they accept the certificate. Is there anyway I can remove this prompt? We have ACS doing authentication.The certificate is signed by authorized bodies? Please advice

I have indeed.
Pushing the profile can happen a few ways. If you use ISE you can push a profile in auto enrollment. Whereby you create the wireless profile (SSID, Security, Add Cert). This is delivered to the user automatically during enrollment.
Another way to make profiles and manually push is with the Apple Configurator.
https://itunes.apple.com/us/app/apple-configurator/id434433123?mt=12
You can also use a tool like Jamf for MACs to make and push profiles.
Hope this helps ..
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."
"Im like bacon, I make your wireless better"

How to "close" AE N Extended wireless network

Hi,
I have two AE N routers.
The first with a wireless mode of 'Create a wireless network' where I have selected "create a closed network" to keep my network name hidden. If just this router is on, when I scan for networks on my MBP, I can't find my network, which is what I expect. I can join the network O.K. after specifying it's name.
On the second router, I have set a wireless mode of 'Extend a wireless network' on the wireless network options, there is no 'create a closed network' checkbox. If this router is on, it does indeed extend my network, but if I run a scan on my MBP, I find that the network name is advertised.
Is this a personal thing? If so what have I done wrong?
I'm extending the network, as I want to run the N network in the 5Ghz band, as I have a bridge to a G network where I have a different named closed network running in WDS mode on 2.4Ghz.
Cheers ... Gwaant.
Mac OS X (10.4.8)

Sorry I'm also a Mac guy but if you read through my first post it might help you to find this out via Airport Utility as it should work on windows too. At first I made the mistake of Joining a network with my Express instead of Extending a network and the clients list will appear different then how I described it above. Seems like the most important things are to make sure your Extreme is set to Create a network and you must check the box that says Allow this network to be extended. In your Express select Extend a network and actually the router did the rest on my end...
Also, it might help if you try the equivalent of iStumber on Windows to see your networks. Although I only have one network name in iStumber it shows me that I have 3 networks so 2 are from my Extreme and 1 from my Express.
And finally and this might do it, you can go back to the Client list in Airport Utility to see which station you are connected to. That's what I was doing before Bob's easier solution which unfortunately doesn't seem to help you at the moment...
Hope this helps a bit as I just went though this. I'm just entry-level here Bob is the true expert and is always helpful! :-)
rc

Extending a network with Time Capsule and AirPort Extreme (via Belkin powerline)

Hello -
I've seen many topics about extending wireless networks here, but none seems to resolve the issue I'm having. I currently have a setup where a DSL cable modem is connected to a Time Capsule and I need to extend this network to another room using an AirPort Extreme.
I live in a very old apartment in Brazil and the walls seem to block the signal from one room to another, hence the need to extend it. Since wireless signal is very weak between rooms, I bought a Belkin powerline AV500 so I could connect both Time Capsule and AirPort using the electrical power at home (just installing a regular Ethernet cable between rooms is not an option).
I started with the basics: configure the Time Capsule + DSL as a standalone network, and it works perfectly within it's range. Then I connected the Belking powerline, plugged a MacBook via Ethernet on the other end and still got very good results (actually better speed than expected). Used it for a while with streaming and other network intensive tasks to make sure it could sustain the connection.
Finally, pluggned the AirPort Extreme on the Belking powerline and this is where the problems started. AirPort Utility 6.3.1 only gives me the option of extending a network wirelessly - it doesn't seem to give me the option of extending it via Etherenet (roaming), which is not good in my case. Luckly I had a copy of AirPort Utility 5.6 which seems to do the job (or I thought so), but it's still not working well.
Although I managed to configure both with the same name, it doesn't seem reliable and some devices (the iPhone 5, for example) are unable to connect and end up with a self-asigned IP address. I'm almost sure I'm doing something wrong on the setup, as I've seen a similar setup working before, so if anyone out there has any clue of what can be done, it will be much appreciated.
Attached the screenshots of both Time Capsule and AirPort Extreme configurations.
Thanks a lot,
-TM
AirPort Exteme:
Time Capsule:

Hello JuliaApple. Welcome to the Apple Discussions!
You have several ways to configure both base stations for what you are trying to do.
The simplest would be to configure the Time Capsule (TC) to "join" (AirPort Utility > Manual Setup > Wireless tab > Wireless Mode = Join a wireless network) your existing 802.11n AirPort Extreme Base Station (AEBSn). In this type of configuration the TC would perform as any other wireless client and not perform as a router. It will; however, still allow for both backups and sharing USB devices attached to it.

Extending a network with 2x Airport Express

I tried searching and couldn't find any discussions which answered my question. We have a home office which was just completed (an actual, separate structure, not just a room) and I need to connect it to the main house where our Internet connection comes in. What I'm trying to do is use an Airport Express (802.11n), which wirelessly connects to the main router, an Airport Extreme (802.11n, 2nd gen.). This Airport Express is then connected via Cat5e cable and a gigabit switch (it's a pretty long run) to another Airport Express (802.11n). This second Airport Express will then reconvert the connection to wireless and allow us to connect our devices in the office to the rest of the network and get access to the Internet.
Here's a crappy diagram I drew in Paint: http://i.imgur.com/5KrhX.png
When I first connected the second Airport Extreme in the office, I got a pop-up showing the new device in Airport Utility. However, no matter how I configure it, I cannot successfully get it to join the network properly. I've gone through the process multiple times, but am not having any luck. I've attempted to get it to "join my existing network" and then specify to connect via Ethernet and extend my network, and then tell it which device (the first Airport Extreme) it's connected to via Ethernet. Once I try to commit the changes, though, the device restarts and ends up with a blinking orange light, disappearing entirely from the list of devices in Airport Utility.
I've checked and the Airport Extreme is set up to allow devices to extend the network, and I've tried setting the first Airport Express to both "Join my wireless network" and "Extend my wireless network," though neither seems to make a difference.
Am I missing something, or trying something that won't work? Any ideas?
Thanks!

When I first connected the second Airport Extreme in the office, I got a pop-up showing the new device in Airport Utility. However, no matter how I configure it, I cannot successfully get it to join the network properly. I've gone through the process multiple times, but am not having any luck. I've attempted to get it to "join my existing network" and then specify to connect via Ethernet and extend my network, and then tell it which device (the first Airport Extreme) it's connected to via Ethernet.
You have two choices with AirPort Express #1:
Configure the AX as a wireless Ethernet bridge. Apple calls this configuration a ProxySTA. In this configuration, the AX would join the wireless network provided by the AirPort Extreme, and then, share this connection out it Ethernet port to the Ethernet switch.
Configure the AX to extend the wireless network of the AirPort Extreme. This would also enable the base station's Ethernet port.
Of the two, I would recommend the first option.
To configure the AX as a ProxySTA, you need just to make the following two setting changes:
Wireless Mode = Join a wireless network
Allow Ethernet clients (enabled)
Both of these settings are on the Wireless tab in the AirPort Utility.

How to verify that I extended my network properly?

Hi,
I finally purchased a new Airport Express to go with my 4th gen Airport Extreme as an extender. So I think I got things right...I have my Airport Extreme set to create a network and allow it to be extended and my new Airport Express set to extend a network. I also have my channels and mode on automatic so it all appears as one network. So I am getting much better range but it seems when I'm in an area where I'm connected to my new Express I have connection but there are some pauses when accessing webpages. It's not horrible but not quite as fast as before when I'm direct to my Extreme. Is that to be expected when extending? Also now in my Extreme the new Express shows as a client with these numbers:
signal -51 noise -82 rate -86 802.11 b/g/n
And in my Express now my Extreme shows as a client:
signal -41 noise -84 rate -144 Wireless
They are not so far apart but there is a wall in between. Anyways, just wanted to get some confirmation that I got things set up the best I can thanks!
rc

Sorry I'm also a Mac guy but if you read through my first post it might help you to find this out via Airport Utility as it should work on windows too. At first I made the mistake of Joining a network with my Express instead of Extending a network and the clients list will appear different then how I described it above. Seems like the most important things are to make sure your Extreme is set to Create a network and you must check the box that says Allow this network to be extended. In your Express select Extend a network and actually the router did the rest on my end...
Also, it might help if you try the equivalent of iStumber on Windows to see your networks. Although I only have one network name in iStumber it shows me that I have 3 networks so 2 are from my Extreme and 1 from my Express.
And finally and this might do it, you can go back to the Client list in Airport Utility to see which station you are connected to. That's what I was doing before Bob's easier solution which unfortunately doesn't seem to help you at the moment...
Hope this helps a bit as I just went though this. I'm just entry-level here Bob is the true expert and is always helpful! :-)
rc

WRT54G v6 client table not showing wired clients

I have a WRT54G v6 using the lastest firmware. Is there any 3rd party software that can display what clients I have on my network? The reason I'm asking is because my router will only show the wireless clients and not the ones connected on the wired side. Other than that everything works fine.

I have similar problem. DHCP client table shows only wireless laptops using dynamic ip address. All my wired destop (dynamic ip), and other static ip devices both wired or wireless do not show up in DHCP client table. Any idea? I have v8.

How can I not allow wireless access when extending a network?

I have two Airport Extremes, one extends the network of the other. How can I not allow wireless access on the remote Extreme when extending a network? I could do it with Airport Utility 5.6, but not with version 6 on Mavericks.

Correct. Use another Mac or even a PC running Airport Utility 5.x. Once you have the extending Extreme configured the way you want, Mavericks will not change the setting on the extending Extreme.

Bridge does not work for wireless clients - connecting to existing network.

Hi - I really hope somebody can help out here, after hours of trial & error, I have finally given up
I need to connect my Airport Extreme Base Station to my existing network. I have a linksys router (192.168.15.1) connected to my modem and this linksys router acts as DHCP server too.
I suppose I have to use "bridge mode" for that to work. But should the linksys be connected to the AEBS using the AEBS's WAN or LAN port?
If I use "bridge mode", then wired computers to the AEBS works fine - getting an IP from the linksys etc. BUT, the wireless clients will have a self-assigned IP and not get through to the internet. It's like the AEBS will not allow wireless clients to "get through" unless AEBS itself is handing out IP addresses.
Page 36 of this manual ( http://manuals.info.apple.com/en/DesigningAirPort_Networks10.5-Windows.pdf ) shows the setup I want. But in the picture, it says "Ethernet WAN port" but the text says: "The Apple wireless device (in this example, a Time Capsule) uses your Ethernet network to communicate with the Internet through the Ethernet LAN port ( <--> )." I don't know which one to use, WAN or LAN - they show WAN but say LAN?
When I set it up as "share an IP address", the AEBS status tells me "double nat" and to change from "shared IP" to "bridge mode". I do that, and everything seems fine - for the wired clients. Now the wireless clients cannot connect, Airport on the MacBook Pro just say "Connection failed" and the MacBook says "Invalid password" (translated from danish), even though I set the Airport Utlity to save the password in keyring, so it should be correct... If I disable wireless encryption, the wireless clients will connect but get a self-assigned IP, and therefor not work (cannot get online)...
It seems the only way I can get wireless to work, is if I set AEBS up as DHCP, but then it won't be on the "same network" as the linksys (192.168.15.1), but rather on 10.0.x.x as I select. If I select 192.168.x.x within AEBS, I'm also getting some error messages, conflict/subnet thing.
Anyway - I really hope somebody knows how to get wireless clients to get an IP address from existing ethernet when connected to the AEBS.
Thanks!!

I've given up and had to go back to running "Double NAT" which also reports as a "problem" within the AEBS, but I just "ignore" it so the light will always be green.
It still ***** though, as "Double NAT" is also a reason for "Back to my Mac" not working properly, but how the ** am I supposed to avoid Double NAT when the wireless will not work in bridged mode?!

How can I set a second Airport Extreme to not allow wireless clients?

I have two Airport Extremes. One is the main, and one is a remote unit used to extend my wireless network. I only want the remote Extreme to be able to use the LAN ports via ethernet to provide connectivity to my home theater gear. I don't want it to allow wireless clients, even though the two Extremes are wirelessly linked. Is this possible? I know it is on the Express, and I'd like to do that here. Thanks.

A simple solution might be.......
Use AirPort Utility 5.6 or earlier and click the Manual Setup option on the extending Extreme.
Click the Wireless tab below the row of icons
Wireless Mode should be set to "Extend a wireless network"
Remove the check mark next to "Allow wireless clients"

Extending wireless network - allow wireless clients or not?

Similar Messages

Maybe you are looking for