LAP drops client connections

Hello! we have WLC 5508 (6.0.188.0) and some converted APs AIR-AP1141N-E-K9. Everything works fine except one moment:
1 of this converted APs is located beyond the office building, but it is still connected to our local network as if it was located within the office (there is a fiber channel between our cisco core switch and a switch, to which that 1 LAP is connected)
The trouble is that users can't have the normal wi-fi on that beyond LAP. I see few successful pings to the "associated" client then drops, again a little success, than long drops.
Logs from the WLC:
Feb 15 10:04:53 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:11:17.702: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
Feb 15 10:04:57 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:11:22.104: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
Feb 15 10:36:14 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:42:38.859: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:354 Invalid replay counter from client xx:xx:xx:xx:xx:xx - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
Feb 15 10:37:07 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:32.061: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M3 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
Feb 15 10:37:12 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:37.061: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
Feb 15 10:37:16 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:40.888: %DOT1X-1-INVALID_WPA_KEY_STATE: 1x_eapkey.c:1638 Received EAPOL-key message while in invalid state (0) - version 1, type 3, descriptor 2, client xx:xx:xx:xx:xx:xx
Feb 15 10:37:21 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:45.661: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
Feb 15 10:37:23 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:47.540: %DOT1X-1-INVALID_WPA_KEY_STATE: 1x_eapkey.c:1638 Received EAPOL-key message while in invalid state (0) - version 1, type 3, descriptor 2, client xx:xx:xx:xx:xx:xx
Feb 15 10:37:26 172.22.90.20 Wi-Fi_Controller: *Feb 15 10:43:50.461: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client xx:xx:xx:xx:xx:xx
What could it be? Is it possible that some noises or whatever could cause it? The building with this problematic LAP is a kind of film studio...

