WDS and Roaming??

I have read other posts on this topic, but still cannot seem to make full sense of the issue. Here is my situation:
I have read through this thread...thanks to all. I have a similar situation, but have not yet purchased or attempted to implement, but have a slightly different network topology in mind. I would like to know before I go and drop the cash if I am on target. Here goes:
Internet
|
_DSL Modem_
|
AX3----------(Roaming/Ethernet)------AX1----------(Roaming/Ethernet)-------AX2
WDS main
AX4
WDS Remote/no wireless
Imac (ethernet)
Three AXs in attic of large house connected via ethernet, set to dual mode. AX1 is connected to DSL Modem/Internet. AX3 is connected and bridged (roaming) to AX1 and AX2 in attic, but also set as the WDS main. AX4 is on the first floor, directly (but two floors lower) from AX3 and will be configured an a WDS Remote with an iMac (gen 2) directly connected via ethernet.
Is the a sensible solution (wiring to first floor in a 1925 plaster walled house is a headache to say the least).
What I am trying to accomplish is using a wireless connection between a third floor attic space, and a first floor non-wireless machine, while still providing good wireless coverage throughout the house for wireless devices (apple TV-XP laptop etc).
Thoughts from those who know way more than I??

Duane,
Thanks for the feedback. I am worried about the density of the walls 12-18inch thick and am pretty sure filled with old lead paint in the undercoats. I have been so disappointed with the coverage areas I have seen in older houses with wireless, I thought some overkill might be necessary. But I may have over done it a bit.
I have determined a slightly different configuration after fishing some walls today, and am planning on installing the DSL in the basement (instead of the attic). This way I can:
1: attach an airport extreme under the house (centrally located) attached to the DSL
2: wire from under the house to 1st floor location with an ethernet link to the iMac
3: make an ethernet run from the basement to attic (2 floors away) thru a chase I found
I will try using just two AXs in the attic and see what the coverage is. What is the best tool for determining overlap of wireless signals. This might help in planning the network. I bought an AE gigabit today, in hopes that I could determine rage etc. in the house.
Again,
Thanks for the input.

