Cisco Wireless :: WAP4410n - Second SSID Is Seen By Clients But Cannot Connect
Nov 15, 2011
I have a WAP4410n which has been configured with a single SSID since implementation several weeks ago with no issues. I am now trying to add a second SSID and not having any success. Originally the second SSID was not being assigned a MAC address and thus not being broadcasted. After upgrading firmware to 220.127.116.11 I now see a MAC address associated with second SSID and it is being seen by clients, but they still cannot connect. I reset the AP to default settings and reconfigured from scratch but still no luck. I have two of these APs, the other one is still at FW rev 18.104.22.168 and has same issue (it does have MAC address associated with second SSID so I didn't bother upgrading firmware yet).
I have tried a few different authetication options, including disabling authentication, to no avail. Question - I do not see an IP address associated with the second SSID - is that the problem and if so, how do I fix that?
I can't configure the SSID more than one in the web UI of the WAP4410N. Except I can type the first SSID1, the rest SSID2 - 4 are grey which not allow me to type in anything. ( See attached the screen shot ) My current version is 2.02.1 and I was using IE8 under windows 7.
I have a 4410N set up on my network. I'm using 4 VLANs on my network, of which, I use my default VLAN 1, as the "public" VLAN which we use to give our clients free WiFi. I would like to have two SSIDs visible from the access point, one unsecured and connected to VLAN 1, and the other secured with WPA2 and connected to our office VLAN on which various servers and resources are available. My preference is for both SSIDs to be visible, as there is not a major security issue and as the only IT person, I do not have time to configure every computer which uses the network with the SSID, but I'll do that if I have to.
I set up the 4410N with it's first SSID using our public WiFi name and did not put any security on it. I went to the VLAN page and set it to use VLAN 1 as both the default VLAN and the VLAN for the first SSID. Then I went back to the Basic Settings page and added a second SSID and chose "Enabled". I went to the Security page and left most things as default (Wireless Isolation between SSIDs is enabled) and changed the security settings for the office SSID to WPA2-Personal. Finally I went to the VLAN page and set it's VLAN to 4.
When I go back to my computer, or from other wireless devices, I only see the public SSID, not the office. I do see on my computer (Win7 x64) an "Other Network" option, but the signal strength on that network is significatnly weaker than that of the public SSID. Also, if I try to connect to it using the office SSID name and the password I set, it doesn't connect.
Am I completely misunderstanding how multiple SSIDs are supposed to work? I am working from a lot of assumptions here.
PS I have no clue if this would affect it, but in the interest of listing all possible factors, the 4410N is powered via PoE and the switch port it is connected to is set to 802.1Q with 1-4 set as the VLANs.
After posting this I discovered that in the Wireless Status page, both SSIDs are listed, but only one (the public SSID) has a MAC listed. I assume I need to add one somewhere. Where should I do this, and what's a "safe" MAC to use that won't conflict with anything?
We just got a WAP4410n and cant seem to get multiple SSID's to show up when searching for them.Only SSID1 shows up in Kismet or any other type of Wifi detector software, is it supposed to be like this?I would imagine that it should display both SSID's
Instead of just Mynetwork1, I have tried everything i can think of to connect to the second one but nothing seems to work.
i set up the WAP4410N and it can be connected with our router. But it's not protected by our password, but once i have set the password of WAP4410N by changing the security mode to WEP, now i will prompted to password when I connect the AP, but it shows limited connectivity, I can't even access my local LAN resources at all.
I am trying to use some WAP4410N in client mode, not much luck.In one case they shouldt connect to different unsecured networks controlled by a Cisco 5508 controller.I can get connection to one of the SSID's but not very stable.One ssid can be seen if i switch from ap-mode to client and run a sitesurvey. If i after that run a site survey again the ssid is not shown.Cant get connected. A third ssid acts "normal" but the 4410 never connects.I have a forth case, WPA2 Personal, cant connect.Been trying fw 22.214.171.124 still no succesAre client mode not usefull at all ?
I have come across a new problem with our WAP4410N. I have set up multiple SSID's for various groups of people and guests at our company, the first and main SSID has set security properly at WPA2-Personal with a 63 character password. So I went ahead and setup the other 3 SSID's with the same security (just to initially get security going was planning on taking down one of them for guest account), but when I boot up my testing laptop, it shows that SSID's 2-4 have no security what-so-ever.
I have re-checked my settings in the Wireless Security tab and they are all still set with the passwords.
I am using: PID VID: WAP4410N-A V02Software Version: 126.96.36.199.
I have two WAP4410N. One of he accesspoints is connected to our wired LAN, called by now AP1. The other accesspoint is connected to the first accesspoint by WDS (Client mode) called now by AP2. I have upgraded both accesspoints to firmware 188.8.131.52. Both accesspoints are set to the same SSID and channel (6) and are set to mixed mode (B/G/N). After I two weeks they started to fail. When I connect to AP1 I don't reveive an IP-address of our DHCP server from our LAN. I'm able to connect to AP1 from our LAN. When I SSH to the box and I do an dmesg command, I see the following messages:
Suddenly after more than a year of running fine, my wap seems to be giving all clients a bad DNS suffix which of course breaks DNS resolution internally (no problem with internet resolution). I assume it's a wap problem since all of my wired clients receive the correct suffix. I'm using a RVS4000 router if that makes any difference.
I just got a WAP321 to replace a very frustrating WAP4410, what is the the SNMP OID to obtain associated wireless clients for each of the SSIDs ? I'd be happy with any OID for client numbers so total clients associated will be fine.
I use two wlc 4400 (4.2.x version) with a mobility domain and one ssid, both wlc are connected to a cisco l2 switch infrastructure. On the wlc I use the p2p blocking action 'drop' [URL] to isolate the clients from each other. Does only unicast traffic is blocked or also multicast and broadcast traffic like arp requests?Concerning blocking p2p traffic of clients connected to the same ssid but different controllers I found the following statement in the LAP FAQs [URL]
Q. In autonomous APs, Public Secure Packet Forwarding (PSPF) is used to avoid client devices associated to this AP from inadvertently sharing files with other client devices on the wireless network. Is there any equivalent feature in Lightweight APs?
A. The feature or the mode that performs the similar function of PSPF in lightweight architecture is called peer-to-peer blocking mode. Peer-to-peer blocking mode is actually available with the controllers that manage the LAP. If this mode is disabled on the controller (which is the default setting), it allows the wireless clients to communicate with each other through the controller. If the mode is enabled, it blocks the communication between clients through the controller. It only works among the APs that have joined to the same controller. When enabled, this mode does not block wireless clients terminated on one controller from the ability to get to wireless clients terminated on a different controller, even in the same mobility group.
what's the best practise to prevent this inter wlc client traffic? I already read about using acls on the wlc dynamic interfaces, or private vlans on the l2 switch vlans where the dynamic interfaces are connected to. Is it allowed to completely isolate the wlc from each other on these dynamic interfaces with acls or private vlans or do the wlc need to see each other on this interfaces (e.g. heart beat)?
My controller is vWLC installed in ESXi which has to vNet Cards configured with all vlans(4095), then it is connected to a 3560 switch with trunk. The configuration of the switch interface is as belows: The SSID is BYOD and I can connect the SSID and get the IP address such as 10.10.10.118/24, but for now, i cannot ping 10.10.10.1, but i can ping 10.10.10.90.
Region : Others Model : TL-WR941ND Hardware Version : V3 Firmware Version : 3.13.9 Build 120201 Rel.54965n
We are trying to use a TL-WR941ND purchased about a month ago, but it keeps hanging, usually within a day or so of operation.To be clear: by "hanging" I mean the device stops providing wireless services (its SSID is no longer visible in WiFi clients) and becomes nonresponsive to pings or control access attempts (via settings web page) from the internal network connections.The device is used in a very simple scenario, where it's being employed as a simple access point, not as a router. As such, the device's configuration is as follows:
* WAN interface is configured with a dummy static IP (10.10.10.10/24) with gateway and DNS set to the internal IP address of the actual routing device connected to the external world. * LAN interface is configured with an IP address inside the actual internal IP subnet (192.168.1.0/24). * DHCP is also disabled as this service is already provided. * Wireless settings: radio enabled, SSID broadcast enabled, WDS disabled, 11bgn mixed mode, auto channel width, max TX rate, channel 7 (manually set). Using WPA-PSK security.
Rest of the settings are unchanged from their default values, as the device isn't being used as an IP router by any client - just as a WiFi/Ethernet layer 2 bridge. We're using what appears to be TP-Link's latest stock firmware for the device.The settings described above appear to provide the connectivity required by the WiFi clients. However, the device continuously hangs within a day or so of operation, requiring someone to physically attend to the device and cold-restarting it (disconnecting it from power and reconnecting it) to regain an operational state.
After performing a cold restart, the system log shows nothing beyond the startup entries: "System started" entry followed by security info entries regarding enabled protocols. Then the device appears to work well for a while, until it hangs again, forcing again someone to attend to the device, etc.
I currently have 1 AP connected to the router via copper. The AP to AP link is over 802.11. I have attached a diagram reflecting the current topology.
The AP-to-AP link will come up utilizing B/G/N mixed mode; however, the connection is basically unusable. About 30% of the traffic is dropped, while the packets that do make it have a consistently volatile latency, anywhere from 15 to 1500 ms. I have had success using G-only and B/G mixed. The link is stable (I have had the best results with B/G). The problem is, I didn't buy the 2nd 4410N to run the G protocol. I would like to connect the APs running either B/G/N (hopefully negotiating to N) or N only. I am wondering if there is a certain configuration I can utilize (perhaps using WDS repeater or bridge versus Wireless Client/Repeater?), or a firmware upgrade set for release that can make this happen for me.
I just purchased a WAP4410N yesterday and connected it to the switch. I can see the WAP4410N, can connect to it, but cannot connect to the internet. I thought this was enabled out of box. What do i need to do in order to activate internet connectivity?
I am having 3 cisco wap4410n devices. i want to use them only in my home. i dont want to connect to internet. i want these devices only for intranet (only LAN) purpose. Means to transfer audio, video, songs through these devices. then how i will connect these devices in order to connect all the computers to each other ??
I have 4 pcs on my WAP. 3 are Win 7, one is Win XP. None of these PC's can see each other to create a Home group. After spending several hours with tech support with ESET (security s/w), we determined the following:
My WAP4410N is wired to my router. The router is IPv4. Apparently the WAP4410N has IPv6 capability by default and is using this to assign all my PC's.
I was not able to setup a Home group on my Windows7 computers as a result of this because they cannot see each other if they are all on the WAP. If I plug a computer directly into my router, I can get that PC seeing just one of the 2 on the WAP.
The ESET security expert advised me to change the settings of the WAP to IPv4 only. The WAP's IP address is showing up as default 192.168.1.245 on an IP scanner but we cannot connect to it on any computer. I've tried while being on the same WAP network and I've tried going through the router but neither can see this IP address.
Recently several customers have brought in their new Nook Color devices attempting to connect to our Wireless Hotspots and are not able to. We are not using any type of security (WPA/WPA2) as these are open and free hotspots for our customers. I have 40 WAP4410Ns on our network running firmware version 184.108.40.206.
After some testing it appears that it's related to WPS. I was able to connect the Nook Color to our test WAP using WPA/WPA2 and entering the Pre-shared key. However, if I turn off security the Nook Color will no longer connect.
I'm trying to setup 2 VLAN's 1 for Native Traffic on my Corp network and another VLAN for Guest Wireless traffic. I have attached the Config from my Cisco AP1231 and my Cisco 3750. I have the AP plugged into port 24 on my switch. I seem to have the VLAN's working fine. I can get the AP1231 to broadcast both SSID's and the very first time i can connect everything seems to work fine. after i power down my switch and AP i cannot connect to either SSID. I get the message Not Connected.
I have my all my computers, printers setup with a wireless network with dsl modem connected to linksys wireless router. I just signed up with comcast with another wireless router. I do not want to reconfigure all the laptops and printers with the new comcast wireless SSID. Is there a way I can connect the linksys router with existing SSID with the comcast router and using the internet speed of comcast. (note. will disconnect service with dsl)
I just purchased a WAP 321 and followed the setup wizard. Its powered by a poe switch. The issue I have is no clients can connect to it. I updated the firmware. I reset to factory and tried setting it up manually till no one can connect. I dont understand what im doing wrong here. Unless its a bad unit. I will have about 10 to 15 clients connecting to it. Its the only ap in the building.
I would like to connect the AP541N to the RV220W and use the same SSID assigned to both throughout the office, for seemless client movement. I would like to keep the AP541N connected via the internet cable, as it will be on a switch which is on the same segment. The access point has many different configuration methods available, but the router appears to only have WDS as an option to connect the two devices. I would rather not use the WDS feature on the AP, as I want to utilize as much bandwidth available as possible, and I assume using that method I would need to remove the ethernet cable from the switch.
Is it as simple as configuring both devices with identical VLAN settings? I am preconfiguring the devices before installing them, as to minimize downtime, so would like to make sure the configuration is correct.
I have configure my AP with to SSID (11 & 12), but I cannot connect to 12. It authenticates, and while trying to acquire IP address from 12, it fails and connects me to 11 (if I have already saved the SSID connection).
The following is my AP status:Product/Model Number:AIR-AP1231G-A-K9 System Software Filename:c1200-k9w7-tar.123-8.JEE System Software Version:12.3(8)JEE Bootloader Version:12.3(2)JA4
The SSID 12 already have 4 clients connected, And I am tring to connect a 5th one (smart phone), but cannot connect to 12, instead coneected to 11. Also tried with a laptop, but cant get the IP address, and give Limited Connectivity error.
actually, i have 2wire DSL Router and i am using SSID Broadcast Disable after disable i can't connect wireless to my extra device too for example my Blackberry. but i am using another computer with wireless but i can't connect blackberry and iphone i don't have more idea in wireless stetting what can i do?
I have dell inspiron 640m with Wireless 1390 WLAN Mini-Card and it is connecting perfectly with any other routers.but i can not connect it to CISCO WAP4410N router ! i tried several times but no way.I can connect IPAD , Samsung Smart tv , Denon network radio and toshiba laptob but not Imy nspiron laptop. think my WLAN can not get th WAP4410N IP address !
In the company we have two SSIDs for corporate and guest networks respectively when I try to connect to any of the SSIDs it doesn't happen until 5 retries. The only log I get that seems to be related to it is the following:
*Jun 11 11:48:09.062: %APF-1-DISCONECT_MOBILE_DUE_TO_WLAN_SW: apf_policy.c:541 Disconnecting mobile 00:23:32:73:d7:15 due to switch of WLANs from 1(femsawl) to 2(visitas)
Here it shows a switch between SSIDs but if you just turned on an apple device and try to associate for the first time to any of the SSIDs the scenario is the same, several tries to connect.I am running a 4402 wlc with 220.127.116.11 software version.
Has anyone come accross a problem whereby an SSID becomes unavailable when selecting a Radio Policy of '802.11g Only'? The SSID is configured identically accross multiple controllers, but only works on the WISM's. The same WLAN profile on a 5508 is unavailable unless I select a Radio Policy of 'All'.
All controllers (WISM's and 5508's are running 18.104.22.168)The WLAN profile is using MAC Filtering[WPA2][Auth(802.1X)] as the security policy.