oh, I badly explained what I need again(((
I don't need only 2.4 Ghz now. I cited just to remind why I was doing this:
" I was making an experiment of changing Radio Policy on a WLAN for SSID, to which only Apple users are connecting. I had chosen "802.11a only", then "802.11a/g" only, but finally I left "All" as it was before. "
And now I am faced this problem :
" But now Apple devices choose only radio 802.11g or 802.11a to connect to, although they could choose 802.11n before my experiments! " Now all that devices have only 54 Mbps as a Current Tx RateSet. They need 144 Mbps, which they had before, while connecting with radio 802.11n
Any ideas?

Similar Messages

Clients seem to drop their connectivity intermittently

Hi,
We've been having an intermittent issue where clients seem to drop their connectivity intermittently. We have an SSID configured with 802.1x and user-machine authentication using MS-PEAP. ISE is currently used as the radius server,
Synopsis:
When the client drops out, it is associated to the AP at good signal strength -64dBm. All our clients are running Win7. Once the issue occurs a yellow exclamation mark appear across the system tray wireless icon and a message appears in the "Network and Sharing Center" that either says “no internet connection” AP status on the controller is associated The client can ping its default gateway, but no connectivity above layer 3 appear to be working. This behavior is extremely intermittent. The only way to restore full connectivity to the client is to hard reset the wireless adapter or switch to another SSID and go back to the problematic SSID.
Today , I've worked with the same Cisco TAC engineer for almost three hours trying to diagnose and analyze this issue. We've tried to diagnose several clients that were having this issue by running debugs on the controllers. The wireless controllers were showing the clients were still associated, yet the clients couldn't communicate with network. I ran a link-test from the controller to the affected clients and all came back with failed status.
Any idea

a link test could fail depending on the adapter and CCX. If the client can ping it's default gateway, then the issue is probably, more than likely, not the wireless. Pinging the GW proves the client is passing traffic out of the WLC and upstream. If they are not able to reach any resources you might want to look and check your CAM and arp table entries, it is entirely possible that a MAC is being spoofed, or an IP address is being stolen somewhere.
HTH,
Steve

Howto block p2p traffic of clients connected to the same ssid on different wlc

Hi all,
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' (http://www.cisco.com/en/US/docs/wireless/controller/5.2/configuration/guide/c52wlan.html#wp1209597) to isolate the clients from each other. Does anybody know if 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 (http://www.cisco.com/en/US/products/hw/wireless/ps430/products_qanda_item09186a00806a4da3.shtml):
===
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.
===
Does anybody know 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)?
Many thanks in advance,
Thorsten

Hi Sasha,Thorsten
The bug is Junked and I believe which is what you are running into with your tests:
CSCtr60787 WLC P2P Blocking Set to Forward-UpStream Doesn't Work.
Bugtoolkit : http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs
To answer your original query :
ACL is only solution to block client communication on same ssid between 2 wlcs. 5508 works better with ACLs then 44xx platform.
ARP requests will be forwarded to upstream router just like any other traffic. WLC won't proxy arp for clients on same vlan.
Gateway arp's I believe should be handled by WLC . ( Don't quote me on this but I am pretty sure it is ) ..If it was not, then how would client know about gw ?
Multicast traffic is not applicable for p2p.
Your ACL can be as simple as this for the scenario :
WLC 1 - clientvlan = 10
WLC 2 - clientvlan = 10
and you want to restrict users from wlc1-wlc1, wlc1-wlc2, wlc2-wlc2 for same vlan10.
Basically in that case the ACL should look like on both WLCs :
1. Permit statement to talk to gateway.
2. Deny to subnet.
3. Permit all.
4. If DHCP/DNS other services are on same subnet then you would need to add a permit
statement before the deny.
5. Attach the ACL to SSID or dymanic interface.
Thanks..Salil
CSCtr60787 WLC P2P Blocking Set to Forward-UpStream Doesn't Work.

Loop drops when connected wireless (NI 9191)

Hi,
I cannot figure out why a NI cDAQ 9191 chassis has connection drops when connected wireless and works
perfectly when connected thru LAN.
I wrote a little test VI to check the connection accuracy. The chassis has a NI 9375 I/O module plugged in.
A Moxa AWK3121 is used as wireles access point. What I do is check 5 digital inputs and control 3 digital outputs.
The outputs are continuously placed on/off at a different rate. I use an event loop and a main loopt that communicates
to the chassis at a loop rate of 10ms.
The chassis, laptop and Moxa A.P. are all close together on my desk. The Wifi signal is excellent.
Now, the code i written is probably not optimal.
But... If I start with connecting the chassis with a LAN cable to my laptop, Wifi Disabled, Linked Local. The communication is perfect.
No drops between the loops and the real time.
No communication errors. Runtime was 52 minutes.
Second test. Connected the chassis to the Moxa A.P. with LAN cable. Laptop connected wireless to the Moxa A.P.
Chassis still in Link Local. Ik can access the chassis in MAX. No problem.
When I run my test, I immediately see loop pauzes. After one minute there can be already a difference of 20 sec.
between calculated looptime and real time. Sometimes the active light on the chassis goes off and on.
When the active light is out, the loop is on hold. (Wich is normal as I assume the DAQ VI's are waiting for response.)
After appr.10 minutes the error -50405 "No Transfer in progress because transfer was aborted by client".
If I look at the timings there is already a difference of more then 5 minutes between the loop timing and the real time.
As last I tested with the chassis and the PC connected wireless to the Moxa A.P.
I did not get the -50405 error, but again loop drops. After 10 minutes there was a shift of 2 minutes.
Has anyone experience with wireless connections with the NI 9191 chassis?
Can I change my code? Did I mis something? (I'm a newbie to Labview)
Any help or suggestions would be appreciated.
Thanks in advance.
Frankie.
Labview 2014 SP1 (32bit) on Windows 7 Enterprise (X64)
Chassis and Moxa all updated to the latest firmware.
Solved!
Go to Solution.
Attachments:
Chassis919Tester.vi ‏51 KB
Symmetrical_Pulse_Generator.vi ‏55 KB

I am not clear on whether you are connecting the two together "in it's own little network" (which implies "router" and not "AP") or if you are connecting to the LAN through the wireless device (in which case it is entirely appropriate to refer to the wireelss device as an "AP"). Your last post about hot spots is what confused me.
But as you said, the biggest worry is the active light. Try using a different router/AP. I've seen routers overheat and reset themselves before due to inadequate heat sinking. i.e., Someone (not me, I swear!) dropped the AP and knocked the heat sink off the chip.
As for the delay, if you are indeed using the Moxa as an AP, are you sure you're connecting to your AP? If you're connected to a hotspot instead, your throughput will be at least halved - and maybe even 1/4 bandwidth if your AP happens to have connected to a different hotspot than you did. If you are using it as a router, try differnt bands or channels to see if you can get around any interference your company wireless network might be generating.
In general, conclude that wireless isn't the best way to connect test devices together.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

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!

LWAPPs Dropping Clients with Only Moderate Load

Hope someone has an answer to this problem, as it's been plaguing me for some time.
In my district, I have 11 schools running many LWAPPs and WAPs, connected to a single WLC and managed by WCS.
Only the 4 LWAPPs in the administration building experience the following issue:
When about 8-10 WiFi devices are present on one AP in the bulding (which usually happens during a meeting), all APs show a "Load Threshold Violation Error" and start dropping some clients intermittently and refusing to connect some new clients. There doesn't seem to be a pattern as to what sort of clients drop, or which ones can connect or re-connect. My WLC is on the same subnet as these LWAPPs since it is in the same building.
If I reboot the APs, this sets things back to normal for a while, but eventually the APs will show the same errors and the same connection problems occur. I have tried adding an LWAPP to our Boardroom, which is generally where users are located when the WiFi drops. For a while, this solved the problem, but it has since returned even with the additional LWAPP.
Currently, I have all four LWAPPs in this building set to AP Mode H-REAP, as I do in my other schools. I understand this is normally bad practice; when your APs are on the same subnet as your WLC, generally those APs should be set to AP Mode Local. However, in my case, Local causes more drops and connection failures than H-REAP, so H-REAP is the closest thing I have to a "solution" to the problem.
I have checked the logs on my WLC and in WCS, and do not see any error messages besides the load threshold violations. I have tried increasing client count, and adjusting interference settings, but nothing seems to help.
All LWAPPs are AIR-LAP1131G-A-K9 on IOS12.4(18a)JA2. WLC is Model 4404 on 5.2.193.0 firmware.
Any ideas? I will be glad to post logs or provide other info as needed.

The error you are referencing about load threshold is only a message. Its a paramater that says "after X users are on an AP, send the warning message". It in itself does not do anything to clients.
If you want to troubleshoot this, then you should find a client in question and reproduce this problem while on the WLC you do a "debug client "
Out of curiousity, do you have load-balancing enabled? Thats the most likely cause for when you have clients disconnecting from wireless.... If Client Load-Balancing is enabled, I'm fairly sure in WLC 5.2 code it was a fix number, instead of a sliding scale....
Again, the client debug will help you see what is happening to your clients, if the WLC is at fault.
If you see "status 17" anywhere in the debug then your clients are being load-balanced and you need to turn that off.....

Problem with Dropped Internet Connections on AE/Macbook

I have a dual band Airport Extreme connected to Comcast Cable. I use a first generation Macbook to access the airport. The problem is that I keep on getting dropped Internet connections. The signal strength is shown at the top rhs of the screen as being full strength (4 bars).
If I swap out the router for a Linksys WRT54G, running DD-WRT, the combination works perfectly without any dropped Internet connections. Also, If I connect the Linksys to the AE with the Linksys acting as a wireless client repeating the signal, then I can connect the Macbook to the Linksys again without any dropped internet connections.
There is something about the Macbook connecting directly to the AE. It happens intemittantly but probably multiple times a day and is very inconvenient. The only way to get it back is to reboot the router or stop/start the aiport on the Macbook.
I have tried just about every possible setup on the AE including splitting the 2.4 and 5Ghz radios into two separate ssid's and changing the channels. I am using the latest AE firmware. I have also taken the AE back to the Apple store and they have swapped it for a new one.
I dont get the same issues with my windows clients or my ipad (although i have experienced issues while steaming video - but I think that may be a different issue).
Any suggestions/advice would be greatly appreciated.

Use the advice in this thread to investigate the signal and noise levels that the Mac sees:
http://discussions.apple.com/thread.jspa?threadID=2347845&start=1
What you may see if an increase in noise when the connection drops.
If that doesn't show anything useful, it might help to reset the connection settings on your Mac using these steps one at a time until the problem is resolved, recognizing that, depending on your problem, not all of these steps will make sense:
1) Use the AirPort menu bar item to turn AirPort off, then on again.
2) Try to select your Wi-Fi network from the AirPort menu.
3) In the Network panel of System Preferences delete the AirPort item from the left column, then add it back.
4) In the same panel as (3), define a new location and see if you can make that work.
5) In the same panel, select the AirPort connection item, click the "Advanced" button, select the "TCP/IP" tab, then click "Renew DHCP Lease". Note that the fix this step implements may be temporary.
6) In the folder /Library/Preferences ( _not_ <yourhomefolder>/Library/Preferences), move the folder SystemConfiguration onto the Desktop, then restart your computer. See if you can now make your AirPort connection work.
These steps may not help, but they'll only take a couple of minutes to try. Before you try these, if you have any special network settings on your Mac for things like DSL credentials, note all your network settings, because the latter steps will destroy them. If you got all the way to the last step, if things don't work any worse than before, you can trash the saved SystemConfiguration folder.

