We experienced this identical symptom with a computer this past Thursday in 416 Ag Hall. Believing we had a new computer with a faulty wifi network card we
returned the machine and acquired a replacement and did not see the issue on the identical replacement machine.
Brian Hoort
College of Agriculture and Natural Resources
Technology Services Helpdesk
Michigan State University
Helpline: (517) 355-3776
http://support.anr.msu.edu
From: Kevin Grattan [mailto:[log in to unmask]]
Sent: Friday, October 19, 2012 10:56 AM
To: [log in to unmask]
Subject: Re: [MSUNAG] [[log in to unmask]: Re: [MSUNAG] MSUNet problems in 271 Bessey]
There are a number of things that could be causing these symptoms. Please call or email and let us know the exact location of the problem and the MAC address of the systems and we will come by and check things out.
The wireless network in the areas mentioned below all have Meru access points. Meru differs from traditional wireless networks in that it is designed to use a single channel and broadcast at full power. The access points are supposed
to coordinate traffic between one another in an effort to improve efficiency and reduce latency. Sometimes if there are too many access points in an area the coordination can get overwhelmed and the wireless service will be less than optimal. This generally
only happens in lecture halls or other areas where there are a large number of access points within range of each other.
Al, we can come by and look at 271 Bessey and let you know what we find.
/Kevin
----- Forwarded message from "Kwiatkowski, Nicholas" <[log in to unmask]> -----
Thread-Topic: MSUNet problems in 271 Bessey
Thread-Index: Ac2tncJe1kBTs1oSRlqzraEsi2PjeQARk30AAAWOkuQ=
Accept-Language: en-US
acceptlanguage: en-US
Date: Fri, 19 Oct 2012 09:04:36 -0400
Reply-To: "Kwiatkowski, Nicholas" <[log in to unmask]>
From: "Kwiatkowski, Nicholas" <[log in to unmask]>
Subject: Re: [MSUNAG] MSUNet problems in 271 Bessey
Comments: To: "Aldrich, Dakharai" <[log in to unmask]>
To: [log in to unmask]
I've been seeing the same issues in the Public Safety and the Henry Center for the last few weeks. In my case, the connection drops for about 30 - 60 seconds (long enough for my VPN or other connections to timeout), and then it picks back up. I don't think
I've been loosing my IP address, but I do know that the interface looses its connection to the WAP. This has happened on both of my laptops (Apple and Dell) and my smartphone (Android).
-Nick
From: Aldrich, Dakharai [[log in to unmask]]
Sent: Friday, October 19, 2012 6:32 AM
To: [log in to unmask]
Subject: Re: [MSUNAG] MSUNet problems in 271 Bessey
Al:
We’ve had the EXACT same problem over in Physical Plant for a while. If everything I’ve heard is correct, and works the way I understand it to, our issue was that there were too many access points in a close proximity, all set to blast signal at 100%, on the
same channel.
I’m not sure that will be your issue, but it’s a place for them to start.
-dak
----------------------------------------
Dak Aldrich
Michigan State University
Physical Plant Division Support
1147 Chestnut Road, Room 1
East Lansing, MI 48824
[log in to unmask]
517-432-0239
From: Al Puzzuoli [mailto:alpuzz@MSU.EDU]
Sent: Thursday, October 18, 2012 10:11 PM
To: [log in to unmask]
Subject: [MSUNAG] MSUNet problems in 271 Bessey
I have been noticing intermittent issues with MSUNet, specifically in Bessey hall. Perhaps the below will be of help to someone.
Today, I was at a meeting in 271 Bessey. Initially, the wireless worked, but I noticed several times within a 2 hour span that I had lost my internet connection. When I checked status of the connection, it showed limited or no connectivity. Disconnecting and
reconnecting would solve things for a while but eventually, the limited or no connectivity condition would return.Here are two ipconfigs, one from when things were working, and another from after they stopped. Basically, it looks like I was initially getting
an IPV4 address, but losing it after a while and falling back to an autoconfiguration address.
Windows IP Configuration
Ethernet adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::d9ce:37bd:787:815c%12
IPv4 Address. . . . . . . . . . . : 35.13.199.71
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : 35.13.192.1
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter 6TO4 Adapter:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2002:2309:7683::2309:7683
IPv6 Address. . . . . . . . . . . : 2002:230d:c747::230d:c747
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
Tunnel adapter isatap.{926740A8-3C0F-4E3B-B0C5-30C73997B61A}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{7905DFE9-FA67-4DEC-A1A3-92FE5411FEB2}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:3809:3dd5:dcf2:38b8
Link-local IPv6 Address . . . . . : fe80::3809:3dd5:dcf2:38b8%15
Default Gateway . . . . . . . . . :
Tunnel adapter isatap.{E558214F-B06A-43A9-8CCD-2DD787649BDA}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{CCE354E8-F0F0-4133-BA4C-F19F4E763D03}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
----- End forwarded message -----
Kevin Grattan
Wireless Team Leader
IT Services
305 Computer Center
517-432-7254