Archived from groups: microsoft.public.windows.networking.wireless (More info?)
I have been experiencing a number ofproblems on Windows XP with
various wirelesss solutions where the connection is lost periodically
and a key absent message is displayed. The only to reset the
connection is to remove or diale the card and start again.
I have run all the updates recommended by a number of wireless sites
including Micrsoft's and have even tried using the various release
candidates for sp2. In addition I have upgraded my network card and
access point drivers/firmware to the latest verison.
The problem appears to be worse with 802.11g clients and initial tests
indicate that disavling qos resolves this problem.
Does anyone know if this is a known problem with qos given that the
802.11e standard has not yet been ratified and therefore presumably is
either not implemented in the microsoft configuration utily or is
partially implemented causing problem with the interaction of the
miniport schedular? or is it something more fundamental to do with
the network card drivers compatability with the winsock2 and gqos
api's?
Something else I have been thinking of is, is there a problem with
802.1p proritisation which is causing a problem with the rekeying
mechanism of wpa?
Sorry for the disjointed comments but I haven't been able to find any
definative answer (been escalated to the highest level within one
vendor in an attemot to determine the problem) to this one so anyone
with any ideas please reply.
Best regards
Chris
I have been experiencing a number ofproblems on Windows XP with
various wirelesss solutions where the connection is lost periodically
and a key absent message is displayed. The only to reset the
connection is to remove or diale the card and start again.
I have run all the updates recommended by a number of wireless sites
including Micrsoft's and have even tried using the various release
candidates for sp2. In addition I have upgraded my network card and
access point drivers/firmware to the latest verison.
The problem appears to be worse with 802.11g clients and initial tests
indicate that disavling qos resolves this problem.
Does anyone know if this is a known problem with qos given that the
802.11e standard has not yet been ratified and therefore presumably is
either not implemented in the microsoft configuration utily or is
partially implemented causing problem with the interaction of the
miniport schedular? or is it something more fundamental to do with
the network card drivers compatability with the winsock2 and gqos
api's?
Something else I have been thinking of is, is there a problem with
802.1p proritisation which is causing a problem with the rekeying
mechanism of wpa?
Sorry for the disjointed comments but I haven't been able to find any
definative answer (been escalated to the highest level within one
vendor in an attemot to determine the problem) to this one so anyone
with any ideas please reply.
Best regards
Chris