Understanding of wireless client connection to multiple APs

Hello,
I would like to know how do wireless clients connect to APs
For e.g. if in a single floor square office space - wireless network with multiple APs exists on the same SSID, how do clients decide which AP to connect to. For e.g. the client may get similar strength signals from two APs close to each other (such as Excellent). Which AP does client connect to.
Secondly, how does the load distribution take place. For e.g. if on one AP, 10 clients connect and on the other AP, 20 clients connect, how can equal load distribution be acheived, that is 15 on each AP without the tiring MAC filtering configurations.
Thirdly, is there something like number of user/connection restrictions on APs. I have gone through some AP manuals and did not find any such specifications like max. # of users = 20 etc. Currently we are using D-Link AP and have noticed that once the # of connections go upto 20, performance reduces heavily such as the latency on gateway pings go upto 1000-2000ms.
Fourthly, how can I identify from the client to which AP it is connected.
Thanks.

I would like to know how do wireless clients connect to APs
For e.g. if in a single floor square office space - wireless network with multiple APs exists on the same SSID, how do clients decide which AP to connect to. For e.g. the client may get similar strength signals from two APs close to each other (such as Excellent). Which AP does client connect to.
ANS - Its first come first serve... however.. sometimes if we have multiple SSIDs one with open auth and no encryption and other fuly protected.. then the client wil connect to the open rather the secured on.
Secondly, how does the load distribution take place. For e.g. if on one AP, 10 clients connect and on the other AP, 20 clients connect, how can equal load distribution be acheived, that is 15 on each AP without the tiring MAC filtering configurations.
ANS - MAC is a good option but apart from that.. i have seen somewhere but not able to remember the command which will limit the number of clients per radio..
Thirdly, is there something like number of user/connection restrictions on APs. I have gone through some AP manuals and did not find any such specifications like max. # of users = 20 etc. Currently we are using D-Link AP and have noticed that once the # of connections go upto 20, performance reduces heavily such as the latency on gateway pings go upto 1000-2000ms.
ANS - AP can take upto 2048 MAC addresses.. its recommended not to have more than 24 clients per AP..
Fourthly, hw can I identify from the client to which AP it is connected.
ANS -If the clients are CCX compatible and aironet extentions enabled on the AP. then the command "show dot11 ass" will tell the clients connecting to which AP.. the AP name will get displsayed in the output..
Regards
Surendra

Similar Messages

2504 controller + 2602 APs = wireless clients connectivity problems

Hello, everybody!
I have a connectivity problems of wireless clients. The symptoms are:
1) Some clients receive 169.254.x.x., instead a correct DHCP addresses, less in a minute connection drops, and in controller's "Monitor" > "Clients" tab these clients are marked as "Excluded".
2) Most of the clients receive the correct addresses from DHCP (192.168.2.x), but also loose connection soon.
3) Wireless clients with correct addresses can't ping each other, gateway and an address of the controller's dynamic interface (all of them are in same subnet).
4) And the most suspicious problem is that some machines are unable to connect to APs after several attemps to do that. I mean, I configure controller and change some options, trying to understand, whether they were applied or not and constantly connect and disconnet certain PC to the SSID. After five or ten attempts I can't connect to the SSID. During these attempts, the others PCs stay connected, without interruptions, and they could be reconnected again. It's like some kind of port security works, but I'm not sure...
Do you have any ideas which options should I configure?
My configuration:
I have three interfaces on the controller: virtual, management (default) and dynamic (it is set to the WLAN)
I have one SSID, WPA/WPA2, AES/TKIP, authentication PSK.
My clients are a/b/g/n, all are permitted on the controller. No custom security policies were applied.
All the devices are in a single room: controller, one AP and different clients: desktop, notebooks, iPad, Nokia Lumia, etc.
I have an internal DHCP Server on the controller and it works perfectly well.
I can provide all the screenshots required from web-interface of the controller...
Many thanks in advance for all ideas that you have about these problems...

Hi, there!
The problem was solved.
1) APIPA address receives only single machine with Win8 - I think there are some firewall issues
2) Other devices have been loosing connection because they were mobile devices, like iPad and Lumia. If you keep working with it, it doesn't drop the connection
3) The dynamic interface address and gateway address were inaccessible because i had not used an appropriate port on the controller. =)))) Firstly, it was just a guess, but it proved.
Now, everything works with WPA2, AES, PSK...
It is a very good day!)
The only question remains: why I can't connect machines, which have a static IP? During the controller initialization, I said "yes" for permitting static IPs...
Guys, many thanks for your help!