Similar Messages

  • WDS and Roaming with 1130AG APs

    Hi there,
    I was wondering if someone could provide me with some insight into a configuration scenario i'm facing:
    Our office is situated in an old building and as such , wireless range is an issue as the walls are very thick and we have a mixture of clients from Laptops to android devices to iPhones that require access.
    we have 2 goals (first 2 are more important)
    1. to be able to roam anywhere in the building and pickup the wireless (fast roaming isn't really that necessary as voice isn't utilised)
    2. to have only 1 SSID for corporate access - Corp VLAN
    3. to have an SSID for guests to access - Guest VLAN
    The VLANs aren't an issue, i have an 1130AG setup which already has 2 SSIDs which does what i need.
    My main concern is around roaming, and i've read a lot about WDS, but this needs an external radius server, i've seen the articles that describe how to set up an AP as WDS and then add Infrastructure APs
    I've also seen that you can simply configure each AP exactly the same, but with different channells.
    I have 4 1130AGs at my disposal.
    What would you guys suggest is my best solution?
    Any help would be gratefully received.

    To get the best roaming, you need to make sure you have enough coverage. That usually means a good site survey was performed to specify how many access points and the locations of the access point. Without this piece, there is no guarantee of roaming.
    As far as WDS, you can setup an autonomous ap as a WDS server that is either dedicated as a WDS or is a WDS server and also serves clients.
    Sent from Cisco Technical Support iPhone App

  • WAP2000 fails WDS and roaming

    Hi,
    I'm wondering if anyone on this forum has successfully used WAP2000 access points.
    I'm particularly disappointed with these device:
    Hardware Version:
    1.0
    Software Version:
    2.0.0.5
    I set two of them up with exactly the same wifi security settings, same channel and WDS, one of which is a repeater (MAC addresses correctly set).
    Whenever I turn the repeater station on, the wireless supplicant not only doesn't extend it's coverage but if it's within the AP's outer range then it LOSES its connection with the AP. It's as if the wrieless repeater "jammed" the connection. I tried just about every possible setup and came to the conclusion that WDS does not work with my WAP2000 devices.
    I don't even "require" WDS to work if at least a decent roaming could be done. So I setup 2 WAP2000 as 2 APs with exactly the same wifi security settings and different, non-overlapping channels (same SSID). Roaming *should* be fairly quick but it lasts between 30 and 50 seconds!
    I replaced both WAP2000 APs with older WAP54G APs (same settings) and roaming is "fast" (less than 3 seconds!).
    So on one hand I'm demonstrating that roaming does NOT depend ONLY on the client side and that APs can be the culprit.
    On the other hand, I'm also showing how bad the WAP2000 product is (it's more expensive than the WAP54G but is completely unreliable).
    No wonder there are so few references on the web to the WAP2000 device.
    "Cisco" isn't as good as it sounds (I know it's "small business" but it's still Cisco).
    If someone here has had a similar experience and has found a solution, please let me know.
    Otherwise, I'm definitely not going to value the "Cisco/Linksys" brand as well as I did in the past.
    Thanks,
    Vieri

    To get the best roaming, you need to make sure you have enough coverage. That usually means a good site survey was performed to specify how many access points and the locations of the access point. Without this piece, there is no guarantee of roaming.
    As far as WDS, you can setup an autonomous ap as a WDS server that is either dedicated as a WDS or is a WDS server and also serves clients.
    Sent from Cisco Technical Support iPhone App

  • WDS AND WLSE

    Hi all , one we have set up the wds, what would happen if my wlse device broke? would this take down my wds service ?

    Sorry I forgot to answer this.
    As I mentioned, WLSE is just monitoring.
    Only If WLSE is being used as Radius server, then the NEW authentications might fail.
    "Might", because remember that WDS will try to cache the credentials, for example, for roaming.
    But sometimes it cache it for a long time. And additionally the current authenticated users will still be associated and authenticated. So only if a  new user trys to associate and authenticate, you will notice that the authentication is not working.
    Now, the other possibility is that you are using a backup WDS and or backup radius server. So everything will keep working as expected.

  • How to improve client handover and roaming between AP's

    Improving client Handover and roaming between APs
    There are a few standards and methodologies available to use to improve handover of clients between APs. Most are focused on VOIP technologies, but it must always be remembered that we cannot control the client Handover (especially with legacy clients) we can only encourage them. Some Standards and methods work well for some environments and some do not - test the recommendations extensively before implementing in a live Production environment. It must also be noted that all settings take effect immediately once applied, however from a client perspective it might need to re-associate for the changes to take effect client side.
    As with everything else in IT, if a perfect method/solution existed there would only be one - try them all and keep the best.
    The Standards and Definitions
    802.11k
    IEEE 802.11k allows a device to quickly identify nearby APs that are available for roaming. When the signal strength of the current AP weakens and the device needs to roam to a new AP, it will already know the best candidate AP with which to connect to.
    802.11r
    IEEE 802.11r specifies fast Basic Service Set (BSS) transitions between access points by redefining the security key negotiation protocol, allowing both the negotiation and requests for wireless resources to occur in parallel.
    When a device roams from one AP to another on the same network, 802.11r streamlines the authentication process. BSS allows a devices to associate with APs more quickly. Coupled with 802.11k's ability to quickly identify the target AP, BSS's faster association method may enhance application performance.
    Handoff Assist
    The AP monitors the RSSI for every associated client. If the RSSI for a specific client falls below "low-rssi-threshold" and continues to fall for the "rssi-falloff-wait-time", then the AP will send a de-auth to the client. 
    The de-auth is meant to kick the client away from the current AP and get it to re-authenticate to a nearby AP. This will have the effect of helping a client handover between 2 APs.
    BUT (Big But), if the client gets de-authed and takes a while to re-authenticate (if it even does re-authenticate automatically after a de-auth), then this will have the effect of destroying communication instead of helping it -- mostly found with legacy clients. 
    Remove Lower Transmit Rates
    Removing lower transmit rates is a way to promote better roaming, BUT not all clients respond well, or even respond to it. 
    The practice is that the basic rates are a subset of the transmit rates. If you only want to allow speeds 9 and up, you would select only the transmit rates of 9 and up, and the basic rates of 9 and 11. If a legacy client expects the rates of 1 and 2 it will not connect.
    Local Probe Threshold
    Local probe Threshold prevents a client from connecting to an AP with a too low a signal - helps more with initial connection than roaming.
    The local probe threshold parameter is not supposed to force clients to roam as soon as they pass near an access point with a good signal, but rather to NOT hold on to an access point with a weak signal (avoiding sticky clients).
    PMK Caching
    Defined by 802.11i and is a technique available for authentication between a single AP and a station. If a station has authenticated to an AP, roams away from that AP, and comes back, it does not need to perform a full authentication exchange. Only the 802.11i 4-way handshake is performed to establish transient encryption keys.
    Opportunistic Key Caching (OKC)
    Is a similar technique to PMK, but not defined by 802.11i, for authentication between multiple APs in a network where those APs are under common administrative control. An Aruba deployment with multiple APs under the control of a single controller is one such example. Using OKC, a station roaming to any AP in the network will not have to complete a full authentication exchange, but will instead just perform the 4-way handshake to establish transient encryption keys
    Implementation and Configuration
    802.11k
    802.11k is configured in your VAP profile. Tick the option to “Advertise 802.11k”. There after set the Handover Trigger Feature Settings.
    Tick the “Enable Handover Trigger feature” and then set RSSI threshold by specifying the -dBm level at what the hand over trigger should be sent to the client
    802.11r
    802.11r is configured under SSID of your VAP profile. Tick the option to “Advertise 802.11r”
    HandofF Assist
    Station Handoff Assist is enabled in RF Optimization under the RF Management section of AP configuration.
    Tick the “Station Handoff Assist” option to enable it, next set the Low RSSI Threshold – the threshold determines above what level no deauth gets sent
    Lower Transmit Rates
    Transmit rates can be adjusted in the Advanced tab of SSID under your VAP profile.
    Remember that the basic rates are a subset of the transmit rates. If you only want to allow speeds 9 and up, you would select only the transmit rates of 9 and up, and the basic rates of 9 and 11
    Local Probe threshold
    Local Probe threshold can be adjusted in the advanced tab of SSID under your VAP profile.
    Depending on the density of your APs consider values between 20 and 40 -- 40 being aggressive in an AP dense area.
    Deny Broadcast Probes
    Denying Broadcast Probes can cause problems with Roaming especially if the SSID is hidden – leave option disabled.

    Hi, thank you for the helpful guidance.  I have a basic question, if the device roam from one AP to another AP with the same SSID.  Is there a need of re-authentication given a) the network uses EAP based authentication; b) the network uses MAC address authentication.   If there is no need of EAP re-authentication, how the 802.11 keys are moved to the new AP.  Thank you very much if you could help me clarify my thought. 

  • WDS, DHCP and WSUS on same server, Virtuals find WDS and start up process, Physicals get PXE-X55 error.

    I have a Windows 2012 R2 server that has the WSUS, WDS and DHCP roles installed. I also have a SCVMM (Win2012R2) server on different machine and it has been connected to the WDS server
    Followed many different guides on the internet to configure the WDS server but if I have option 60 configured the virtual machines will find and do a PXE boot successfully, but the physical systems will fail with a E55 error.
    I take out option 60 and both fail.
    Did I miss a niggly bit some where?

    Have you tried this (from article):
    Custom-made Option 60 – String – PXEClient
    Predefined Option 66 – IP or Hostname of the WDS Server (in our case 10.150.150.1)
    Predefined Option 67 – boot\x86\wdsnbp.com
    and this in WDS properties:
    and
    Many people remark this as solution:
    WDSUTIL /Delete-AutoAddDevices /DeviceType:ApprovedDevices

  • WDS and authentication

    We have 1200 APs configured with mobility networks (mGRE tunnels terminated on a WLSM). The APs are pointed at the WLSM WDS and pass their authentication requests to the WLSM acting as the WDS using WLCCP. However, these APs also provide wireless access to the local wired networks. This can be configured, but it appears that all authentication requests go via the WDS (i.e. all locally configured RADIUS servers for local network authentication are ignored).
    The WLSM Deployment Guide suggests that it is possible to have "WDS" and "non-WDS" SSIDs coexist. The consequence is that the availability of the WDS (on the WLSM) becomes critical, even for APs which could authenticate local wireless users through RADIUS servers configured directly on the AP.

    WDS checks its local list for authentication . If the Mac address is not present it uses configured Radius server for authentication. Make sure Mac address is either in the Local list or Radius server. If you are using Radius server make sure Mac address is configured as user

  • WDS and MDT

    I setup my WDS and MDT Deployment and the image booms out at TFTP and never gets to the menu screen.

    Hi dektame,
    Some required information are needed for us to help you. A screen shoot would be appreciated.
    By the way, if you mean you stuck in TFTP step, you need check if imported right boot image to WDS.
    Regards
    D. Wu
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • WDS and Unattended queries/clarification (Server 2012)

    Hi Folks
    I am studying for my 70-411 exam and have a few points that I would like clarification on relating to unattended installations and WDS:
    1: When you create an unattend.xml for the 'Windows Deployment Services client’,  in SIM which image do you need to base this on? 
    Do you just use the install.wim from the server iso?
    2: Are both a WDSClientUnattend and a ClientUnattend mandatory for unattended to work? 
    For example if you only want to automate the image settings but not the settings pre-image selection (such as usename/password to connect to WDS) can you specify only a ClientUnattend?
    3: Can disk partitions be set in the ClientUnattend or do these have to be in the WDSClientUnattend file?
    Thanks in advance.

    1. The WDS Client itself is based on "boot.wim" from a preferably new OS. For instance if you plan to deploy Windows Server 2012R2 or Windows 8.1, you need to have a 6.3 version of the boot.wim, either from the 2012R2 server iso, or Windows 8.1
    iso (it doesn't actually matter). You can deploy e.g. windows 7 from the 6.3 boot.wim aswell, but not the other way around.
    2. The WDSClientUnattend is for the "WDS Client" part, that means you should specify settings here on "how you want to perform the installation", e.g. which edition of Windows to install (Server standard, or Server Enterprise...), to
    which DISK (and how to partition it), credentials to connect to WDS share (remoteinstall$ on WDS), and also what language and keyboard settings to use during setup. If you don't specify this, you can still specify an unattend.xml file for an install Image,
    that is settings relevant to a specific image only. So you can decide to do either of them, or both.
    3. This needs to be done in WDSClientUnattend, that is "1 - WinPE-phase". You can see this phase as the first phase Before first reboot, that is lang settings, partition settings, image selection, and then copying of files. Upon next reboot, and
    not Before is when you reach the next Phase, that is "4 - Specialize"

  • WAP321 - No WDS and Single Point Setup

    Hi folks
    I bought 3 WAP321s with the intention of creating a fairly wide network in a large building where I can't easily add wiring.  Access was to be via a captive portal where I would create logins for all of the users.  However since I have bought the devices I discover that it isn't possible to use both WDS and clusters at the same time.  I have connected 2 devices by WDS by duplicating settings by hand in both but I have some questions that maybe some folks can answer?
    1. Do I have to copy both the captive portal design and the username and logins to each of the 3 devices for this to work? (I think that I do now)
    2. In the manual under the WDS discussion there is talk of both point to point and point to multipoint setups.  It seems to imply that with point to multipoint then there is a single WAP handling the client associations.  In that case does only one WAP handle the logins by captive portal?  I am trying to avoid having to duplicate the logins on all devices. 
    3. How do you decide in WDS if you are point to point or point to multipoint?  Is it just the number of connections that you have on the WDS setup page?
    An alternative if I am desperate is to use RADIUS but I am trying to avoid that
    Just for reference I have already read the manual for the WAP321 several times as well as watching the video on WDS setup
    Thanks
    Richard

    Hi Richard, thank you for using our forum, my name is Luis I am part of the Small business Support community.
    1 and 2. It isn't necessary to copy the same captive portal configuration for all the equipment, you should just configure the central WAP and the rest will receive the Captive portal.
    3. In the point-to-multipoint bridge mode, one WAP device acts as the common link between multiple access points. In your case if you are connecting two WAPs to one that is a multipoint bridge.
    I hope you find this answer useful
    Greetings,
    Luis Arias.
    Cisco Network Support Engineer.

  • I was wondering if towers are still being built in dead areas and roaming areas.

    So, my iPad cannot roam in extended coverage and I was wondering if you guys are still building towers in dead areas with no service and roaming areas. It would be nice to access data service mostly everywhere, even in mountainous areas. So I was wondering if you guys are fixing the roaming and dead areas. I think every town in the United States needs coverage also in parks like the grand canyon, so I was wondering about that. Thanks!

        I can understand and appreciate your interest in the additional coverage areas. We are constantly looking to expand our coverage area. You can keep up to date with additional coverage or improvements here, http://bit.ly/xVecuo or here http://bit.ly/n5snpq
    YosefT_VZW
    Follow us on Twitter @VZWSupport

  • SCCM 2012 R2, DHCP and WDS and PXE same server

    hi
    I am using DHCP and PXE on same server and getting error PXE-E55: proxyDHCP did not reply to request on port 4011

    HI,
    To get WDS and DHCP to work on the same machine, you need to configure WDS to share the same server as DHCP, here is how it is done.
    You must have a functioning DHCP server with an active scope. WDS will utilize PXE which requires a DHCP server.
    Whether you plan to co-host WDS and DHCP on the same server or use two different servers you must configure WDS to listen on a specific port. DHCP and WDS both require port number 67. If you have co-hosted WDS and DHCP you can move DHCP or the PXE site role
    to a separate server or use the procedure below to configure the WDS server to listen on a different port.
    Modify the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE              
    Set the registry value to:
    UseDHCPPorts = 0              
    For the new configuration to take effect run the following command on the co-located DHCP and WDS server:
    WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes
    https://technet.microsoft.com/en-us/library/bb680753.aspx
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • PXE, WDS and DHCP Option 66 and 67 PXE-M0F: Exiting

    Hello,
    I have configured DHCP options 66 and 67 to point to my site server running WDS and SCCM 2012 R2 with a DP with PXE enabled. 
    My DHCP server is on 10.1.54.199 and my sccm server is on 10.1.184.60 whilst my client is on 10.1.141.245. I have set the options in DHCP to 10.1.184.60 and SMSBoot\x86\wdsnbp.com
    When i boot my client I get
    Client MAC:xxxx GUID:xxxxxClient IP: 10.1.141.245, MASK: 255.255.254.0, DHCP IP: 10.1.54.199Gateway IP: 10.1.140.1TFTP.PXE-M0F: Exiting Intel Boot Agent.
    Can anyone offer any help on where to begin troubleshooting this? Previously this has all worked but the server was recently moved to a new IP address and VLAN where IP helpers are not configured. This method worked a treat for us in 2007 but for whatever
    reason not in 2012?
    Any advice would be greatly appreciated.

    Hi Gerry, Yes When I added the second DP to the All DPs Distribution Point Group it then went and distributed some 70 or so packages, among these were the boot images. I just double checked and the second DP is listed in the content locations tab for both
    boot images.
    Hi Jason,
    Not yet but when i tried this earlier (16:00 ish where I am) the date modified time of the log had not changed (it reported sometime like 14:30). I will have a look in the log... It has indeed changed...
    It seems to be looping through a process of:
    Begin Validation of Certificate thumbprint...
    Completed Validation of Certificate thumbprint...
    PXE Client Certificate Valid...
    Purging Old Images 0...
    Purging Old Images 0...
    There are a few lines above from a few hours earlier (when i installed the second DP and enabled PXE) where it shows it adding files to install que, No errors though. Further up the log I can see errors...
    Initializing PXEPerfObject. SMSPXE 18/02/2014 14:21:18 3164 (0x0C5C)
    Failed to get logging settings for 'ccmperf' from Registry (80070002) SMSPXE 18/02/2014 14:21:18 3164 (0x0C5C)
    Could not load logging configuration for component ccmperf. Using default values. SMSPXE 18/02/2014 14:21:18 3164 (0x0C5C)
    Client is set to use HTTPS when available. The current state is 224. SMSPXE 18/02/2014 14:21:19 3164 (0x0C5C)
    CLibSMSMessageWinHttpTransport::Send: URL: primary-site-server.co.uk:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 18/02/2014 14:21:19 3164 (0x0C5C)
    RequestMPKeyInformation: Send() failed. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    Failed to get information for MP: http://primary-site-server.co.uk. 80004005. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    PXE Provider failed to initialize MP connection. 
    Unspecified error (Error: 80004005; Source: Windows) SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    CLibSMSMessageWinHttpTransport::Send: URL: primary-site-server.co.uk:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    RequestMPKeyInformation: Send() failed. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    Failed to get information for MP: http://primary-site-server.co.uk. 80004005. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    PXE::CPolicyProvider::InitializeMPConnection failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
    I am not sure if the above is relevant but it is the only stuff marked red in cmtrace in SMSPXE thats around the timeframe where I was testing it earlier today.
    Any suggestions?
    EDIT: I dont think I have imported the web server certificate on the second DP or configured IIS to use this cert for https, I am guessing that is what these error are all about? Not sure why this would effect PXE though especially as it should be getting the
    content from the first DP. I will crack on sorting this cert problem tomorrow and see if it fixes the issue I am having with PXE with no IP Helper.
    EDIT 2: I also changed the DHCP option 67 from SMSBoot\x86\wdsnbp.com to SMSBoot\\x86\\wdsnbp.com. It may have been the \\ in here that also helped solve my problem.

  • What series or type of Linksys Router that had WDS and Repeater ?

    Alo guys, i've been wondering about which type of linksys router had WDS and Reapeter. I need it to expand my wireless network at home.

    I already had WRT150N, but the problem is my WRE54G is broken and know i had to wait for my replacement, but when i search on the internet, i found there is an extra fitur on the router which is called WDS and repeater and maybe i think linksys router had one of these.

  • What is the difference between WDS and Extending a network?

    What is the difference between the two? Why choose one over the other?

    Both the WDS and "Extend a wireless network setting will add more coverage area to a wireless network.
    WDS must be used if any device on the network is an older "g" device. The downsides to WDS are that it drops the overall wireless speed down to "g" levels (even if there are other newer "n" routers on the network) and cuts the bandwidth capability of the network in half for each "remote" device that is added to the network. That's a really severe loss in performance.
    "Extend a wireless network" is a newer technology that can be used only if all of the routers on the network are newer "n" capable devices. It allows full "n" speeds and imposes only a small bandwidth penalty on the network. Obviously, this is the setup to use if your devices will support the technology.
    Message was edited by: Bob Timmons

Maybe you are looking for