SRP541W drops idle connections fast

I have installed SRP541W and found a big anoying issue with this router - it drops idle TCP connections after a couple of minutes (more than 5 but less than 20) of inactivity. Namely, this "feature" becomes apparent when using ssh connections - if nothing happens in an ssh terminal for a given time, the connection is lost and the ssh client must be reconnected. As having a lot of ssh terminals open simultaneously (and, of course, leaving some them idle for a while) is a core of my work, this behavior annoys me a lot. Does anyone know how to solve this problem?
I understand that dropping idle connection is needed to keep the NAT tables reasonably small, but dropping connections after less than 20 minutes of inactivity is just way too fast and useless. Even cheap home routers usually do not drop idle connections after many hours or days of inactivity.

Also, if I switch the Airport Express to connect to the 2.4GHz network instead, the same thing happens on that network. After a few hours, the base station stops authenticating clients on the 2.4GHz network, and only the 5GHz network works.

Dropped clients and Load threshold violation

Can someone tell me if a load threshold violation can lead to dropped clients. Is this error message just a notice or does the controller drop clients after reaching the threshold value.
Thanks
Chris

Can you do a show wlan for me and post the results.
Do you have load balance enabled ?
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

ONS 15454 MSTP Client Connection Options

Hi!
Have questions regarding client connection options to ONS 15454 MSTP. FYI, I have experience on ONS 15540 ESPx and I usually connect client to the ONS using transponder like this
ONS 15540 ESPx
Client<->transponder<->OADM<->OADM<->transponder<->client
I am new to ONS 15454 MSTP and from the reference manual I understand that the it can be configured as hub, passive oadm, anti ase etc. My questions is how does the client get connected to each of this configurations
For example, for a passive or amplified nodes the client connections would be like this
ONS 15454 MSTP
client<->transponder<->OADM<->OA<->OA<->OADM<->transponder<->client
What about hub nodes where mux/demux card are used, where does the client connect,I do understand that these cards have to be used in pairs.
As always,appreciate your expert opinions and if you can point me to a web link that would be even better. Many Thanks.