Solved. Travel router WTR54GS sharing one wireless hotspot connection with multiple devices

Hi, Passing on info I've learned.
The manual for the WTR54GS mentions being able to "...use multiple devices on a single hotspot account in a coffee shop or airport lounge...". See my original posting, "How to set up a wireless private bubble at paid hotspot? WTR54GS?", which ended in a dead end. I subsequently had a Linksys live chat session and the representative provided the solution. Perhaps worthy to be included in the Wireless FAQ?
Situation: you have access to a paid hotspot (hotel room, meeting room, etc.) and you want to share the connection with several devices, also wirelessly.
Solution: the WTR54GS can accept an incoming Internet connection wirelessely and re-broadcast that connection to form your own private bubble or network. (Note the WTR54GS can also accept an incoming Internet connection via Ethernet cable).
Linksys Live Chat pointed me to these web pages.
Go to the Linksys Easy Answers page: For a schematic of the concept of "associating the travel router to a hotspot (wirelessly)" search for Easy Answer ID# 4831
URL for above is http://linksys.custhelp.com/cgi-bin/linksys.cfg/php/enduser/std_adp.php?p_faqid=4831&p_created=1167963305&p_sid=GmLnq3Zi&p_accessibility=0&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9NjImcF9wcm9kcz0wJnBfY2F0cz0xNzIxLDE3MjMmcF9wdj0mcF9jdj0yLjE3MjMmcF9zY2ZfbGFuZz0xJnBfcGFnZT0xJnBfc2VhcmNoX3RleHQ9V1RSNTRHUw**&p_li=&p_topview=1
There is a "configuration simulator" that shows the options for selecting a wired or wireless incoming Internet Type.
http://linksys.com/ui/files/WTR54GS/1.0_15/Setup-Wireless.htm
The hotspot has to be "open", that is transmitting an SSID and with no WEP or WPA key. It may have a log-in page accessible via a web browser, this is okay as this will be passed onto the connected device.
My personal application is to be able to connect a PDA that has a 801.2b wifi to a 801.2g wireless network. I haven't tried it but if this works, it will extend the useful life of my PDA in a "g" environment. Will report back once I find a "g" only environment. Comments?
-Tony
Dang, the long URL is making for a really wide message. Is there a fix?
Message Edited by tony_vancouver on 02-28-2008 02:08 PM
Message Edited by tony_vancouver on 02-28-2008 02:12 PM

There are two conditions which must be met in order to use your WTR54GS to "extend" an incoming, wireless internet connection:
The incoming connection must be unsecured. You have already covered this point;
The security settings on your WTR54GS can only be set to "WEP," or to "Disabled." If you choose "WEP," then you can use either a 40/64-bit, or a 128-bit key.
If those two conditions have been met, then it works fine -- says the guy who is sharing one paid internet conneciton in his hotel amongst three devices, and with co-workers in nearby rooms.

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?!

APEx '03 and Non-Apple Wireless Client Connection Problems

Good morning. I have a 2003 vintage AirPort Extreme, running 5.5.1 firmware (due to the issues with the newer firmware discussed on this forum).
--> Wired iMax
My setup is DSL-->APEx--|
--> Apple Wireless Clients
--> Linksys w54 acting as a bridge
In order to get the Linksys working in the first place, I had to remove the WEP, not a huge deal as we live in the boonies and no one within range of the APEx. I couldn't figure out how to get anything to work with Apple wireless security outside of the Family. I have it manually set to channel 1, and radio mode to G only.
My problem basically is that non-Apple devices can see the SSID but cannot connect. The problem at hand are my kids' various PSPs & Ninendo DS's, and a little Windows CE netbook. Of course, none of these simple devices give anything helpful in terms of errors. Those three different devices all have their own version of the same error: See the SSID, try to connect, but fail.
I'd like to figure out this problem, although the simpler solution might be to just buy another cheap Linksys on craiglist and use it for the non-Apple stuff.

Bump?

Java client connecting to multiple weblogic instances

