Access points joining different WLC

hi
i have a wireless controller module( NME-AIR-WLC25-K9) installed in a Cisco 2851 ISR, this setup is in my remote site, we are connected through MAN network. In our main office i have a cisco 4402 wireless controller. so whenever i install a AP in my remote site instead of joiining the remote site WLC, the access point joins my main office 4402 controller, i dont why it is happening, the AP is not even trying to join the remote site WLC.. i have not configured high availability and both these controller are in separate RF network.
the firmware version in NME-AIR-WLC25-K9 is 7.0.98.0 ...
the version in the other controller is 6.0.196.0
Please let me know what is else i need to check asap
Thanks
karthik

Hi,
  Did you even see the AP trying to join the local controller?  If the controller are in different domains, the AP will prefer the remote controller since it join that one first.  Since you are running 5.2, try configure on the AP the primary controller with the name, and local IP address of the local controller, and then reboot the AP.  See if after that the AP join. run debug capwap events enable to see if you see the AP event trying to join the controller.
Regards,
Manuel

Similar Messages

  • Access Points Joining Random WLC

    My environment contains 4 seperate controllers.  1 controller in the datacenter which remote offices use with HREAP and discover this WLC using DNS  We will call this Controller WLC1.  2 more controllers (WLC 2 and WLC 3) in the corporate headquarters to support >40 access points in a N+1 configuration and finally an anchor controller which doesnt matter in this post.
    What I am experiencing is Access points in the Corporate office are using DHCP option 43 to discover the WLC2. every night or after long periods of time a random number of my access points are either rebooting or most likely sleeping.  Then are attaching them selves to WLC 1 which is in the datacenter and is not supporting DHCP from that location which to clients make the wireless network seem to be down.
    I think that with using a hybrid of DHCP and DNS is partly my issue but it shouldnt be. I have primed all the Access point to look at primary controller WLC1 and secondary controller WLC2 both by name and using the IP address of the respective management ports.
    Can there be any explaination for this and why this seems to be so random?
    WLCs are 5508
    Corporate Access points are 1142
    ***EDIT
    After some more investigation this isnt completely random rebooting the access points in question are connected to a new 4506-E chassis with the Sup 6-E while the other access points are connected to a 6509-E.. not sure how much this matters but I am seeing in the access point logs that about every 2-3 hours they are accessing DHCP again and sometime not successfully.  Is there some EnergyWise or power savings happening on the 4500 possibly??

    I understand that all and here is a screen shot (see attached) of an ap that was on WLC 2 last night at midnight when i wrote this orginally and now how jumped to WLC 2..  The major issue here is that WLC 1 does not give out DHCP because it is used for HREAP and remote office that have other local DHCP servers.
    I am running code 6.0.199.4
    Now yes all controllers WLC1,2,and3 are in the same mobilty group.  Maybe I should move the WLC1 out of the mobility group and that might solve the issue.  Here is a log too.  See timing is 3 hours and then its trying to find another controller.  I see a retransmission count exceeded here. What can cause that?  I have 4 port LAG configured on both WLC2 and WLC3 and they are both on seperate 6500 switches.  This access point is on a seperate floor connected to a 4500 with uplink to each of the 6500's
    **********LOG from Access Point***********
    *Oct 14 02:41:21.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.104.210.21 peer_port: 5246 This Is correct
    *Oct 14 02:41:21.000: %CAPWAP-5-CHANGED: CAPWAP changed state to 
    *Oct 14 02:41:21.826: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.104.210.21 peer_port: 5246
    *Oct 14 02:41:21.827: %CAPWAP-5-SENDJOIN: sending Join Request to 10.104.210.21
    *Oct 14 02:41:21.827: %CAPWAP-5-CHANGED: CAPWAP changed state to  
    *Oct 14 02:41:21.911: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
    *Oct 14 02:41:22.047: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
    *Oct 14 02:41:22.052: %LWAPP-3-CLIENTEVENTLOG: Received AP Syslog IP Address(255.255.255.255) configuration.
    *Oct 14 02:41:22.173: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller nwcp01-1211-02b
    *Oct 14 02:41:22.254: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[0]
    *Oct 14 02:41:22.255: %DOT11-4-NO_HT: Interface Dot11Radio0, Mcs rates disabled on vlan 1 due to WMM is not enabled
    *Oct 14 02:41:22.257: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[0]
    *Oct 14 02:41:22.259: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[1]
    *Oct 14 02:41:22.261: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[1]
    *Oct 14 02:41:22.263: %DOT11-4-NO_HT: Interface Dot11Radio1, Mcs rates disabled on vlan 1 due to WMM is not enabled
    *Oct 14 02:41:22.263: %DOT11-4-NO_HT: Interface Dot11Radio1, Mcs rates disabled on vlan 2 due to WMM is not enabled
    *Oct 14 02:41:22.264: %DOT11-4-NO_HT: Interface Dot11Radio0, Mcs rates disabled on vlan 2 due to WMM is not enabled
    *Oct 14 02:41:22.274: %WIDS-6-ENABLED: IDS Signature is loaded and enabled
    *Oct 14 05:57:40.164: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_ECHO_REQUEST
    ., 3)
    *Oct 14 05:57:40.164: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
    *Oct 14 05:57:40.164: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.104.210.21:5246  *** This is correct
    *Oct 14 05:57:40.206: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
    *Oct 14 05:57:40.207: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Oct 14 05:57:40.207: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Oct 14 05:57:50.229: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Oct 14 05:57:49.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.98.10.20 peer_port: 5246 **This is the controller it should never get on.
    *Oct 14 05:57:49.000: %CAPWAP-5-CHANGED: CAPWAP changed state to 
    *Oct 14 05:57:49.844: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.98.10.20 peer_port: 5246
    *Oct 14 05:57:49.845: %CAPWAP-5-SENDJOIN: sending Join Request to 10.98.10.20
    *Oct 14 05:57:49.845: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
    *Oct 14 05:57:49.930: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
    *Oct 14 05:57:50.078: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
    *Oct 14 05:57:50.078: %LWAPP-3-CLIENTEVENTLOG: Received AP Syslog IP Address(255.255.255.255) configuration.
    *Oct 14 05:57:50.206: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller nep00WLC00e
    *Oct 14 05:57:50.293: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[0]
    *Oct 14 05:57:50.298: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[0]
    *Oct 14 05:57:50.303: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[1]
    *Oct 14 05:57:50.309: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[1]
    *Oct 14 05:57:50.414: %WIDS-6-ENABLED: IDS Signature is loaded and enabled

  • Limiting access points joining a specific WLC

    Hello Cisco Forum Team!
      I am currently installing a new WLC in a VLAN/IP segment that already has WLCs configured and access points registered. I do not want existing ap's on this VLAN to join this new WLC.  Which is the best way to limit ap's joining this new WLC?
    I am thinking of some sort of AP authorization list but by IP address instead of MAC address due to the high amount of ap's currently registred on the existing WLCs (approx. 300 ap's).
    Thanks in advanced for your support!

    AP authorization list would work but you have to use MAC address & cannot use IP address for that. Once you enable AP authorization you can add AP mac to the list like below using CLI.
    (5508-1) >config auth-list add mic <AP1 mac>
    (5508-1) >config auth-list add mic <AP2 mac>
    (5508-1) >config auth-list add mic <APn mac>
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • Access points with differing regulatory domains?

    I have four new air-lap1142n-e-k9 that I'm attempting to connect to a wireless lan controller 4402.
    We have about 8 similar devices connected to it since earlier.
    Connecting them to the wlc isn't a problem, but only the 802.11b/g interface comes up when they're
    connected, the 802.11a is taken down. Looking at the configuration of the ap it seems that the
    802.11a interface has the wrong regulatory domain. Should be Sweden and '-E' (which all the other
    aps have), but the new ones all have -E on the 802.11b/g and -C on the 802.11a (see attached wlc
    webgui screenshots).
    Is there a way of changing the regulatory domain of the 802.11a interfaces to -E?
    And out of curiosity, is there a point in having different regulatory domains on different interfaces on
    the same access point..?
    Thanks in advance.
    /richard

    Please check if the regulatory domain should be on the same AP. Please check the PDF for referring codes of different countries-
    http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aecd80537b6a.pdf

  • Access point connection to WLC

    Hi all,
    I wanted to know that in Cisco wireless or in general, is it possible to connect lightweigt access point with controller without any wired connection ? or a ethernet connection between an AP and WLC is mandatory ???

    What can't you find?
    Reference to the Wireless LAN Controller not having a Wireless NIC? The documents won't list everything the product doesn't come with, it lists what it does come with.
    This guide is helpful:
    http://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/consolidated/b_cg74_CONSOLIDATED.pdf
    It doesn't state that the Access Points can communicate with the WLC Wirelessly because they can't.

  • Access Points Joining 3850 next generation switches

    It's my understanding that APs can join 3850s if and only if the APs are directly connected to ports on the 3850 next generation device.
    Can someone point me to where this is explained?

    CB90021204 - APs indirectly connected to a 3850 (connected to a downstream switch) will not join the 3850
    Q. Does the Cisco Catalyst 3850 support indirectly connected access points?
    A. No. The Cisco Catalyst 3850 switch will always terminate the CAPWAP  tunnel locally. Pass-through mode or indirectly connected access point  is not supported at this time.
    http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps12686/qa_c67-722110.html

  • Access Points Joining

                       Dear sir/ma,
    I have bought a wireless LAN controller and access points of 10 qty
    Item Name
    Quantity
    AIR-CT5508-12-K9
    1
    CON-SNT-CT0812
    1
    LIC-CT5508-12
    1
    LIC-CT5508-BASE
    1
    PI-MSE-PRMO-INSRT
    1
    AIR-PWR-5500-AC
    1
    SWC5500K9-72
    1
    AIR-PWR-CORD-UK
    2
    AIR-CAP2602I-E-K9
    10
    CON-SNT-C262IE
    10
    SWLAP2600-MESH-K9
    10
    AIR-AP-BRACKET-1
    10
    AIR-AP-T-RAIL-R
    10
    but the access points are not joining the controller. please what could be the cause of this?
    please find the attached file for the configuration output.
    br
    kuku

    Hi,
    For the Mesh APs, you must enter the MAC address in the MAC filter which is found in
    Security > AAA > MAC Filtering. Note that Outdoor Mesh APs, the MAC address is the BVI mac address, for Indoor Mesh, it is the Ethernet MAC address.
    Also, if you're using DNS for controller discovery, create a pointer record in your DNS with the following:
    CISCO-CAPWAP-CONTROLLER.domainname - IP address of WLC

  • Lightweight access-point joined the wireless controller but no radio channels

    a customer  wireless controller 2106  he use  access-point AIR-LAP1252G-E-K9  the access point the leds indicate
    etherner and radio is blinking green and status is green.
    please help i am in the customer company now

    The AP1252 has higher power requirements than some of the Cisco PoE switches provide.  Depending on the switch you are plugging them into you will get enough power to power up the device and connect to a controller but not enough to power up the antennas.  Options that can work include:
    1) Removing one of the antennas if you are not gonig to use it (or as a temporary workaround to get some wireless)
    2) Using an external power supply
    3) Using an external inline power appliance system that supplies enough power (http://www.microsemi.com/powerdsine/ is one example).
    4) Depending on the type of switch you are connecting to you may be able to upgrade code to provide a higher amount of power to the port.  For instance, a Catalyst 6500 by default supplies 15.8 watts of power to a port.  But if you upgrade the code to 12.2(33)SXH2? I believe you can get 16.8 watts of power and this is enough to bring up both antennas on the AP.  But even then you don't have enuf power to run the upper N speeds - I think anything above 72 Mbps is unattainable.
    Other AP models such as the 1140 have lower power requirements and may work better for you.

  • 602-OEAP Access Point broken after WLC upgrade to 7.4.100.0

    Hey all,
    I have a TAC case open, but it doesn't seem to be making any progress....
    I upgraded my 5508 controller from 7.2.111.3 up to 7.4.100.0
    Most of my APs are fine. 3500s, 1100s etc.except for 602i APs. The APs associate, they update software etc, but they won't broadcast the WLAN.
    An interesting thing, on the 602 AP, in the log, I see this:
    *Mar 06 15:08:12.667: SSID remote, WLAN Profile Name: RemoteOEAP, added to the slot[0], disabled
    So the AP is definately talking to the WLC and being pushed the correct WLAN profile.
    Another thing I noticed:
    On the controller, the AP shows the the Admin status of the radios is showing DOWN, but the Admin status on the AP itself shows UP
    I've done a factory reset on the APs to no avail. I have a 2504 WLC as well that i'm in the process of implementing in a DMZ specificially for these APs, and for testing purposes, I associated the 602 Ap to that WLC as well. This one is running 7.4.100.0 too, same results. It would appear to be a problem with this version of software?
    Anyone else had this problem?

    Hey, thanks for taking a look at this. Unfortenately, that's not the issue in this case. The AP is set to "United States" and the WLC is only configured for US. Just so I'm looking in the correct place:
    On the AP in the WLC, it's under the "Advanced" tab
    On the WLC, its under Wireless -> Country correct?
    The frustrating part is that the 600 really doesn't have anything that can be configured on it, which means troubleshooting is also limited.

  • E71 Different Access Points for different modes?

    Hi
    I have just got the E71 and think it's a really good phone. I have a question about the two different modes that the E71 can switch from and to.
    I would like to be able to have a "Home Mode" and an "Away Mode".
    The Home Mode would use a default WLAN connection for web and push email.
    The Away Mode would use a mobile web connection from my mobile provider for web browsing and push email etc.
    Is this possible at all?
    I have tried changing the incoming mail connection setting on one of the modes but when I switch to the other mode the incoming mail settings are what was set in the previous mode.
    Hope that made sense?
    Thanks in advance

    I've the same question !

  • Access Points not joining WLC

    Hello All,
    I am trying to deploy several AIR-CAP3502E-E-K9 access points from a cisco 5508 wire lan contoller running ver 7 code. However iam having difficulty regiserting the access points with the WLC. The wlc is connect to a 3650 switch, and each access point is connected to a 2960 switch.
    Problem Solved. A bad update was not allowing the access points to get their correct firmware.

    You need to provide what Leo stated, that would help a lot. Anyways you can't telnet or ssh into a capwap AP if it has not joined the WLC. So that being said, provide the info Leo requested and then console into the ap and provide use with output from the console. Make sure you reboot the AP and then start capturing the output for around 5 minutes.
    Sent from Cisco Technical Support iPad App

  • MFP Anomaly Detected Access Points are moving from one wlc to another and vice versa

    Hi together,
    a customer has lost some Access Points to another WLC with 7.2  and then they come back after 15 minutes to the origin WLC with 7.5
    Attached the messages
    MFP Protection is configured as optional
    152
    Wed Nov 27 05:33:26 2013
    MFP Anomaly Detected - 1 Not encrypted event(s) found as   violated by the radio 58:bf:ea:0f:67:4a and detected by the dot11 interface   at slot 1 of AP 58:bf:ea:0f:67:40 in 300 seconds when observing . Client's   last source mac 70:11:24:e4:43:0f
    153
    Wed Nov 27 05:31:40 2013
    AP Disassociated. Base Radio MAC:88:43:e1:56:91:d0
    154
    Wed Nov 27 05:31:40 2013
    AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:88:43:e1:56:91:d0 Cause=New Discovery Status:NA
    155
    Wed Nov 27 05:31:33 2013
    AP Disassociated. Base Radio MAC:58:bf:ea:0f:73:d0
    156
    Wed Nov 27 05:31:33 2013
    AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:58:bf:ea:0f:73:d0 Cause=New Discovery Status:NA
    157
    Wed Nov 27 05:31:33 2013
    AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:58:bf:ea:0f:73:d0 Cause=New Discovery Status:NA
    158
    Wed Nov 27 05:31:28 2013
    AP Disassociated. Base Radio MAC:58:bf:ea:0f:fc:20
    159
    Wed Nov 27 05:31:28 2013
    AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:58:bf:ea:0f:fc:20 Cause=New Discovery Status:NA
    160
    Wed Nov 27 05:31:28 2013
    AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:58:bf:ea:0f:fc:20 Cause=New Discovery Status:NA
    161
    Wed Nov 27 05:31:17 2013
    AP Disassociated. Base Radio MAC:b4:e9:b0:e4:02:20
    162
    Wed Nov 27 05:31:17 2013
    AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:b4:e9:b0:e4:02:20 Cause=New Discovery Status:NA
    163
    Wed Nov 27 05:31:17 2013
    AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:b4:e9:b0:e4:02:20 Cause=New Discovery Status:NA
    164
    Wed Nov 27 05:31:15 2013
    AP Disassociated. Base Radio MAC:a4:18:75:eb:da:b0
    165
    Wed Nov 27 05:31:15 2013
    AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:a4:18:75:eb:da:b0 Cause=New Discovery Status:NA
    166
    Wed Nov 27 05:31:15 2013
    AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:a4:18:75:eb:da:b0 Cause=New Discovery Status:NA
    167
    Wed Nov 27 05:28:26 2013
    MFP Anomaly Detected - 35 Not encrypted event(s) found as   violated by the radio d8:24:bd:2f:df:6f and detected by the dot11 interface   at slot 1 of AP d8:24:bd:2f:df:60 in 300 seconds when observing Deauth.   Client's last source mac 00:23:14:a7:e3:54
    168
    Wed Nov 27 05:23:26 2013
    MFP Anomaly Detected - 23 Not encrypted event(s) found as   violated by the radio f8:4f:57:a5:40:b2 and detected by the dot11 interface   at slot 0 of AP f8:4f:57:a5:40:b0 in 300 seconds when observing . Client's   last source mac 44:4c:0c:ba:27:77
    Don´t know at the moment how to handle it.
    Regards
    Alex

    Hi lAlex,
    Disable Client MFP under WLAN advanced tab & see if  this still occur
    Regards
    Rasika
    **** Pls rate all useful responses *****

  • How do i ensure the new access point is joined the controller or not

    How do i ensure the new access point is joined the controller or not

    To Verifying that Access Points Join the Controller or not there are two ways as below.
    Please go through the step by step to find the APs joined state
    When replacing a controller, you need to make sure that access points join the new controller.
    Using the GUI to Verify that Access Points Join the Controller
    Follow these steps to ensure that access points join the new controller.
    Step 1 Follow these steps to configure the new controller as a master controller.
    a. Click Controller > Advanced > Master Controller Mode to open the Master Controller Configuration page.
    b. Check the Master Controller Mode check box.
    c. Click Apply to commit your changes.
    d. Click Save Configuration to save your changes.
    Step 2 (Optional) Flush the ARP and MAC address tables within the network infrastructure. Ask your network administrator for more information about this step.
    Step 3 Restart the access points.
    Step 4 Once all the access points have joined the new controller, configure the controller not to be a master controller by unchecking the Master Controller Mode check box on the Master Controller Configuration page.
    Using the CLI to Verify that Access Points Join the Controller
    Follow these steps to ensure that access points join the new controller.
    Step 1 To configure the new controller as a master controller, enter this command:
    config network master-base enable
    Step 2 (Optional) Flush the ARP and MAC address tables within the network infrastructure. Ask your network administrator for more information about this step.
    Step 3 Restart the access points.

  • Bridge to bridge and bridge to access-point via wireless is it possible.

    here;s my topology i am trying to configure. i have a router whose ethernet is connected to a bridge.this bridge 1 is connected to a bridge 2 via wireless. now i am trying to connect a access-point via wireless to this bridge2. is it possible for bridge 2 to support connectivity to the bridge1 and the access-point both of them via wireless.
    can someone pls help me on this.
    waiting for someone to reply.
    regards
    sebastan

    You can set up each radio in the access point for different functionality. Considering the scenario, this can be done by setting up the SSID for the G radio and another SSID for the A radio. Then, set the role in the radio network parameter for the G radio to access point and for the A radio to the root bridge role.
    ou can prevent unauthorized users from reconfiguring your access point/bridge and viewing configuration information. Typically, you want network administrators to have access to the access point/bridge while you restrict access to users who connect through a terminal or workstation from within the local network.
    To prevent unauthorized access to your access point/bridge, you should configure one of these security features:
    Username and password pairs, which are locally stored on the access point/bridge. These pairs authenticate each user before that user can access the access point/bridge. You can also assign a specific privilege level (read only or read/write) to each username and password pair.
    http://www.cisco.com/en/US/products/ps5861/products_configuration_guide_chapter09186a00804ed6d4.html

  • Problem with PowerBook (but NOT MacBook) and two access points on network

    I recently installed a wall-plugged ethernet adapter system (Netgear XE104 and XE103) and plugged a wireless access point (Netgear WPN802) into one of the adapters (in the part of our house where we lacked a wireless signal) in order to extend the range of our (DSL) wireless network. I configured this new access point--disabled DHCP, assigned an IP address to the access point that does not fall into the wireless router's IP adress range, put the wireless router and access point on different channels (6 and 11), and made sure the router and access point had the same SSID.
    I have had no problems using the resulting setup with our new MacBook--everything goes as planned. BUT I am having a terrible time with my PowerBook G4. It has a really strong signal everywhere, but when I open my browser it says that I am not connected to the internet. The problem seems to be that my PowerBook refuses to change channels once it connects to one. I installed iStumbler to see if I could manually control which access point/channel the PowerBook uses, and, while I can track the signal strengths for both access points, I can't get my PowerBook to switch from one access point to the other.
    I've tried just about everything I can think of. I suppose I could try giving a different SSID to the access point (and then try to switch with the airport menu in the toolbar), but I would like to avoid this if possible.
    I would really appreciate any advice you have. Thank you!

    Can you connect if you temporarily turn off WEP or WPA?
    This will determine if it is a WEP or WPA issue.
    Does your PC support WPA, from both a hardware and a software perspective?
    The problem you are having probably lies with the encryption key.
    Accessing a Airport Network with a Windows XP PC or laptop (with XP SP2)
    http://tech.ifelix.net/1011.html
    Accessing a Airport Network with a Windows XP PC or laptop (with XP SP1)
    http://tech.ifelix.net/1010.html
    Problems connecting an XP PC to an Airport Base Station
    http://tech.ifelix.net/2002.html
    iFelix

Maybe you are looking for