Anonymous_User Absent Member.
Absent Member.
848 views

Slow wireless authentication

Our school is using Netware 6.5 sp6 with Windows XP sp2 Dell notebooks
running client version 4.91 sp2 with the latest Dell updates. We only have
IP bound to the NICs, no IPX. When the notebooks are wired, authentication
and drive mapping is very fast. But when these same notebooks go wireless
(connecting to Cisco Aironet 1100 series with latest firmware) the whole log
in procedure can take up to 5 minutes.

The frustrating thing is, it is not consistent. The same laptop connecting
to the same AP can take 20 seconds one day and 5 minutes the next. We have
tried: making sure the wireless starts up before we try connecting to the
network, changing from g to b, decreasing the name resolution timeout on
the client from 10 sec to 1 sec, tried the server IP rather than the name,
set the preferred login method to NDS - nothing consistently works, the
problem still comes and goes but again - ONLY when wireless.

Any other suggestions? All of our APs (we have about 15) have the same
SSID, could that adding to the problem? The APs are using defined channels
rather than auto.


Labels (2)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Slow wireless authentication

Just for the sake of curiosity have you removed the NW client to see if that does anything? Can I assume you have the wireless network and SSID assigned and ready to go on the laptops, so it would go hunting for networks?

Also, does location make a difference? I have a neat little Targus device that tells me the stength of a wireless network.

>>> Amy<none@none.com> 5/3/2007 12:36 PM >>>

Our school is using Netware 6.5 sp6 with Windows XP sp2 Dell notebooks
running client version 4.91 sp2 with the latest Dell updates. We only have
IP bound to the NICs, no IPX. When the notebooks are wired, authentication
and drive mapping is very fast. But when these same notebooks go wireless
(connecting to Cisco Aironet 1100 series with latest firmware) the whole log
in procedure can take up to 5 minutes.

The frustrating thing is, it is not consistent. The same laptop connecting
to the same AP can take 20 seconds one day and 5 minutes the next. We have
tried: making sure the wireless starts up before we try connecting to the
network, changing from g to b, decreasing the name resolution timeout on
the client from 10 sec to 1 sec, tried the server IP rather than the name,
set the preferred login method to NDS - nothing consistently works, the
problem still comes and goes but again - ONLY when wireless.

Any other suggestions? All of our APs (we have about 15) have the same
SSID, could that adding to the problem? The APs are using defined channels
rather than auto.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Slow wireless authentication

Do you mean try using native Windows access to login? We haven't tried that.
Yes the SSID is assigned and ready to go. The wireless is in the green zone
(good to excellent connection). Location doesn't make a consistent
difference.


"Tom Miller" <TMiller@hnncsb.org> wrote in message
news:463A14CE.E13E.00F6.0@hnncsb.org...
Just for the sake of curiosity have you removed the NW client to see if that
does anything? Can I assume you have the wireless network and SSID assigned
and ready to go on the laptops, so it would go hunting for networks?

Also, does location make a difference? I have a neat little Targus device
that tells me the stength of a wireless network.

>>> Amy<none@none.com> 5/3/2007 12:36 PM >>>

Our school is using Netware 6.5 sp6 with Windows XP sp2 Dell notebooks
running client version 4.91 sp2 with the latest Dell updates. We only have
IP bound to the NICs, no IPX. When the notebooks are wired, authentication
and drive mapping is very fast. But when these same notebooks go wireless
(connecting to Cisco Aironet 1100 series with latest firmware) the whole log
in procedure can take up to 5 minutes.

The frustrating thing is, it is not consistent. The same laptop connecting
to the same AP can take 20 seconds one day and 5 minutes the next. We have
tried: making sure the wireless starts up before we try connecting to the
network, changing from g to b, decreasing the name resolution timeout on
the client from 10 sec to 1 sec, tried the server IP rather than the name,
set the preferred login method to NDS - nothing consistently works, the
problem still comes and goes but again - ONLY when wireless.

Any other suggestions? All of our APs (we have about 15) have the same
SSID, could that adding to the problem? The APs are using defined channels
rather than auto.


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.