We have a standalone java client JMS application that needs to connect to multiple
Weblogic instances running in different domains.
The client works fine when we obtain an initial context to the multiple instances
without specifying a security principle and password. As soon as we add in this
information, we get problems: The initial context is still successfully retrieved
for each of the weblogic instances, but we cannot send JMS messages to destinations
on one of the Weblogic instances due to a security exception which states that
there is an 'Invalid Principal'.
Any advice would be appreciated.

You should first establish a trust relationship between your Weblogic
servers:
http://e-docs.bea.com/wls/docs70/secmanage/domain.html#1171534
It is very poorly documented since this is a change in the behavior with
previous versions and should have been in the Release Notes but instead
is inside the normal documentation.
--dejan
jonathan wrote:
Thanks Arvind, but both JVMs are the same (1.3.1) and there is no jsse stuff in
the classpath.
"Arvind Gudipati" <[email protected]> wrote:
check if yr client's jvm version is the same as server's jvm.. ive noticed
this problem a few times when i was using client jvm (1.4.x) connecting
to
server jvm (1.3.x).. also check if u have any jsse libraries in yr
classpath.. if so remove 'em
+arvind
"Jonathan" <[email protected]> wrote in message
news:3f2f9f19$[email protected]..
We have a standalone java client JMS application that needs to connect
to
multiple
Weblogic instances running in different domains.
The client works fine when we obtain an initial context to the multiple
instances
without specifying a security principle and password. As soon as we
add in
this
information, we get problems: The initial context is still successfully
retrieved
for each of the weblogic instances, but we cannot send JMS messages
to
destinations
on one of the Weblogic instances due to a security exception which
states
that
there is an 'Invalid Principal'.
Any advice would be appreciated.

Windows 7 or 8 shows the wireless client connected to the access point but the wireless icon displays "No connection to the internet

I have seen the same issue working with a different vendors wireless solution. When I sniffed the air with OmniPeek and the network the ap was on with WireShark, I see the arp request for the gateway go to the router, the reply from
the gateway router is sent out to the suspect machine in the air, the PC ack's the packet but never populates the arp cache. I have looked at both arp responses in a working vs failing scenario, both packets are the same.
The only way I have been able to resolve it was to disable IP Helper (start up too) from Services, reboot the machine. I was seeing 3 to 4 drops per day but since disabling this Service the machines I have been testing with have not seen the
issue again.
IP Helper:
Provides tunnel connectivity using IPv6 transition technologies (6to4, ISATAP, Port Proxy, and Teredo), and IP-HTTPS. If this service is stopped, the computer will not have the enhanced connectivity benefits that these technologies offer.
Machines Tested and Fixed:
Lenovo E540
Lenovo W540
Acer Aspire One
Dell Latitude E6420
The ip helper service change was made on 40 laptops, a dozen of which would fail in about an hour. So far 0 out of the 40 has seen the issue since making the change and rebooting (rebooting is key after the disable) the laptops. It's
been about 5 days.
Any reason why disabling this Service fixes the issue? With it on I can replicate the issue pretty quickly on a few different machine types so it does not seem to be driver or wireless nic vendor specific. I've checked through the
event viewer logs but nothing seems to be triggered during the time of the issue. Using the troubleshooter or disconnecting from the wireless service will fix the issue for only a short time.

I have seen the same issue working with a different vendors wireless solution. When I sniffed the air with OmniPeek and the network the ap was on with WireShark, I see the arp request for the gateway go to the router, the reply from
the gateway router is sent out to the suspect machine in the air, the PC ack's the packet but never populates the arp cache. I have looked at both arp responses in a working vs failing scenario, both packets are the same.
The only way I have been able to resolve it was to disable IP Helper (start up too) from Services, reboot the machine. I was seeing 3 to 4 drops per day but since disabling this Service the machines I have been testing with have not seen the
issue again.
IP Helper:
Provides tunnel connectivity using IPv6 transition technologies (6to4, ISATAP, Port Proxy, and Teredo), and IP-HTTPS. If this service is stopped, the computer will not have the enhanced connectivity benefits that these technologies offer.
Machines Tested and Fixed:
Lenovo E540
Lenovo W540
Acer Aspire One
Dell Latitude E6420
The ip helper service change was made on 40 laptops, a dozen of which would fail in about an hour. So far 0 out of the 40 has seen the issue since making the change and rebooting (rebooting is key after the disable) the laptops. It's
been about 5 days.
Any reason why disabling this Service fixes the issue? With it on I can replicate the issue pretty quickly on a few different machine types so it does not seem to be driver or wireless nic vendor specific. I've checked through the
event viewer logs but nothing seems to be triggered during the time of the issue. Using the troubleshooter or disconnecting from the wireless service will fix the issue for only a short time.

