Thursday, March 1 the college restricted network access to about 15 Apple wireless devices that were causing no end of trouble on the Batavia campus wireless network. That means we’ve barred them from the college wireless network. ;-(
There’s a known bug where some Apple portable devices do not play well with wireless networks. When you go frequently from place to place, or work at home, you won’t see that problem. In a finite environment like the college (i.e. there are a finite list of IP addresses to share among all the wireless devices) where you want to log in for a longer period of time, then the bug becomes a major issue.
This problem is getting worse due to more people using wireless — primarily on the Batavia campus. It’s not as much a problem at the campus centers, but doesn’t mean it might not happen! Right now we can manage but as wireless use increases, if Apple does not correct this problem, we may need to restrict access to the wireless on more personal devices. Sorry!
To read up on the problem in more detail, go here:
The problem *may* be corrected using this workaround:
This is our effort to get the word out that certain Apple products have this bug, that the bug may be mitigated by means of a workaround, and that if a device causes network disruption, it may be prevented from accessing College wireless services.
Another option is to update your Apple device to iOS 5. The problem still exists there but the work around is a bit simpler to implement. (The workaround for iOS 5 is on that same page!)
Wireless use is really increasing, so we think that getting out in front of this moving train is a good idea.
Well, maybe it is not. Because we would be hit by the train.
ETA: If you are having problems, you need to log a help desk call with the following information: device model, operating system version, MAC address. And it won’t be an ‘on the spot’ resolution… ::wince:: it may take time to unravel the problem.