WDS error?

anyone else having an issue to get an Airport express to extend their Airport Extreme Network?
I did have 3 airport expresses located through out the house 1 master. and then 2 others for speakers. I replaced the master one with the new airport extreme. I got them connected and extended ok. until I went to set up the WPA2 passwords. as soon as I set up one of the express's as an WDS extender (with the password) the extreme comes back with WDS error
but I can get the expresses to connect ok with the passwords as a wireless client
Any idea's people??" (APPLEGUY)
http://forums.macrumors.com/showthread.php?t=288640
This was posted on another forum, but it was written so well and the exact problem/issue I am having....

Make sure you read this article:
Changing network security for a WDS network
The point made in that article relevant to your problem is this one:
"If you have a WDS network set up to use either no security, or 40 or 128-bit WEP, and you decide to upgrade the network security settings to WPA Personal, you will need to reset all of the base stations on the network, and then set up the WDS network again. "

Similar Messages

Getting WDS Error

Hi, I've been having a problem with my wireless network the past couple of weeks. I have an AEBSn set up as a base station and an AEBSg and Airport Express set up as remote units in different parts of the house. This configuration worked great until about 2 weeks ago. Someone uplugged the Airport Express and after it was plugged back in I have been getting an amber flashing light indicating a WDS error on the AEBSn unit.
I look into Airport Utility and it sees all three units with the remote units coded green. At times, it seems to resolve itself and the status light goes green but after a few minutes it begins flashing amber again.
I'm getting a good signal throughout the house, it just is annoying to see the amber flashing light.
Thanks for any suggestions or hints.
Bob

There is no reason to suspect a "settings" problem here. My guess is that this error is being caused by an occasional drop in the wireless communication between the main and remote base stations.
For a start, you might try pulling power to all base stations, then plug the main base station into power and waiting for it to reboot, followed by both remote base stations. That might force the entire network to work on a different channel with a better connection than current.

AEBS/relay/remote flashes WDS Errors

I am trying to set up a remote connection from the office to the gym using 3 Airport Extreme Base Stations. I currently have all 3 in a room the main connected to the DSL modem, and the remote connected to the main via ethernet.
The problem is that the main keeps flashing WDS Errors, then goes back to a Normal status. The relay would flash, then the remote. I removed the relay, and the remote seems to keep it Normal status better even as the main changes to WDS Error - it shows an error it is just for a blink. WDS Error is "This Apple wireless device is set up as part of a WDS network but no other Apple wireless devices were found." When ever the main changes status it drops it wireless clients.
If I use the main in "Create wireless network" it seems to work fine.
Anyone know why this might be happening? Can I just click ignore it since the remote is Normal most of the time?
I have set up the network following Apples Designing AirPort networks guide available online http://manuals.info.apple.com/en/DesigningAirPort_Networks10.5-Windows.pdf . I have entered the airport id in the proper place and set the WDS Mode to the proper mode for each device.
I have tried checking and unchecking the use interference robustness (makes no difference). I have checked and unchecked "Allow this network to be extended" and found there to be no difference. All three are set at Participate in a WDS network.
I have tried every channel and there is no difference.
Should the Wireless Mode on the relay/remote be Extend a wireless network? Should allow this network to be extended be checked or unchecked?
Any more ideas will be appreciated. Time to enjoy the 4th!

I have set on AEBS in the hall about 100 feet from the first. I am going though 2 steel framed drywalls and one block&brick wall. Still have about 1650kbps using iNetwork test. The problem has been getting into the gym. I can get from the hall through a glass window, courtyard, steel covered wooded door and into the kitchen. But the wall between the kitchen and gym is double thick with steel rods. I changed the location of the remote from the kitchen to the storage room, which houses the water heaters. The signal goes through the courtyard and a brick&block wall. The reading was about 400kbps and I am able to get through the wooden doors into the gym area with one bar showing on my Macbook.
I guess I will have to try something different.

WDS error message

I am getting a WDS error message on my set up - saying station part of wds network but no other base stations found.
The network works fine so i could just ignore but i am interseted to understand more and the manual 'designing n network' does not help me
here is the set up: dsl modem>n base station>connected wirelessly to 3 aiport expresses (printer;itunes/hifi and ax in bedroom) and a g base station
The error message says set up N base station as a 'bridge' but if i do that the ax's and g base station don seem to connect. The raeson I am using a n base station in this is that i want to use a shared hard drive on the network
All thoughts gratefully received