Wireless Client associated to 2 APs

I searched for my mac address in WCS and I recieved three results. See the attached screenshot. I am just curious why the second entry show I am associated to AP 00:00:00:00:00:00?
I do not have an AP named that.
Running 4.2.130 on all my WLC. Have a mis of WiSM and 4400 Controllers totaling about 10 WLCs.

As Jeff mentioned, this is due to your client roaming and most likely due to wlc roaming. The information you see is not real time accurate, especially the wlc information of clients. You can see that 10.92.0.111 shows the client as still being authenticated which is not the case. So most likely what happens is the wlc is cached until flushed or cleared, but ap's keep the real time information, so the all zero's just mean that the wlc knows of the client but not yet flushed the old info and when it tries to detect which ap that user is on, there isn't one.... so it produces the all zero's.

Airport Extreme and Dlink dwl-2000AP+ as wireless client

Hi,
i'm trying to let an old iMac G3 without any airport card, join an existing lan using an Airport Extreme as router, connecting an old D-Link access point configured as wireless client and connected via ethernet to the iMac G3. All my setup works fine if the wireless connection is open without encryption, but it won't work using any protection like WPA or WEP.
When the airport express wireless connection is protected via WPA, the dlink won't be present in wireless clients list panel. When i use WEP (with a password of 13 characters) i can see in the wireless clients list both the MAC address of the iMac's ethernet and of the dwl-2000AP+ etherenet. But the connection won't work.
I'm sure i'm not configuring right the DWL-2000AP+ wireless protection:
i can't understand if i can change the airport express WEP encryption to a 64 bits or to a 128 bit, if the WEP method used is with a shared key or not.
The only info i get from it to let the clients connect are the WEP ASCII plain-text 13 characters password and its conversion in HEX base.
I'm assuming, since the password is a 13 character, that in WEP encryption the Airport Extreme uses a 128 bits key, but, again, how i can understand if it is used in shared way or in open way?
And why the dlink AP that is WPA capable cannot connect as wireless client to the airport express when is using WPA/WPA2 Personal encryption?
I upgraded the DWL-2000AP+ to its latest firmware that (they sayd)fixes any issue with the wireless client mode on WPA or WEP protected connections.
Thanks in advance for any help given.
P.S.: sorry for my "broken" english
Message was edited by: Rayced

Resolved by myself. It works only setting the Dlink dwl-2000AP+ wireless client connection (wireless pane in the admin control of it) as open with WEP 128bits and using as key an ascii password of 13 charcaters. The Airport Extreme's wireless encryption should be set as WEP, using the same password of 13 charcaters. I still can't uderstand why the WPA/WPA2 encryption wouldn't work since the Dlink dwl-2000AP is WPA capable.
Maybe it could be so because the Airport Extreme is WPA2 and at the first negotiation between it and the dwl-2000AP+, the Airport Extreme won't downgrade to WPA encryption? Does anybody else tried to connect a WPA wireless client to the Airport Extreme setup as WPA2/WPA Personal?
@wallstreet 04: try to setup your Airport Extreme's wireless encryption to WEP and use a 13 chars password, then do the same on the Dlink wireless client you are trying to connect to the base, i don't know how is its control panel but the wireless should be setup as open with WEP 128, as key use that 13 chars password you put in the Extreme's as WEP password. If in the Dlink WEP 128 bits key field you have to put an HEX value instead of the ASCII, you can get that from the Airport Utility from the menu BASE AIRPOT select PASSWORD NETWORK... (the one before the last choice that should be ADD WIRELESS CLIENT).
I hope it will help.

Why are so many wireless clients seen when using airport utility?

When I open up the Airport Utility, I can see upwards of a dozen "wireless clients" connected to each of the two Airport Extremes that I have on my network. Some of these are known computers and iOS devices, but many of them have names that are IP addresses (like 10..0.0.3) or hexadecimal numbers (like 9C:FE:94:4B:75:FE). Not sure what these are. Can they slow down the network?