In both cases, the client (assuming it has a non-ITU output) will connect via a transponder or muxponder card. This takes the client signal and converts (with multiplexing in the muxponder case) the client signal into an ITU wavelength.
On the MSTP, the ITU port on the transponder/muxponder is then physically patched into the appropriate port on either ROADM, OADM or Mux/Demux cards.
To directly answer your question, on a hub node equipped with Mux/Demux cards, the Tx from the Transponder is connected to the Mux card, and the Rx connected to the Demux. Likewise, at the node where the wavelength is dropped (eg at an OADM site), there will be an equivalent transpoder connected to the OADM module (Tx and Rx at wavelength xyz).
The transponders/muxponders may be in the same shelf, separate shelves, or you may use a direct ITU connection from devices such as a DWDM GBIC, an SDH DWDM card or 10GE XENPAK from Catalyst 6500.
As long as you have designed the network to take the appropriate interface types into account, you should be fine.

AP periodically dropping his connection to WLC

Hello ,
I have problem with AP 1262 witch periodically lose his connection to the controller.
I have this situatuion. One WLC 5508 and two 1242 dual band controller based APs.One AP 1242 is connected to the controller through fiber link.The other AP1242 is connected to WLC through first AP on 5GHz Wireless Backhaul.First one is RootAP and second one is MeshAP.WIreless link between two APs have SNR=40dB and distance is no more than 30 metres(100 feet).Antennas used in this case is directioanl 5GHz "AIR-ANT5160NP-R" with gain 6dBi.
MeshAP have an IP and have alreaday downloaded IOS image and configuration from WLC. MeshAP is working fine when he si connected with WLC , and client can gain access two WLAN.
However the MeshAP is periodically dropping his connection to WLC.(once every 4-5 hours).
This is part of the log generated by the WLC before loosing connection with MeshAP:
*apfReceiveTask: Dec 01 10:41:08.199: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*spamApTask1: Dec 01 10:37:54.022: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:5416 Did not receive heartbeat reply; AP: 00:08:30:70:97:70
*apfReceiveTask: Dec 01 08:47:30.943: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*spamApTask1: Dec 01 08:43:56.610: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:5416 Did not receive heartbeat reply; AP: 00:08:30:70:97:70
*apfReceiveTask: Dec 01 07:28:50.498: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*spamApTask1: Dec 01 07:25:38.994: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:5416 Did not receive heartbeat reply; AP: 00:08:30:70:97:70
*apfReceiveTask: Dec 01 06:28:26.299: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*spamApTask1: Dec 01 06:25:02.186: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:5416 Did not receive heartbeat reply; AP: 00:08:30:70:97:70
*apfReceiveTask: Dec 01 00:07:47.769: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*spamApTask1: Dec 01 00:04:39.750: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:5416 Did not receive heartbeat reply; AP: 00:08:30:70:97:70
*apfReceiveTask: Nov 30 17:05:40.975: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*spamApTask1: Nov 30 17:02:23.102: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:5416 Did not receive heartbeat reply; AP: 00:08:30:70:97:70
*apfReceiveTask: Nov 30 07:08:58.755: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*spamApTask1: Nov 30 07:05:28.818: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:5416 Did not receive heartbeat reply; AP: 00:08:30:70:97:70
*apfReceiveTask: Nov 30 04:09:30.046: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*spamApTask1: Nov 30 04:06:12.370: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:5416 Did not receive heartbeat reply; AP: 00:08:30:70:97:70
*apfReceiveTask: Nov 29 19:04:58.763: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
Any help would be appreciated.Thanks in advance.