Hi xhoffman,
This error can occur when you try to install Windows 7 or Windows Server 2008 R2 on a system if the following situation is true on your PC:
You are installing by using Windows 7 or Windows Server 2008 R2 RTM media.
Your system has an Intel storage controller that is configured to "RAID" mode in the BIOS. (This is a standard setting for many PC manufacturers).
The hard drive you are installing to an "Advanced Format" disk.
Please check your installation media and BIOS drive settings or download the appropriate drivers for your hard disk drive.
You could also check your setupact.log and setuperr.log for more failure details
https://technet.microsoft.com/en-us/library/hh825073.aspx?f=255&MSPPError=-2147217396
For more information or advanced methods
http://support.microsoft.com/en-us/kb/2466753
Regards
D. Wu

Configure WDS error - The Network path was not found

I'm trying to configure WDS on Server 2012 R2. The Server is a DC and hosting DHCP and DNS. When running through the wizard or via command line to configure WDS, I get a message saying "The network path was not found". The folder gets created,
however there is no content in the folder.
We are also getting the following event "An error occurred while trying to initialize provider from WDSMDMGR from C:\windows\system32\wdsmc.dll
Any ideas?
thanks.

Hi,
Since WDS is running on the same server with DHCP, did you set WDS not to listen to port 67 and configure DHCP option 60 PXEClient?
These settings can be done via WDS installation wizard.
Hope this helps.

WLSE 2.11, snmp and wds errors

Hello,
I try to use WLSE to manage our AP1131,1231 with different IOS version.. Some AP are in WDS domain with a WLSM, others in WDS with an AP configured to be wds master, and other are standalone without wds configured.
I have a lot of AP with error on WLSE, the most recurring ones are "Device was not reachable via SNMP" and "Inconsistent state found for query "interface.radio.basic"".
WLSE says that some device were not reachable by SNMP but snmp community is configured with a good access-list. Moreover, when I test snmp reachability from WLSE (admin>appliance>connectivity tools>SNMP Query Tool) it works fine. So I do not understand why I have this fault.
I do not understand the fault "Inconsistent state found for query "interface.radio.basic"", someone could help me perhaps ?
And the last question, some AP without wds configured have "Parent WDS for the Access Point" = 0.0.0.0.. I do not understand why..
If someone could help me for one of these troubles, it would be great
Thank You,
regards

All these faults are explained in detail at: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwparent/cw_1105/wlse/2_11/ts_gd/faults.htm
including the "Inconsistent state found for query...

DHCP WDS Error

Hi. Im having a problem where I get the error 'An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment'when booting from a standard WDS boot.wim image taken
from a Windows 7 DVD.
I am using Server 2008 R2 and am adding the drivers to the boot using WDS, but also have the problem if the drivers are injected beforehand using DISM.
When the error occurs I can shift + F10 and IPCONFIG and see it HAS picked up an internal IP from DHCP. Seems maybe it is timing out before it gets the IP?
As per some fixes I have read I enabled RSTP on my switches but that didnt help.
I have included the end of setupact.log to see if any of you have any ideas.Seems to be failing but as I say, the network IS initialized as I can see the internal IP assigned by DHCP when running IPCONFIG.
I dont suppose theres any way of increasing the timeout?
Thanks.
2011-04-11 17:26:31, Info       [0x0b0022] WDS    StartNetworking: Trying to start networking.
2011-04-11 17:26:31, Info                  WDS    Network service dhcp not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service lmhosts not running or could not be queried: 264e18 1 1
2011-04-11 17:26:31, Info                  WDS    Network service lanmanworkstation not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service bfe not running or could not be queried: 264e18 1 1
2011-04-11 17:26:31, Info                  WDS    Network service ikeext not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service mpssvc not running or could not be queried: 264e18 1 1
2011-04-11 17:27:24, Info                  WDS    Installing device pci\ven_14e4&dev_1691&subsys_04aa1028 X:\WINDOWS\INF\oem37.inf succeeded
2011-04-11 17:27:25, Info                  WDS    No computer name specified, generating a random name.
2011-04-11 17:27:25, Info                  WDS    Renaming computer to MININT-VN2P876.
2011-04-11 17:27:25, Info                  WDS    Acquired profiling mutex
2011-04-11 17:27:25, Info                  WDS    Service winmgmt disable: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Service winmgmt stop: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Service winmgmt enable: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Released profiling mutex
2011-04-11 17:27:25, Info                  WDS    Acquired profiling mutex
2011-04-11 17:27:25, Info                  WDS    Install MS_MSCLIENT: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_NETBIOS: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_SMB: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_TCPIP6: 0x0004a020
2011-04-11 17:27:26, Info                  WDS    Install MS_TCPIP: 0x0004a020
2011-04-11 17:27:26, Info                  WDS    Service dhcp start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service lmhosts start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service ikeext start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service mpssvc start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Released profiling mutex
2011-04-11 17:27:26, Info                  WDS    Spent 967ms installing network components
2011-04-11 17:27:28, Info                  WDS    Spent 2247ms installing network drivers
2011-04-11 17:27:38, Info                  WDS    QueryAdapterStatus: no operational adapters found.
2011-04-11 17:27:38, Info                  WDS    Spent 10140ms confirming network initialization; status 0x80004005
2011-04-11 17:27:38, Info                  WDS    WaitForNetworkToInitialize failed; ignoring error
2011-04-11 17:27:38, Info                  WDS    GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:
2011-04-11 17:27:38, Error      [0x0b003f] WDS    StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
2011-04-11 17:27:38, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server
on this network segment.]