Take a few moments and count up the total number of wireless devices that you have.
In addition to computers, be sure to include printers, iPhones, iPads, Apple TVs, other Airport routers, other mobile devices, baby monitors, thermostats, etc......anything that uses a wireless signal from your network.
Some devices will be displayed by their name, others by assigned IP address and others by their MAC Address with 12 characters and colons.
Every device that is connected to your network uses up a certain amount of bandwidth, so the more devices that you have connected at one time, the slower the network will operate.
Unless you are lucky enough to have a very fast Internet connection plan with your provider, you may likely notice that browsing, email and other activities on the the wireless slow down when multiple devices are using the Internet, or you are copying files from one device to another over the network.
When you are ready, open AirPort Utility. Hold down the option key while you double click on your AirPort icon.
A window displaying wireless clients will be displayed. Compare the total of devices to your count. If you see more devices than you have, you may have an unwanted guest on your network. Change your wireless network password immediately.
Another thing that you can do is power off all of the wireless devices and then start them up one at a time while you are checking AirPort Utility.

Wireless clients cannot get ip address

I have 7 WLANs configured all work fine but the latest. The 7th WLAN I configured will not let clients get an IP address. I can plug a wire into the port with the same VLAN configured on the port and I get an IP address but wireless clients connected to an AP on that port cannot get an IP adddress. Any suggestions would be appreciated.

Hello,
where is the DHCP server configured?
- do all other 6 WLAN's work fine with the same DHCP server.
- do you have any H-REAP VLAN mapping , or AP groups configured?
they will override the WLAN-interface configuration.
Kind regards
Talal
=======
please rate answers that you find useful , and mark as answered - when it is :-) - so others can find it easily

WRT120N: Wireless Client List - Refresh button useless

WRT120N:
Wireless --> Wireless MAC Filter --> Enabled --> Wireless client list...
Opening Wireless Client List on WRT120N shows the list of wireless clients connected.
Add button is working.
Close button is working
But Refresh button is useless. Even if clients on the lists are already not connected to the router, pressing the Refresh button does nothing. It may add new clients connected but can't determine whether the client disconnects or not. The only way to determine if the client is still connected or not is to Reboot the router (Administration --> Start Reboot).
Refresh doesn't update/remove disconnected clients from the list.
I'm hoping that on future firmware updates for WRT120N, this can be fixed.

Did you try to upgrade/re-flash the firmware on your router?
Connect the computer to the router with the Ethernet cable. Download the latest firmware from Linksys website and save it on your computer. Upgrade/re-flash the firmware on your router. After upgrading the firmware on your router, reset the router and reconfigure it.

E1200 Wireless Client List will not display and causes web UI to temporarily stop responding

