[25779] in resnet
Re: Windows computer access point association
daemon@ATHENA.MIT.EDU (Glenn Sutherland)
Tue Jan 18 09:45:30 2011
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <EB210B37BD40B841BCC40156B1D70B4755AA1C@SMU-MBX1.SMUNET.SMU.CA>
Date: Tue, 18 Jan 2011 14:44:40 +0000
Reply-To: Resnet Forum <RESNET-L@listserv.nd.edu>
From: Glenn Sutherland <Glenn.Sutherland@SMU.CA>
To: RESNET-L@listserv.nd.edu
In-Reply-To: <C9547163.622B%avoelker@wcu.edu>
We had a similar problem with windows laptops using Atheros ar5007 wireless cards connecting to newer Cisco 1142 APs. The APs they could not connect to were identical to ones that the clients could connect to, but the new APs had a high octect mac address.
What I found:
--
Older Atheros drivers, for the AR5000 series chipsets, do not properly
connect to access points with a high octet MAC addresses (not beginning with
the traditional 0.) High octet MACs are becoming more common, we just happened
to notice the problem because of the newness of the (.) APs.
Upgrading Vista to driver version 7.7.x seems to fix the issue. The difficulty
is finding the updated driver. Many computer manufacturers still have older
drivers on their websites, and I can't find anything from Atheros directly.
We've found drivers, but they're from less than official sources.
--
Glenn Sutherland
Technology Analyst, ITSS, Saint Mary's University
923 Robie St. Halifax, NS
(902) 420-5545
glenn.sutherland@smu.ca
-----Original Message-----
From: Resnet Forum [mailto:RESNET-L@LISTSERV.ND.EDU] On Behalf Of Andy Voelker
Sent: January-13-11 10:14 AM
To: RESNET-L@LISTSERV.ND.EDU
Subject: Windows computer access point association
We've been having this problem on our campus lately with windows computers associating with one single access point only on our enterprise network. The network setup works flawlessly in our help desk area, but as soon as they leave the room and go down the hall it stops. Of course every time they come back it works fine.
To fix the problem I have been fairly successful running netsh resets on winsock and ipv4 and then running a Microsoft Fixit tool. That seems to work most of the time, but sometimes the problem returns.
I'm at a bit of a loss as to what is really happening here. If anyone has a clue, please clue me in.
We run a Trapeze network. I'm support personnel so I don't know the intimate details of the network, but I can have Stephen chime in if someone would like details. I have not personally seen this happen on a mac computer, but I can't guarantee that it hasn't happened.
-- Andy Voelker
Manager of Student Computing of the Technology Commons
Western Carolina University
Hunter 57A
Be sure to check out the WCU TechTips Podcast at http://www.youtube.com/WesternCarolinaU!!
--
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