Thanks for the reply. I have came across the post about removing setup.exe etc but thats a nasty hack and Id rather get the thing working properly.
For my own testing to prove I had added the drivers correctly I booted off a base boot.wim with no drivers injected. There was no IP when running IPCONFIG. End of setupact.log shows
2011-04-13 09:09:20, Info WDS Spent 936ms installing network components
2011-04-13 09:09:23, Info WDS Spent 2355ms installing network drivers
2011-04-13 09:09:23, Error [0x0b003e] WDS QueryAdapterStatus: no adapters found.[gle=0x000000cb]
2011-04-13 09:09:23, Info WDS Spent 0ms confirming network initialization; status 0x80004005
2011-04-13 09:09:23, Info WDS WaitForNetworkToInitialize failed; ignoring error
2011-04-13 09:09:23, Info WDS GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:
2011-04-13 09:09:23, Error [0x0b003f] WDS StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
2011-04-13 09:09:23, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while starting networking: a matching network card driver was not found in this image. Please have your Administrator add the network driver for this machine to the Windows PE image on the Windows Deployment Services server.]
Next, I injected the latest Broadcom drivers into another base boot.wim file. IPCONFIG shows an IP address. End of setupact.log shows
2011-04-13 09:17:38, Info WDS Spent 936ms installing network components
2011-04-13 09:17:40, Info WDS Spent 2309ms installing network drivers
2011-04-13 09:17:50, Info WDS QueryAdapterStatus: no operational adapters found.
2011-04-13 09:17:50, Info WDS Spent 10140ms confirming network initialization; status 0x80004005
2011-04-13 09:17:50, Info WDS WaitForNetworkToInitialize failed; ignoring error
2011-04-13 09:17:50, Info WDS GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:
2011-04-13 09:17:50, Error [0x0b003f] WDS StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
2011-04-13 09:17:50, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment.]
Windows IP Configuration
Host Name . . . . . . . . . . . . : minint-2eljtfg
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : correct.co.uk
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : correct.co.uk
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
Physical Address. . . . . . . . . : 78-2B-CB-93-11-F8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a098:117a:a1fd:a4b9%2(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.78(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, April 13, 2011 9:17:57 AM
Lease Expires . . . . . . . . . . : Thursday, April 21, 2011 9:17:57 AM
Default Gateway . . . . . . . . . : 10.0.0.66
DHCP Server . . . . . . . . . . . : 10.0.0.21
DHCPv6 IAID . . . . . . . . . . . : 41429963
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-37-93-19-78-2B-CB-93-99-F8
DNS Servers . . . . . . . . . . . : 10.0.0.21
10.0.0.6
NetBIOS over Tcpip. . . . . . . . : Enabled
See the difference? 'no adapters found' vs 'no operational adapters found'.
However this time I did notice that when I typed IPCONFIG straight away after the error message poped up it only showed an IPV6 address. Then when I tried 1 second later it had picked up the DHCP address.
Seems that the network card takes some time to initialize and the deployment setup is too impatient and falls over?

WDS Error Event ID : 722

WDS & DHCP configured in same server. I getting error in WDS log file.
An error occurred while trying to create the UDP endpoint for WDSTFTP provider on interface 10.146.8.5:69. This can happen if the network interface was disabled or changed, or some other application is already using the port. The provider will not
be able to receive requests on this interface.
Error Information: 0x2740
How to reslove it

Also, please review
https://technet.microsoft.com/en-us/library/hh397405.aspx and make sure all steps are taken for running DHCP and WDS on the same server.
Jeff

WDS error 1067 in SCCM

I need some troubleshooting steps for the below .
not WDS not getting connected error 1067 in SCCM
when pxe enabled wds getting disabled

Hi,
Please refer to the link below:
SC Configuration Manager 2012 R2 OS Deployment Error at Windows Deployment Services
http://www.microsofttranslator.com/bv.aspx?from=tr&to=en&a=http%3A%2F%2Fsocial.technet.microsoft.com%2Fwiki%2Fcontents%2Farticles%2F22949.sc-configuration-manager-2012-r2-os-deployment-error-at-windows-deployment-services-tr-tr.aspx
In that case,the solution is install the Hotfix KB2905002.
Below is the link to download and install this Hotfix.
http://support.microsoft.com/kb/2905002
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WDS error message Windows cannot be installed

Hi I am new on the WDS environment, yesterday I installed the role on a Win 2012 server, added the DHCP config, the boot image and the install image from a windows 7 64 bit ISO and now when I try to push the install into a dell latitude E5530 I get an error
message right at the end on the Windows 7 install saying that Windows cannot be installed in this hardware.
What am I doing wrong?

Hi xhoffman,
This error can occur when you try to install Windows 7 or Windows Server 2008 R2 on a system if the following situation is true on your PC:
You are installing by using Windows 7 or Windows Server 2008 R2 RTM media.
Your system has an Intel storage controller that is configured to "RAID" mode in the BIOS. (This is a standard setting for many PC manufacturers).
The hard drive you are installing to an "Advanced Format" disk.
Please check your installation media and BIOS drive settings or download the appropriate drivers for your hard disk drive.
You could also check your setupact.log and setuperr.log for more failure details
https://technet.microsoft.com/en-us/library/hh825073.aspx?f=255&MSPPError=-2147217396
For more information or advanced methods
http://support.microsoft.com/en-us/kb/2466753
Regards
D. Wu

WDS Error Code:0xc1420127

I am trying to add a network driver to a 64 bit Windows 7 boot image. I get the error:
Error Occurred while trying to execute this command.
Error Code: 0xc1420127
The driver is for an HP 8540p. I was able to add drivers to it before but it seems like anything 64 bit won't take. I've deleted and reinstalled the image to no avail. I've tried adding drivers with dism and that hasn't resolved either.
Please help!

Hello!
Unfortunately dosen't work. As I think this is architecture problem.
Server Win2k8 R2 Enterprise SP1 RU.
WDS Role Installed. With Windows 7 Enterprise x64-based boot&install images WDS working very well. Network drivers (x64) was added succesfully into x64-based boot image. Also after oobe preparation vga-drivers (x64) was added successfully to install.wim
(with DISM /add-driver utility).
Now I need to deploy x86-based Windows 7 Enterprise. Boot and install images was added to the server without any probles. It is necessary to add network x86 driver package to x86 Windows 7 Enterprise boot.wim. But I have problems during adding drivers:
Error Code:0xC1420127
As you can see x64 images can be added wery well.
How can I resolve the promblem? Can anybody help?
Thank you.

WDS errors - but it seems to work

I keep getting this silly flashing orange light. Then it goes green for a minute, then orange again.
I have a totally up to date (software) installation of the following
1) APExtreme - setup in N(BG) mode, its also the main WDS
2) 3 AP Express - setup in b/g mode, also setup as remote WDS.
So, everything seems okay - I can see them all in the admin util, and access them all. I can see all the names in iTunes. What I cannot figure out is why I keep getting errors in the logs for 2 of the APExpress that seem to be constantly getting disassociated from WDS. I think this would be everything. have the logs set to Debug. Anyone have a clue how to get rid of this?
Here are the logs:
Jul 02 20:32:20 Severity:5 WDS established with station 00:11:24:06:dc:d1
Jul 02 20:32:20 Severity:5 Associated with station 00:11:24:06:dc:d1
Jul 02 20:32:20 Severity:5 Installed unicast TKIP key for supplicant 00:11:24:06:dc:d1
Jul 02 20:33:17 Severity:5 WDS expired with station 00:11:24:06:dc:d1
Jul 02 20:33:17 Severity:5 Disassociated with station 00:11:24:06:dc:d1
Jul 02 20:33:19 Severity:5 WDS expired with station 00:11:24:03:6b:7b
Jul 02 20:33:19 Severity:5 Disassociated with station 00:11:24:03:6b:7b
Jul 02 20:33:23 Severity:5 WDS established with station 00:11:24:06:dc:d1
Jul 02 20:33:23 Severity:5 Associated with station 00:11:24:06:dc:d1
Jul 02 20:33:26 Severity:5 WDS established with station 00:11:24:03:6b:7b
Jul 02 20:33:26 Severity:5 Associated with station 00:11:24:03:6b:7b
Jul 02 20:33:26 Severity:5 Deauthenticating with station 00:11:24:06:dc:d1 (reserved 2).
Jul 02 20:33:26 Severity:5 WDS expired with station 00:11:24:06:dc:d1
Jul 02 20:33:29 Severity:5 Deauthenticating with station 00:11:24:03:6b:7b (reserved 2).
Jul 02 20:33:29 Severity:5 WDS expired with station 00:11:24:03:6b:7b
Jul 02 20:33:37 Severity:5 WDS established with station 00:11:24:06:dc:d1
Jul 02 20:33:37 Severity:5 Associated with station 00:11:24:06:dc:d1
Jul 02 20:33:37 Severity:5 Installed unicast TKIP key for supplicant 00:11:24:06:dc:d1
Jul 02 20:33:39 Severity:5 WDS established with station 00:11:24:03:6b:7b
Jul 02 20:33:39 Severity:5 Associated with station 00:11:24:03:6b:7b
Jul 02 20:33:39 Severity:5 Installed unicast TKIP key for supplicant 00:11:24:03:6b:7b
Jul 02 20:33:39 Severity:5 Associated with station 00:0f:86:67:53:66
Jul 02 20:33:39 Severity:5 Installed unicast CCMP key for supplicant 00:0f:86:67:53:66
Jul 02 20:35:18 Severity:5 WDS expired with station 00:11:24:03:6b:7b
Jul 02 20:35:18 Severity:5 Disassociated with station 00:11:24:03:6b:7b
Jul 02 20:35:19 Severity:5 WDS expired with station 00:11:24:06:dc:d1
Jul 02 20:35:19 Severity:5 Disassociated with station 00:11:24:06:dc:d1
Jul 02 20:35:24 Severity:5 WDS established with station 00:11:24:03:6b:7b
Jul 02 20:35:24 Severity:5 Associated with station 00:11:24:03:6b:7b
Jul 02 20:35:25 Severity:5 WDS established with station 00:11:24:06:dc:d1
Jul 02 20:35:25 Severity:5 Associated with station 00:11:24:06:dc:d1
Jul 02 20:35:27 Severity:5 Deauthenticating with station 00:11:24:03:6b:7b (reserved 2).
Jul 02 20:35:27 Severity:5 WDS expired with station 00:11:24:03:6b:7b
Jul 02 20:35:28 Severity:5 Deauthenticating with station 00:11:24:06:dc:d1 (reserved 2).
Jul 02 20:35:28 Severity:5 WDS expired with station 00:11:24:06:dc:d1
Jul 02 20:35:37 Severity:5 WDS established with station 00:11:24:03:6b:7b
Jul 02 20:35:37 Severity:5 Associated with station 00:11:24:03:6b:7b
Jul 02 20:35:37 Severity:5 Installed unicast TKIP key for supplicant 00:11:24:03:6b:7b
Jul 02 20:35:38 Severity:5 WDS established with station 00:11:24:06:dc:d1
Jul 02 20:35:38 Severity:5 Associated with station 00:11:24:06:dc:d1
Jul 02 20:35:38 Severity:5 Installed unicast TKIP key for supplicant 00:11:24:06:dc:d1