I picked up an E1200 and set it up successfully. I am using wireless MAC filtering, and decided to pull up the list of connected wireless clients (Wireless >> Wireless MAC Filter >> push "Wireless Client List" button).
When I do so, it immediately throws this back:
Immediately after this the Web UI of the E1200 becomes inaccessible. It still routes traffic, and the router remains pingable, but it will not allow access to the Web UI for several minutes. The error that appears upon attempt to access the Web UI during this time window is similar to the above, but reads "Error 102 (net::ERR_CONNECTION_REFUSED): The server refused the connection."
I have tried this in Google Chrome, Firefox 4, and MSIE on two separate computers. Each browser displays the error a bit differently (MSIE, for example, just says it can't display the page and gives no further detail) but the net results are always the same. I have tried resetting the device to factory defaults in addition to re-downloading the firmware from the Cisco/Linksys website and installing it. No improvement.
I have also noted that the Log (Administration >> Log; and yes, I have it enabled) doesn't appear to be picking up anything at all. In fact, the Security log, which supposedly (according to the Help) "displays the login information for the Router’s browser-based utility," is also blank.
Is this a bug, or should I head back to the retailer and swap this device?

Ok - I nailed this down, I think, and it looks like a firmware bug.
Short version is that a factory reset cleared the issue, but during stepwise reconfiguration the problem came back. Through a bunch of iteration I figured out that if I have the E1200's DHCP server disabled *and* have wireless clients connected to it, the problem I described appears.
Turn the DHCP server back on and the problem goes away. Turn it off and the problem comes back. Turn it back on and it goes away. You get the idea.
If I had to pose a theory here, it's that the initial display of the Wireless Client List, which uses "IP Address" as the default sort, somehow implodes if the E1200 isn't actually assigning those IP addresses to the clients.
When this happens it appears to crash the Web UI wholesale. Just for grins, while the Web UI was unresponsive, I pinged the router it as before - still pingable - then ran nmap against it - no open ports found on the router. When the Web UI is functional, though, nmap detects port 80 quite easily. I have not timed how long it takes for the Web UI to come back up, but it is longer than 5 minutes, and I presume some sort of watchdog process has to detect that it has gone kaput and start it up again.
Final test was to restore my saved configuration from before the factory reset (note that the saved config was done under the same firmware version, and in this config, the DHCP server is disabled). Boom, problem. Wait for the Web UI to come back, turn on the DHCP server. Problem goes away. Turn the DHCP server off. Boom, problem comes back.
So, there you go.
Would be interesting if someone could verify this via a test against another E1200. It may be worth noting that in my baseline test I was also using Manual wireless setup (vs. Wi-Fi Protected Setup), and WPA2. Didn't make any other setting changes from the factory defaults. I did not actually have to turn the Wireless MAC Filter on to do the test. All one needs to do is click Enable on the Wireless MAC Filter tab, and then do *not* click Save Settings - just clicking Enable will light up the Wireless Client List button, which you can then push to get the list. That is how I handled testing to ensure that neither specific entries, nor the Prevent/Permit setting, nor having the filter enabled in saved configuration were involved in the problem.
Separately, no explanation for the lack of entries in the security log, but that pretty much looks like a firmware bug to me as well.

WRT54GX2 Wireless Security Enabled DHCP blocked for wireless clients

Hey gang,
My subject says it all. Yesterday I updated my WRT54GX2 version 1's firmware to the latest and greatest.I first reset the box, and rebooted. I updated the firmware. On the first attempt I picked the wrong image file. The machine halted and told me bad image. I then found and installed the correct image. I then added an Admin password, and entered a new SSID. I left the DHCP settings at the default. I then set wireless security at WPA Personl/WPA2 with TKIP&AES.
I found the wired client could obtain an IP address and to connect to the internet. The wireless clients could connect, but could not obtain an IP address.
I left the wireless security settings off.
Any suggestions?

The wireless security settings are correct. The wireless clients "CONNECT" to the WRT54GX2. The clients stall on obtaining an IP address via DHCP. Fixing the clients with static IP addresses also does not work.
I repeat: The wireless clients successfully connect to the WRT54GX2. The WPA/WPA2 & TKIP/AES settings are correct. The clients cannot receive a dynamic IP address.
On Friday I will reset the box for 30+ seconds. I doubt this will have any effect. I reset it on Tuesday twice on Tuesday, and still have the problem.
Any help appreciated.
-WJ

Some wireless clients can't discover or connection to local wired systems

Hi,
I've just upgraded my home wireless from an NetComm NB5540 + modem to a LinkSys X3000.
Internet access works fine for all devices, but some wireless devices can't "see" my Win7 desktop system that's on a wired connections to the router.
I've tried three devices...
Galaxy Note phone (running ICS 4.0.4) can discover and connect to file shares on my desktop system without any problems.
Asus Transformer Prime tablet (running JellyBean 4.1.1) can see the router on the local network, but can't see my desktop. Even if I manually type in the IP address it can't connect to it
Likewise my old WinXP laptop can see the router but can't see or connect to any other devices.
Any suggestions welcome.
Hugh
ps. I tried connecting the NetComm router with just Wifi configured to one of the ethernet ports on the X3000, so I've got two Wifi networks running in parallel. If I connect to this second WiFi network with any of the above devices then they can all discover and connect to my desktop system on the wired connection to the X3000.

Just to test network connectivity, why don't you ping the wired client from the wireless devices that are not able access it? Do post your results so we can further analyze this scenario. By the way, when you cascaded another access point (using the NetComm router) to the X3000, was it via LAN- LAN? Was the X3000 still the DHCP server for the wireless clients?

Understanding of wireless client connection to multiple APs

Similar Messages

Maybe you are looking for