Why are you using 802.11a as a backhaul? 802.11a may have the speed but the range of the 802.11a is not good. Now you said that you are using the 5060NP-R antenna on the 1260 side, now what antenna is being used by the RootAP?

ConfigMgr Clients connection over direct access.

My test client machine is running Windows 8.1 and connecting to network through Direct Access. I am running SCCM 2012 R2 on Windows Server 2012.
Test Machine: NYWIN8
SCCM Server: SCCM01
Domain: demo.local
I would like to understand how configmgr handles clients connecting through direct access. What all functionality is available for such clients?
On my client machine is see following errors:
FSPSTATEMESSAGE.LOG
Failed in WinHttpSendRequest API, ErrorCode = 0x2ee7
[CCMHTTP] ERROR: URL=HTTP://SCCM01.demo.local/SMS_FSP/.sms_fsp, Port=80, Options=480, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED
POLICYAGENT.LOG
Policy
http://SCCM01.demo.local/SMS_MP/.sms_pol?WRC10000.SHA256:BE60C5A54E508758261E6EDAE80AB21576A214309B9E1E19EE1D5A96C4508EC4 is not available.
DATATRANSFERSERVICE.LOG
DTS job {E6FAADEE-F22E-4E89-92EE-C2D9C10C3056} BITS job {9C444FAB-FD3C-4A6B-B8A4-81DA159E4E45} failed to download source file
http://SCCM01.demo.local:80/SMS_MP/.sms_pol?WRC10000.SHA256:BE60C5A54E508758261E6EDAE80AB21576A214309B9E1E19EE1D5A96C4508EC4 to destination C:\Windows\CCM\Temp\{C9AA0DDC-BD37-442D-A00E-EE7404D47C12}.tmp with error 0x80190194
DTS job {E6FAADEE-F22E-4E89-92EE-C2D9C10C3056} BITS job {9C444FAB-FD3C-4A6B-B8A4-81DA159E4E45} partially completed 0/1 with error 0x80190194 context 5
Software Catalog Update Endpoint
Failed to open portal registry key 'Software\Policies\Microsoft\CCM'. maybe haven't been created yet. Error 0x80070002
WEDMTRACE.LOG
No CCM Identification blob
CAS.LOG
The number of discovered DPs(including Branch DP and Multicast) is 0
SMSCLIUI.LOG
Failed to set DNSSuffix value to the registry.
Are there any issues due to connecting using direct access?

