RE: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
Ah... how I pine for fat APs on certain days:) Heh, yeah until you have to reconfigure 100 of them to expand a subnet size ;) I still have a handful of fat 1200s floating around in production to remind me how wonderful centrally managed Wireless really is - despite some of its developmental hiccups :) But that's quite easy to solve: put all your AP's in a database and make scripted config changes using SNMP... we manage over 800 fat AP's that way, but the method would scale to thousands :-) We'll probably move to centralized within a year, but only because of the L3 mobility it offers (and we need that after a redesign of our wired network). Best regards, Jeroen van Ingen ICT Service Centre University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands [EMAIL PROTECTED]; http://www.utwente.nl/icts ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
On Nov 5, 2008, at 2:31 AM, Jeroen van Ingen wrote: But that's quite easy to solve: put all your AP's in a database and make scripted config changes using SNMP... we manage over 800 fat AP's that way, but the method would scale to thousands :-) This is basically what we're doing to manage 2,300 fat AP's. We'll probably move to centralized within a year, but only because of the L3 mobility it offers ditto here, too. Dale ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
Hi Jim- Last Friday, on our test/hot-spare controllers, I enabled Secure Mobility Tunneling and rebooted the controllers. Problem went away. Over the weekend, I did this to our production controllers- again, all is well. But then... as I read the notes, the feature to me makes no sense at all for our topology- all controllers and APs managed on same L2 space, all affected users in a single VLAN that has only one L3 head-end. So, for spite I removed the feature this morning on our test/hot-spare controllers- and all is still well. I believe that in our case, the controllers needed to be rebooted. There is a Cisco bug that may explain this for us based on our versions that we came from and went to, but it waited months to reveal itself- that's the zinger that I can't quite rationalize. Ah... how I pine for fat APs on certain days:) Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Jim Galiardi Sent: Monday, November 03, 2008 1:03 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Interesting thread. I've only recently been made aware of similar issue on our WLAN that may have been occurring since the start of fall quarter but took a few weeks to filter through to me from our helpdesk and NOC. This also seems new to us and we've made no configuration changes since winter quarter of last year. In our case DHCP transactions seem to occur normally according to DHCP logs. Requests are being received And ACKs returned. The client seems to be receiving the ACKs as they maintain the same IP address being issued during a release/renew. However, as mentioned in other threads the client cannot ping anything on the network but itself. However, in many of the reports I've received and some of the duplication we've been able to produce, a reset of the NIC or even full reboot of the client does not alleviate the issue. Seems only moving to a different controller alleviates the issue. What is interesting, is most of the recent talk has been focused on Cisco sites, but in our case we are an Aruba shop. The one commonality may be mobility as we also run a large mobility domain. This may be just coincidence, but the symptoms sounded so eerily familiar, I thought I would post our experiences to date. After a significant amount of problem replication and troubleshooting last week, I finally opened a case with Aruba TAC on this which is currently being worked. We'll see what they can come up with. Regarding the post from Bruce Johnson: When a mobile station roams from an AP joined to one controller, to an AP joined to another controller, the client may suffer a lack of data connectivity for a period as long as the configured user idle timeout. This may also be a commonality. I reduced the configured 'idle timeout' on our controllers to 300 seconds late last week which seems to have stemmed the number of complaints, but it's still too early to say for sure. Also in similar problems we've had in the past, Aruba has a similar workaround to the one Bruce mentions;' Delete the mobility members from the configuration and re-add them.' Fortunately, though we don't have to re-add them manually, it is still not a very scalable solution for clients stuck out on campus with no connectivity. ___ Jim Galiardi Network Specialist, Network Systems UW Technology University of Washington (206)616-0397 Box 354150 -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Friday, October 31, 2008 11:35 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: Windows Wireless Clients- strange behavior after recent Windows Updates? It's good to know we have our choice of bugs on this condition:) It's looking very much like the symmetric mobility tunneling that the esteemed gentleman from New Mexico mentioned- set this up on our spare controllers and tested thoroughly, we're looking much better. But we went to this version of code months ago, yet the problem started in the last week- that's the real confusion agent to me. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Johnson, Bruce T Sent: Friday, October 31, 2008 11:55 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? CSCsr40109 Bug Details http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method =3DfetchBu gDetailsbugId=3DCSCsl51486from=3Dsummary Mobility announcements not sent
RE: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
Jim, What version of Aruba code are you running? At Emory, we've experienced similar problems since our move to 3.3.1 code (currently on 3.3.1.15). We've been working with Aruba TAC and have identified a bug - bugid 27234. It relates to MobileIP where a wireless client may not be cleanly removed from the mobility table. Symptoms are strong signal level and 802.1x authentication occurs normally but user is unsuccessful in getting an IP address (self-assigned or it just keeps trying to reconnect). A user debug shows the user requesting a DHCP IP address, but the mobility process preventing it from being assigned. We've only seen a handful of users affected by this problem. The users are generally only affected in locations homed to one controller, and can connect normally at other locations homed to different controllers. The good news is that Aruba has a patch for this in 3.3.1.20 code. We are upgrading next weekend to address this problem. There are some workarounds (some drastic) that I'll let Aruba TAC tell you about to temporarily address this. - Stan Brooks - CWNA/CWSP Emory University University Technology Services 404.727.0226 AIM/Y!/Twitter: WLANstan MSN: [EMAIL PROTECTED] GoogleTalk: [EMAIL PROTECTED] -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Jim Galiardi Sent: Monday, November 03, 2008 1:03 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Interesting thread. I've only recently been made aware of similar issue on our WLAN that may have been occurring since the start of fall quarter but took a few weeks to filter through to me from our helpdesk and NOC. This also seems new to us and we've made no configuration changes since winter quarter of last year. In our case DHCP transactions seem to occur normally according to DHCP logs. Requests are being received And ACKs returned. The client seems to be receiving the ACKs as they maintain the same IP address being issued during a release/renew. However, as mentioned in other threads the client cannot ping anything on the network but itself. However, in many of the reports I've received and some of the duplication we've been able to produce, a reset of the NIC or even full reboot of the client does not alleviate the issue. Seems only moving to a different controller alleviates the issue. What is interesting, is most of the recent talk has been focused on Cisco sites, but in our case we are an Aruba shop. The one commonality may be mobility as we also run a large mobility domain. This may be just coincidence, but the symptoms sounded so eerily familiar, I thought I would post our experiences to date. After a significant amount of problem replication and troubleshooting last week, I finally opened a case with Aruba TAC on this which is currently being worked. We'll see what they can come up with. Regarding the post from Bruce Johnson: When a mobile station roams from an AP joined to one controller, to an AP joined to another controller, the client may suffer a lack of data connectivity for a period as long as the configured user idle timeout. This may also be a commonality. I reduced the configured 'idle timeout' on our controllers to 300 seconds late last week which seems to have stemmed the number of complaints, but it's still too early to say for sure. Also in similar problems we've had in the past, Aruba has a similar workaround to the one Bruce mentions;' Delete the mobility members from the configuration and re-add them.' Fortunately, though we don't have to re-add them manually, it is still not a very scalable solution for clients stuck out on campus with no connectivity. ___ Jim Galiardi Network Specialist, Network Systems UW Technology University of Washington (206)616-0397 Box 354150 -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Friday, October 31, 2008 11:35 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: Windows Wireless Clients- strange behavior after recent Windows Updates? It's good to know we have our choice of bugs on this condition:) It's looking very much like the symmetric mobility tunneling that the esteemed gentleman from New Mexico mentioned- set this up on our spare controllers and tested thoroughly, we're looking much better. But we went to this version of code months ago, yet the problem started in the last week- that's the real confusion agent to me. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Johnson, Bruce T Sent
Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
We have WiSMs 4.1.185 and we use web authentication and WPA/WPA2 enterprise. I haven't received similar complains from our users. I tested myself with a fully patched XP SP3 laptop. I tested coming out of sleep, roaming to different APs and different controllers, tested both web auth and WPA2, I didn't see any issues. Dennis Xu Network Analyst(CCS) University of Guelph 5198244120 x 56217 - Original Message - From: Lee H Badman [EMAIL PROTECTED] To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Sent: Friday, October 31, 2008 8:29:13 AM GMT -05:00 US/Canada Eastern Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? This is getting worse for us, and I think we have found that the recent Windows patches have their own baggage but are likely not the actual problem in our Cisco environment. We have an open TAC case right now, but so far no response to what is becoming a very disruptive condition. It seems that any OS is impacted (Linux, Mac, Windows) but only on our secure 802.1x network- open networks not affected- in that if you roam from one AP to another your session breaks. Seems worse on APs on different controllers, though everything is in the same mobility group. We’ve made no system changes and did not have this problem a week ago. Weird stuff- debug is so convoluted and chattey on a busy controller that it’s hard to extract any value in this case Lee Badman From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Bentley, Douglas Sent: Thursday, October 30, 2008 11:14 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Yes, Cisco for us. 2 6509E with 6 WiSMs (3x3) and 2 4404-100s in our test core. We just moved to 4.2.130. I need to perform more testing with this code in place. We are using open and WPA with web authentication as well as WPA2/AES. Douglas R. Bentley University Information Technology Systems Engineering Group cid:543522017@17092008-2BBE 727 Elmwood Avenue, Suite 132 Rochester , NY 14620 Office: (585) 275-6550 Fax: (585) 273-1013 Mailto:[EMAIL PROTECTED] www.rochester.edu/its/ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Thursday, October 30, 2008 11:06 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Cisco for you? And what version code? And only on secure WLAN or on open nets as well? Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Bentley, Douglas Sent: Thursday, October 30, 2008 9:57 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are seeing the same thing here. If anyone finds anything please post it. Douglas R. Bentley University Information Technology Systems Engineering Group cid:543522017@17092008-2BBE 727 Elmwood Avenue, Suite 132 Rochester , NY 14620 Office: (585) 275-6550 Fax: (585) 273-1013 Mailto:[EMAIL PROTECTED] www.rochester.edu/its/ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:26 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are so far finding that just changing network selection (go to another network then come back) or disconnect/reconnect, or reboot, or similar does tend to fix it. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Fruits, Brian Sent: Wednesday, October 29, 2008 12:23 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? I have had reports from one user that sound very similar to your last item. They say they can connect in one location, but when they move they have no connectivity. If they move back they are online again. I am still waiting for the user to contact me with more details about their device, have you found a fix/workaround for this? We run mostly Meru with BlueSocket and nothing special like 802.1x. Brian Fruits ITS – Network Services UNC Charlotte From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:16 PM
Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
Lee, Are you using GLBP? I recently had an issue with clients roaming from one AP to another AP on a different controller, but in the same mobility group. After a week or so of providing Cisco with logs and configs I was issued the following: Bugs CSCsv21441 and CSCsv21464 have been filed on the GLBP issue. As a work around I was instructed to use the router's actual ip address instead of the GLBP virtual address for the default gateway on the client interfaces. James Nesbitt Wireless Engineer Duke University On Oct 31, 2008, at 8:29 AM, Lee H Badman wrote: This is getting worse for us, and I think we have found that the recent Windows patches have their own baggage but are likely not the actual problem in our Cisco environment. We have an open TAC case right now, but so far no response to what is becoming a very disruptive condition. It seems that any OS is impacted (Linux, Mac, Windows) but only on our secure 802.1x network- open networks not affected- in that if you roam from one AP to another your session breaks. Seems worse on APs on different controllers, though everything is in the same mobility group. We’ve made no system changes and did not have this problem a week ago. Weird stuff- debug is so convoluted and chattey on a busy controller that it’s hard to extract any value in this case Lee Badman From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU ] On Behalf Of Bentley, Douglas Sent: Thursday, October 30, 2008 11:14 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Yes, Cisco for us. 2 6509E with 6 WiSMs (3x3) and 2 4404-100s in our test core. We just moved to 4.2.130. I need to perform more testing with this code in place. We are using open and WPA with web authentication as well as WPA2/AES. Douglas R. Bentley University Information Technology Systems Engineering Group image001.jpg 727 Elmwood Avenue, Suite 132 Rochester, NY 14620 Office: (585) 275-6550 Fax:(585) 273-1013 Mailto:[EMAIL PROTECTED] www.rochester.edu/its/ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU ] On Behalf Of Lee H Badman Sent: Thursday, October 30, 2008 11:06 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Cisco for you? And what version code? And only on secure WLAN or on open nets as well? Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU ] On Behalf Of Bentley, Douglas Sent: Thursday, October 30, 2008 9:57 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are seeing the same thing here. If anyone finds anything please post it. Douglas R. Bentley University Information Technology Systems Engineering Group image001.jpg 727 Elmwood Avenue, Suite 132 Rochester, NY 14620 Office: (585) 275-6550 Fax:(585) 273-1013 Mailto:[EMAIL PROTECTED] www.rochester.edu/its/ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU ] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:26 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are so far finding that just changing network selection (go to another network then come back) or disconnect/reconnect, or reboot, or similar does tend to fix it. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU ] On Behalf Of Fruits, Brian Sent: Wednesday, October 29, 2008 12:23 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? I have had reports from one user that sound very similar to your last item. They say they can connect in one location, but when they move they have no connectivity. If they move back they are online again. I am still waiting for the user to contact me with more details about their device, have you found a fix/workaround for this? We run mostly Meru with BlueSocket and nothing special like 802.1x. Brian Fruits ITS – Network Services UNC Charlotte From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU ] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:16 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Windows
RE: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
CSCsr40109 Bug Details http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBu gDetailsbugId=CSCsl51486from=summary Mobility announcements not sent after an upgrade when wrong version Symptom: When a mobile station roams from an AP joined to one controller, to an AP joined to another controller, the client may suffer a lack of data connectivity for a period as long as the configured user idle timeout. debug mobility handoff enable output shows that, after the roam event, the WLC to which the client has roamed does not send the MobileAnnounce message to the WLC from which the client had roamed. Conditions: Multiple WLCs in the same mobility group, running 4.2.112.0. The WLCs had all been upgraded from 4.1.185.0, and then had not been rebooted again. Workaround: There are 2 workarounds for this issue, 1) Delete the mobility members from the configuration and re-add them. 2) After upgrading all WLCs to 4.2.112.0, reboot them all once more. Bruce T. Johnson | Network Engineer | Partners Healthcare Network Engineering | 617.726.9662 | Pager: 31633 | [EMAIL PROTECTED] From: The EDUCAUSE Wireless Issues Constituent Group Listserv on behalf of James Nesbitt Sent: Fri 10/31/2008 11:49 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Lee, Are you using GLBP? I recently had an issue with clients roaming from one AP to another AP on a different controller, but in the same mobility group. After a week or so of providing Cisco with logs and configs I was issued the following: Bugs CSCsv21441 and CSCsv21464 have been filed on the GLBP issue. As a work around I was instructed to use the router's actual ip address instead of the GLBP virtual address for the default gateway on the client interfaces. James Nesbitt Wireless Engineer Duke University On Oct 31, 2008, at 8:29 AM, Lee H Badman wrote: This is getting worse for us, and I think we have found that the recent Windows patches have their own baggage but are likely not the actual problem in our Cisco environment. We have an open TAC case right now, but so far no response to what is becoming a very disruptive condition. It seems that any OS is impacted (Linux, Mac, Windows) but only on our secure 802.1x network- open networks not affected- in that if you roam from one AP to another your session breaks. Seems worse on APs on different controllers, though everything is in the same mobility group. We've made no system changes and did not have this problem a week ago. Weird stuff- debug is so convoluted and chattey on a busy controller that it's hard to extract any value in this case Lee Badman From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Bentley, Douglas Sent: Thursday, October 30, 2008 11:14 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Yes, Cisco for us. 2 6509E with 6 WiSMs (3x3) and 2 4404-100s in our test core. We just moved to 4.2.130. I need to perform more testing with this code in place. We are using open and WPA with web authentication as well as WPA2/AES. Douglas R. Bentley University Information Technology Systems Engineering Group image001.jpg 727 Elmwood Avenue, Suite 132 Rochester, NY 14620 Office: (585) 275-6550 Fax:(585) 273-1013 Mailto:[EMAIL PROTECTED] www.rochester.edu/its/ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Thursday, October 30, 2008 11:06 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Cisco for you? And what version code? And only on secure WLAN or on open nets as well? Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Bentley, Douglas Sent: Thursday, October 30, 2008 9:57 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are seeing the same thing here. If anyone finds anything please post it. Douglas R. Bentley University Information Technology Systems Engineering Group image001
Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
STOP SENDING ME YOUR MINDLESS EMAILS. i DIN'T WANT THEM. I DON'T LIKE THEM. I DON'T NEED THEM. NOW A LOT OF NUTS HAVE STOLEN MY EMAIL ADDRESS FROM YOU AND I GET MORE AND MORE I DON'T WANT. gRUBB ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
We are seeing the same thing here. If anyone finds anything please post it. Douglas R. Bentley University Information Technology Systems Engineering Group 727 Elmwood Avenue, Suite 132 Rochester, NY 14620 Office: (585) 275-6550 Fax:(585) 273-1013 Mailto:[EMAIL PROTECTED] www.rochester.edu/its/ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:26 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are so far finding that just changing network selection (go to another network then come back) or disconnect/reconnect, or reboot, or similar does tend to fix it. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Fruits, Brian Sent: Wednesday, October 29, 2008 12:23 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? I have had reports from one user that sound very similar to your last item. They say they can connect in one location, but when they move they have no connectivity. If they move back they are online again. I am still waiting for the user to contact me with more details about their device, have you found a fix/workaround for this? We run mostly Meru with BlueSocket and nothing special like 802.1x. Brian Fruits ITS - Network Services UNC Charlotte From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:16 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Wondering if anyone else is feeling this effect after the recent spate of updates to XP and Vista machines- our Mac. Linux, and handheld users seem to be immune and we have had no configuration changes in our Cisco LWAPP environment of late, and the condition has also been noted on at least two staff machines in their home networks: - Machines coming out of sleep, hibernation, screen saver, etc have an IP address, but can ping nothing (but themselves) - Wireless sniffing showed one user was simply generating null data frames (likely 802.11 power save related) - Or- user is good and functional on one AP, but cannot move to an AP on another controller- same symptoms described above. Again, non-Windows users have no issue Is this ringing bells for anyone? Mostly, this seems to be very recent. I know for sure that Windows XP SP3 was not kind to one of my own PCs- after the reboot it came up with unrecognized hardware (sound card) and drastic changes were made to my wireless adapter including my 802.1x profile being changed. -Lee Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. image001.jpg
RE: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
Cisco for you? And what version code? And only on secure WLAN or on open nets as well? Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Bentley, Douglas Sent: Thursday, October 30, 2008 9:57 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are seeing the same thing here. If anyone finds anything please post it. Douglas R. Bentley University Information Technology Systems Engineering Group 727 Elmwood Avenue, Suite 132 Rochester, NY 14620 Office: (585) 275-6550 Fax:(585) 273-1013 Mailto:[EMAIL PROTECTED] www.rochester.edu/its/ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:26 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are so far finding that just changing network selection (go to another network then come back) or disconnect/reconnect, or reboot, or similar does tend to fix it. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Fruits, Brian Sent: Wednesday, October 29, 2008 12:23 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? I have had reports from one user that sound very similar to your last item. They say they can connect in one location, but when they move they have no connectivity. If they move back they are online again. I am still waiting for the user to contact me with more details about their device, have you found a fix/workaround for this? We run mostly Meru with BlueSocket and nothing special like 802.1x. Brian Fruits ITS - Network Services UNC Charlotte From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:16 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Wondering if anyone else is feeling this effect after the recent spate of updates to XP and Vista machines- our Mac. Linux, and handheld users seem to be immune and we have had no configuration changes in our Cisco LWAPP environment of late, and the condition has also been noted on at least two staff machines in their home networks: - Machines coming out of sleep, hibernation, screen saver, etc have an IP address, but can ping nothing (but themselves) - Wireless sniffing showed one user was simply generating null data frames (likely 802.11 power save related) - Or- user is good and functional on one AP, but cannot move to an AP on another controller- same symptoms described above. Again, non-Windows users have no issue Is this ringing bells for anyone? Mostly, this seems to be very recent. I know for sure that Windows XP SP3 was not kind to one of my own PCs- after the reboot it came up with unrecognized hardware (sound card) and drastic changes were made to my wireless adapter including my 802.1x profile being changed. -Lee Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. image001.jpg
RE: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
Yes, Cisco for us. 2 6509E with 6 WiSMs (3x3) and 2 4404-100s in our test core. We just moved to 4.2.130. I need to perform more testing with this code in place. We are using open and WPA with web authentication as well as WPA2/AES. Douglas R. Bentley University Information Technology Systems Engineering Group 727 Elmwood Avenue, Suite 132 Rochester, NY 14620 Office: (585) 275-6550 Fax:(585) 273-1013 Mailto:[EMAIL PROTECTED] www.rochester.edu/its/ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Thursday, October 30, 2008 11:06 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Cisco for you? And what version code? And only on secure WLAN or on open nets as well? Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Bentley, Douglas Sent: Thursday, October 30, 2008 9:57 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are seeing the same thing here. If anyone finds anything please post it. Douglas R. Bentley University Information Technology Systems Engineering Group 727 Elmwood Avenue, Suite 132 Rochester, NY 14620 Office: (585) 275-6550 Fax:(585) 273-1013 Mailto:[EMAIL PROTECTED] www.rochester.edu/its/ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:26 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are so far finding that just changing network selection (go to another network then come back) or disconnect/reconnect, or reboot, or similar does tend to fix it. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Fruits, Brian Sent: Wednesday, October 29, 2008 12:23 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? I have had reports from one user that sound very similar to your last item. They say they can connect in one location, but when they move they have no connectivity. If they move back they are online again. I am still waiting for the user to contact me with more details about their device, have you found a fix/workaround for this? We run mostly Meru with BlueSocket and nothing special like 802.1x. Brian Fruits ITS - Network Services UNC Charlotte From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:16 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Wondering if anyone else is feeling this effect after the recent spate of updates to XP and Vista machines- our Mac. Linux, and handheld users seem to be immune and we have had no configuration changes in our Cisco LWAPP environment of late, and the condition has also been noted on at least two staff machines in their home networks: - Machines coming out of sleep, hibernation, screen saver, etc have an IP address, but can ping nothing (but themselves) - Wireless sniffing showed one user was simply generating null data frames (likely 802.11 power save related) - Or- user is good and functional on one AP, but cannot move to an AP on another controller- same symptoms described above. Again, non-Windows users have no issue Is this ringing bells for anyone? Mostly, this seems to be very recent. I know for sure that Windows XP SP3 was not kind to one of my own PCs- after the reboot it came up with unrecognized hardware (sound card) and drastic changes were made to my wireless adapter including my 802.1x profile being changed. -Lee Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups
RE: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
I have had reports from one user that sound very similar to your last item. They say they can connect in one location, but when they move they have no connectivity. If they move back they are online again. I am still waiting for the user to contact me with more details about their device, have you found a fix/workaround for this? We run mostly Meru with BlueSocket and nothing special like 802.1x. Brian Fruits ITS - Network Services UNC Charlotte From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:16 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Wondering if anyone else is feeling this effect after the recent spate of updates to XP and Vista machines- our Mac. Linux, and handheld users seem to be immune and we have had no configuration changes in our Cisco LWAPP environment of late, and the condition has also been noted on at least two staff machines in their home networks: - Machines coming out of sleep, hibernation, screen saver, etc have an IP address, but can ping nothing (but themselves) - Wireless sniffing showed one user was simply generating null data frames (likely 802.11 power save related) - Or- user is good and functional on one AP, but cannot move to an AP on another controller- same symptoms described above. Again, non-Windows users have no issue Is this ringing bells for anyone? Mostly, this seems to be very recent. I know for sure that Windows XP SP3 was not kind to one of my own PCs- after the reboot it came up with unrecognized hardware (sound card) and drastic changes were made to my wireless adapter including my 802.1x profile being changed. -Lee Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
We are so far finding that just changing network selection (go to another network then come back) or disconnect/reconnect, or reboot, or similar does tend to fix it. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Fruits, Brian Sent: Wednesday, October 29, 2008 12:23 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? I have had reports from one user that sound very similar to your last item. They say they can connect in one location, but when they move they have no connectivity. If they move back they are online again. I am still waiting for the user to contact me with more details about their device, have you found a fix/workaround for this? We run mostly Meru with BlueSocket and nothing special like 802.1x. Brian Fruits ITS - Network Services UNC Charlotte From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:16 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Wondering if anyone else is feeling this effect after the recent spate of updates to XP and Vista machines- our Mac. Linux, and handheld users seem to be immune and we have had no configuration changes in our Cisco LWAPP environment of late, and the condition has also been noted on at least two staff machines in their home networks: - Machines coming out of sleep, hibernation, screen saver, etc have an IP address, but can ping nothing (but themselves) - Wireless sniffing showed one user was simply generating null data frames (likely 802.11 power save related) - Or- user is good and functional on one AP, but cannot move to an AP on another controller- same symptoms described above. Again, non-Windows users have no issue Is this ringing bells for anyone? Mostly, this seems to be very recent. I know for sure that Windows XP SP3 was not kind to one of my own PCs- after the reboot it came up with unrecognized hardware (sound card) and drastic changes were made to my wireless adapter including my 802.1x profile being changed. -Lee Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
I agree. We started seeing the problem late last week and just confirmed it was the latest windows security update that caused it. --Todd Lee H Badman wrote: We are so far finding that just changing network selection (go to another network then come back) or disconnect/reconnect, or reboot, or similar does tend to fix it. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] *On Behalf Of *Fruits, Brian *Sent:* Wednesday, October 29, 2008 12:23 PM *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU *Subject:* Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? I have had reports from one user that sound very similar to your last item. They say they can connect in one location, but when they move they have no connectivity. If they move back they are online again. I am still waiting for the user to contact me with more details about their device, have you found a fix/workaround for this? We run mostly Meru with BlueSocket and nothing special like 802.1x. Brian Fruits ITS – Network Services UNC Charlotte *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] *On Behalf Of *Lee H Badman *Sent:* Wednesday, October 29, 2008 12:16 PM *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU *Subject:* [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Wondering if anyone else is feeling this effect after the recent spate of updates to XP and Vista machines- our Mac. Linux, and handheld users seem to be immune and we have had no configuration changes in our Cisco LWAPP environment of late, and the condition has also been noted on at least two staff machines in their home networks: - Machines coming out of sleep, hibernation, screen saver, etc have an IP address, but can ping nothing (but themselves) - Wireless sniffing showed one user was simply generating null data frames (likely 802.11 power save related) - Or- user is good and functional on one AP, but cannot move to an AP on another controller- same symptoms described above. Again, non-Windows users have no issue Is this ringing bells for anyone? Mostly, this seems to be very recent. I know for sure that Windows XP SP3 was not kind to one of my own PCs- after the reboot it came up with unrecognized hardware (sound card) and drastic changes were made to my wireless adapter including my 802.1x profile being changed. -Lee Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
It sounds like a session 'idle timeout' value was exceeded while the computers were in sleep/hibernation mode. How long do your controllers remember an authenticated client while the client is no longer on the network (hibernating/sleeping)? I am not sure about the problem of coming out of screen saver mode. Unless the wireless interface shuts down while the computer is screen saving. Certainly changing networks and coming back, or logout and log back in (or reboot/login) should created a new working and valid wireless session. Cheers, John Wheeler Wireless Network Specialist Network Infrastructure Team - McGill NCS From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:26 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are so far finding that just changing network selection (go to another network then come back) or disconnect/reconnect, or reboot, or similar does tend to fix it. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Fruits, Brian Sent: Wednesday, October 29, 2008 12:23 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? I have had reports from one user that sound very similar to your last item. They say they can connect in one location, but when they move they have no connectivity. If they move back they are online again. I am still waiting for the user to contact me with more details about their device, have you found a fix/workaround for this? We run mostly Meru with BlueSocket and nothing special like 802.1x. Brian Fruits ITS - Network Services UNC Charlotte From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:16 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Wondering if anyone else is feeling this effect after the recent spate of updates to XP and Vista machines- our Mac. Linux, and handheld users seem to be immune and we have had no configuration changes in our Cisco LWAPP environment of late, and the condition has also been noted on at least two staff machines in their home networks: - Machines coming out of sleep, hibernation, screen saver, etc have an IP address, but can ping nothing (but themselves) - Wireless sniffing showed one user was simply generating null data frames (likely 802.11 power save related) - Or- user is good and functional on one AP, but cannot move to an AP on another controller- same symptoms described above. Again, non-Windows users have no issue Is this ringing bells for anyone? Mostly, this seems to be very recent. I know for sure that Windows XP SP3 was not kind to one of my own PCs- after the reboot it came up with unrecognized hardware (sound card) and drastic changes were made to my wireless adapter including my 802.1x profile being changed. -Lee Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates?
300 seconds for us (system default)- doesn't feel like this is the case (at least on our end). Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of John Wheeler, Mr. Sent: Wednesday, October 29, 2008 12:46 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? It sounds like a session 'idle timeout' value was exceeded while the computers were in sleep/hibernation mode. How long do your controllers remember an authenticated client while the client is no longer on the network (hibernating/sleeping)? I am not sure about the problem of coming out of screen saver mode. Unless the wireless interface shuts down while the computer is screen saving. Certainly changing networks and coming back, or logout and log back in (or reboot/login) should created a new working and valid wireless session. Cheers, John Wheeler Wireless Network Specialist Network Infrastructure Team - McGill NCS From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:26 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? We are so far finding that just changing network selection (go to another network then come back) or disconnect/reconnect, or reboot, or similar does tend to fix it. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Fruits, Brian Sent: Wednesday, October 29, 2008 12:23 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? I have had reports from one user that sound very similar to your last item. They say they can connect in one location, but when they move they have no connectivity. If they move back they are online again. I am still waiting for the user to contact me with more details about their device, have you found a fix/workaround for this? We run mostly Meru with BlueSocket and nothing special like 802.1x. Brian Fruits ITS - Network Services UNC Charlotte From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman Sent: Wednesday, October 29, 2008 12:16 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Windows Wireless Clients- strange behavior after recent Windows Updates? Wondering if anyone else is feeling this effect after the recent spate of updates to XP and Vista machines- our Mac. Linux, and handheld users seem to be immune and we have had no configuration changes in our Cisco LWAPP environment of late, and the condition has also been noted on at least two staff machines in their home networks: - Machines coming out of sleep, hibernation, screen saver, etc have an IP address, but can ping nothing (but themselves) - Wireless sniffing showed one user was simply generating null data frames (likely 802.11 power save related) - Or- user is good and functional on one AP, but cannot move to an AP on another controller- same symptoms described above. Again, non-Windows users have no issue Is this ringing bells for anyone? Mostly, this seems to be very recent. I know for sure that Windows XP SP3 was not kind to one of my own PCs- after the reboot it came up with unrecognized hardware (sound card) and drastic changes were made to my wireless adapter including my 802.1x profile being changed. -Lee Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