Did you find a solution to this problem? I'm encountering the same issue.
Cheers,
joel

Airport Extreme N works fine but not when WDS activated

I replaced my old Airport Extreme by the new 802.11n.
Works fine with our Macbooks (pro) enabled for n.
But when I activate WDS (I'd like to use my old airport Express for airtunes sometimes), an error message appears (WDS error) in the summary, and the light flashes alternatively in green and yellow... Everything else seems to work (internet connexion), but it seems no WDS possible... If I swtich it off, everything is just fine and green...
Of course I reinitialized the base, I once used the Airport utility assistant and then manually reput my personal options. I upgraded my airport firmware to 7.1 and WDS error message is still there with the flashing light... And I tried to see if my old express would make it but nope.

I had similar issues. To roll the firmware back to an earlier version try this:
- With the option key depressed, launch the Airport Utility (located: /Applications/Utilities)
- Select your problematic extreme base station and then while holding option again, click "Continue" and then choose Manual Setup.
- It should prompt you to choose a firmware version to upload. You can select 7.0 or 7.1.
The process is a little different on PC. Let me know if this solves your problem or if you need the directions for doing this from within Windows!

WDS Set up - Help Needed! Airport Extreme with one Relay and one remote

Hi Guys,
I need a bit of help. I am feeling quite stupid and frustrated. I am having some difficulty with setting up a WDS network with:
Base station: Airport extreme (current version)
Relay: Airport Express (current version)
Remote: Airport Express (current version)
I start by cold resetting the three units. The Base station is connected via Ethernet. The setup I wish to get going is a simple base - relay - remote.
I go through the utility manager and set up the base station, first as "create a wireless network" enter the ISP details etc etc. Its green light. Everything is fine. Then manually configure the Base Station. Hold down option key hit Participate in a WDS. I then select main enter + and add the Mac Id's for the intended Relay unit and Remote Unit (12 character and numeric string). At this stage I am only adding the intended Relay unit and Remote units MAC number.
Question 1: Do I need to add the base unit's MAC number itself under: WDS Remotes? even I am setting it up as Main?
I am careful to note the security settings and the the Wireless Network name to match these in the relay and remote set up. Under the Wireless tab I leave the Radio Mode: as Automatic (802.11a/n - 802.11b/g/n). I make sure the base has "allow this network to be extended" ticked. Under Radio Channel selection I edit it to reference channel 1 for 2.4Ghz (5 Ghz leave as Auto). I am careful when setting up the Relay and remote to match the Radio Channel. (Although I tired many channels as I thought maybe interference was a factor and denying the fact its obviously my set up skills as a factor).
Question 2: Do you need to disable Guest networks? I would think it does not matter as I have tired turning it off and has not made any difference.
Under Access Control I leave as default, Not enabled.
Next I hit update and and error message comes up. WDS Error as it can not find other units. Ok fine as the relay and remote are not yet set up. So I ignore and can get to the stage where the base unit is working and green light with an internet connection.
I then proceed to set up the Relay unit. Doing the same steps as above with a couple of differences being I add the MAC numbers and select the WDS Mode (Relay for Relay and Remote for Remote. I add the Main base station (i.e Airpot Extreme MAC No.) when prompted and then + the Remotes MAC number. The same for the Remote except I only need to add the base station's main no.
Question 3. Do I need to add the Relay's own MAC number to its own setup? This seems doubtful as with the base station but tired with and without for good measure with no success.
The 2.4Ghz channels are all set to 1. Radio mode set to Auto. Although even when I try to manually set them to all identical it doesn't seem t help.
Then the problems begin. The base unit is Green and the Relay and Remote say they are not connected to the internet. I assume since I have not seen a WDS Error message then the units are set up correctly or as I ignored it on the base unit. But when click unignore the error seems to work itself out.
Question 4. I need help to understand why I have no internet. The remote / relay says something about no IP number and I don't really understand what I should do? Do I need to go back the Airport Utility Manager and start messing about with the TCP/IP, DHCP, NAT ? The base is set up PPPoE and the relay and remote are set to Bridge.
It is really puzzling me why the relay and remote flash amber with error messages related to the IP number? I have tried turning off the base station and router and then on again but no joy.
Can anyone please enlighten me or give me a few ideas? I am doing something very obviously stupid and I guess the fix is something simple that I have overlooked.
I did spend the time and go through the threads and search online, So I am not trying to waste anyone's time I referenced the two links to get a second opinion:
http://broadcast.oreilly.com/2009/03/taming-an-airport-express-wds.html
http://www.macobserver.com/tmo/article/settingup_an_airport_relay_with_airportexpress/
Any help much appreciated!

Versed wrote:
I need a bit of help.
Welcome to Apple's discussion groups.
My WDS experience is limited to "main" and "remote" configurations (no "relay"), so I'm not posting from direct experience, but below is what I think would work in your case.
I go through the utility manager and set up the base station, first as "create a wireless network" enter the ISP details etc etc. Its green light. Everything is fine. Then manually configure the Base Station. Hold down option key hit Participate in a WDS. I then select main enter + and add the Mac Id's for the intended Relay unit and Remote Unit
I don't think the "main" unit needs to be told about the "remote" unit, only about the "relay" unit.
Question 1: Do I need to add the base unit's MAC number itself under: WDS Remotes? even I am setting it up as Main?
You'd never enter the MAC address of a unit into its own configuration, if that's what you mean. I also don't think that you'd need to enter the MAC address of the main into the remote and conversely.
I am careful to note the security settings and the the Wireless Network name to match these in the relay and remote set up. Under the Wireless tab I leave the Radio Mode: as Automatic (802.11a/n - 802.11b/g/n).
Five things have to match in a WDS configuration: network name, encryption type, network password, band, and channel.
I make sure the base has "allow this network to be extended" ticked.
I don't think that's important for a WDS configuration.
Question 2: Do you need to disable Guest networks?
I wouldn't think that matters.
Under Access Control I leave as default, Not enabled.
That's fine.
WDS Error as it can not find other units. Ok fine as the relay and remote are not yet set up.
Right.
I then proceed to set up the Relay unit. Doing the same steps as above with a couple of differences being I add the MAC numbers and select the WDS Mode (Relay for Relay and Remote for Remote. I add the Main base station (i.e Airport Extreme MAC No.) when prompted and then + the Remotes MAC number. The same for the Remote except I only need to add the base station's main no.
I think this should be the MAC address of the relay station, not that of the main station.
Question 3. Do I need to add the Relay's own MAC number to its own setup?
No.

Can't get WDS Relay mode to work.

I'm trying to create a wireless network between 2 houses across from one another. Basically, I want to use a SlingBox to access a DirecTV receiver attached to a large satellite dish. I have 3 new Airport Extreme 802.11n base stations and if I could get them linked together this should work really well. One base station in my current house, one in my old house connected to the SlingBox, and one somewhere in between acting as a relay.
I've tested this set-up with the 3 base stations in one room and I just can't get it to work. No matter what, the base station that's set to WDS Relay always has a blinking amber light. The main base station and the remote base station both have green lights. Also, once relay station has a blinking amber light, I can hardly ever access it from the Airport Utility. I usually have to completely reset it and start all over again. When I have been able to access it, the error messages have been either a WDS error saying no peers can be found or an "Ethernet Unplugged" error, even though I have it set to participate in a WDS network.
Has anyone been able to set up a network using an airport base station set to WDS Relay yet? If I can't get this to work, will I get the same results just using an extended Airport network rather than a WDS network, setting the 2 additional base stations to extend the network?
Thanks,
Steve
MBPro Core 2 Duo Mac OS X (10.4.8)

Oh, and how do you like the SlingBox? Are you
running the Mac OS version?
I love my Slingbox, which is running the MAC OS version ......but
It was working fine until I swopped my D-Link wireless router for an Airport Extreme. My Slingbox was reaching my WLAN via the ethernet port of an Airport Express, but since "upgrading" to a X-modem and Airport Extreme set up I have hit trouble.
I can set up the Airport Express to join the Airport Extreme WLAN (e.g. for Air Tunes), but not to extend the network.
If I try to set up the Airport Express from a factory re-boot to extend the network with Air Port Utility, it just seems to crash the Airport Extreme.
Alternatively if I try to change the setting on the Airport Express with Air Port Utility to "participate in a WDS network" I get the error message "WDS requires multiple base stations. Please add at least one WDS peer" and I don't understand what that means.
BTW, my Airport Extreme is set up with "allow this network to be extended" checked.
Airport Express & Airport Extreme don't seem to be altogether compatible.
Any and all assistance will be gratefully received!

WDS error?

Similar Messages

Maybe you are looking for