When I try to deploy any software (7-ZIP or Notepad++) to this client I get following error:
The software change returned error code 0x87D00607(-2016410105).
I can deploy same software fine to other machines connecting on LAN.
Server Logs:
Portlctl
PORTALWEB's previous status was 0 (0 = Online, 1 = Failed, 4 = Undefined)
PORTALWEBs http check returned hr=0, bFailed=0
awbsctl
AWEBSVCs http check returned hr=0, bFailed=0
AWEBSVC's previous status was 0 (0 = Online, 1 = Failed, 4 = Undefined)
Client Logs:
CAS
The number of discovered DPs(including Branch DP and Multicast) is 0
CCMEVAL
Client's current MP is http://SCCM01.DEMO.local and is accessible
ClientLocation
Current AD forest name is Demo.local, domain name is Demo.local
Domain joined client is in Intranet
Rotating assigned management point, new management point [1] is: SCCM01.demo.local (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>
Assigned MP changed from <SCCM01.demo.local> to <SCCM01.demo.local>.
ContentTransferManager
No data since 11/13/2013
CTM job {F6085C09-4C39-489E-A6F6-2C268398B7F2} successfully processed download completion.
DataTransfer
DTS job {B227AB6E-6D0F-4709-B8C6-AA8B66CBBE2D} BITS job {AE61D01C-E251-45FA-8B2C-2E22DDD91016} failed to download source file
http://SCCM01.demo.local:80/SMS_MP/.sms_pol?WRC10000.SHA256:BE60C5A54E508758261E6EDAE80AB21576A214309B9E1E19EE1D5A96C4508EC4 to destination C:\Windows\CCM\Temp\{22619283-47B1-445A-9262-C1FA54AD0F64}.tmp with error 0x80190194
DTS job {B227AB6E-6D0F-4709-B8C6-AA8B66CBBE2D} BITS job {AE61D01C-E251-45FA-8B2C-2E22DDD91016} partially completed 0/1 with error 0x80190194 context 5
Filebits
BranchCache Is Not Enabled
Failed to check PeerDistribution status. NOT able to do branch cache.
FSPSTATEMESSAGE
Failed in WinHttpSendRequest API, ErrorCode = 0x2ee7
[CCMHTTP] ERROR: URL=HTTP://SCCM01.demo.local/SMS_FSP/.sms_fsp, Port=80, Options=480, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED
Successfully sent location services HTTP failure message.
InternetProxy
Failed to get proxy for url 'HTTP://SCCM01.demo.local/SMS_FSP/.sms_fsp'. Error 0x87d00215
InventoryAgent
Inventory: 9 Collection Task(s) failed.
SCCLIENT
Event maps to notification type = Application Enforcement Failed (Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager at EventWatcher_EventArrived)
SMSCLIUI
Failed to set DNSSuffix value to the registry.
IPCONFIG /ALL from CLIENT:
Windows IP Configuration
   Host Name . . . . . . . . . . . . : NYWIN8
   Primary Dns Suffix . . . . . . . : demo.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : demo.local
   System Quarantine State . . . . . : Not Restricted
Ethernet adapter vEthernet (Internal):
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
   Physical Address. . . . . . . . . : 00-15-5D-01-0B-07
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d3f:4e51:c648:7b26%26(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.123.38(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 872420701
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-EA-A9-CE-E0-DB-55-D2-5E-59
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter vEthernet (External):
   Connection-specific DNS Suffix . : home
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
   Physical Address. . . . . . . . . : 84-A6-C8-AF-03-DE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::9cb5:5132:1f47:e7c6%24(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Thursday, January 2, 2014 1:27:53 PM
   Lease Expires . . . . . . . . . . : Saturday, January 4, 2014 12:27:55 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 730113736
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-EA-A9-CE-E0-DB-55-D2-5E-59
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Local Area Connection* 3:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : 84-A6-C8-AF-03-DF
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Bluetooth Network Connection:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : 84-A6-C8-AF-03-E2
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . : home
   Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
   Physical Address. . . . . . . . . : E0-DB-55-D2-5E-59
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.home:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . : home
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter iphttpsinterface:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : iphttpsinterface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : fd64:fc00:d17b:1000:e1a7:9cc8:c3c7:d819(Preferred)
   Temporary IPv6 Address. . . . . . : fd64:fc00:d17b:1000:c598:7f17:e286:369d(Preferred)
   Link-local IPv6 Address . . . . . : fe80::e1a7:9cc8:c3c7:d819%10(Preferred)
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 369098752
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-EA-A9-CE-E0-DB-55-D2-5E-59
   NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{DC7D2C63-1506-49EC-A40F-AA4E56DE4001}:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Remote access VPN clients connected to Internet from VPN

Greetings,
I need to let remote VPN clients to connect to Internet from the same ASA VPN server
" client connects to ASA through VPN tunnel from outside interface then access Internet from the same ASA from outside interface again
thanks

you'll need to configure 'same-security-traffic permit intra-interface' on the ASA .
Also, need to setup the corresponding nat statements for your clients pool range.
i.e.
global (outside) 1 interface
nat (outside) 1 access-list anyconnectacl
where anyconnectacl is the pool for your clients:
access-list anyconnectacl permit ip 172.16.1.0 255.255.255.0 any

My i Phone drops WiFi connection after just a few minutes and wont reconnect unless I reset the network settings and reboot the phone?

My i Phone 4s has suddenly started to drop wifi connection after nealy months of near perfect connections?
To restore a wifi connection I have to reset the network settings and restart the phone, this only fixes the issues for around 2-3 mins?
Other quick fixes like switching wifi on and off/ switching to airoplane mode for a few secconds have no impact.
This is really annoying as I am using my data allowence very quickly, and as the phone is continually searching for a wifi connection the battery time has reduced dramatically.
I just wondered if any one else has the same issue, and any suggestions as to how I can fix this.
Thanks in Advance

Reboot.
Restore (from backup)
Restore (as new)
Test after each step. If one of them doesn't fix the problem, make an appointment at the genius bar.

Regarding mountain lion server: clients experience intermittent service connections. the server system log has the following error- Client handshake failed (6):113: Server not accepting client connections (any ideas???)

regarding mountain lion server: clients experience intermittent service connections. the server system log has the following error- Client handshake failed (6):113: Server not accepting client connections. any suggestions would be greatly appreciated - thank you

Hi Jason
I was getting the same behavior after Apple support had me delete some plist files to get Airplay going. I was also getting the following error:
the error occurred while processing a command of type 'writesettings' in the plug-in 'server vpn'
I went into ~/Library/Preferences/ and /Library/Preferences/ and deleted every plist contating the word server. I had to re-set up my server (meaning walk through some intial steps) but all of my settings were still there after that and everything started working again.
Just a thought, obviously try at your own risk but it worked for me.
Kellen

LAP drops client connections

Similar Messages

Maybe you are looking for