Wireless Connectivity on Domain

We're having a very frustrating issue on a new wireless implementation we've
setup at one of our high schools.

We have a 140 HP 6515B laptops running XP SP2 connecting to cisco access
points using WEP encryption. All the 32 access points are centerally managed
by cisco software and use one seemless SSID across all of them. The laptops
have the WEP key entered and saved to them and they've all be successfully
connected to the WAP. The Microsoft Wireless Zero client is handling all the
wireless configuration on the laptops.

The issue we have is about 75% of the time after you shut down or reboot the
laptop it fails to connect to the WAP at the login screen. You just keep
getting "No Domain Could Be Found", the same error you'd receive if your hard
wire PC was disconnected from the ethernet cable. If the user has logged in
sucesfully before it lets them in on a cached account, then it triggers the
wireless and it will connect after the cached login. The user can then log
out and anyone can log in, cached or non-cached. Its like the Wireless Zero
client isn't connecting up at the log in screen, but instead needs a user
logged in first to trigger the connection to the WAP. What really drives me
and my technicans nuts is thats not always consistent, sometimes it will work
right at bootup, but most of the time it won't. We've tried the latest
drivers and firmware for the wireless NIC also.

Is there any special configurations you have to make to enable wireless on a
laptop joined to a domain? Some setting that triggers connectivity it at the
login screen? Any suggestion would be greatly appreciated.

Thanks,

Derek

1. Are you using WEP or WPA? You mentioned WEP and the WAP.
2. If it is WPA2, Microsoft has a hotfix.

Hotfix: XP wireless doesn't work ...Assuming you use XP, Microsoft has
hotfix that may fix the problem. >> >> Many Wireless issues can be fixed by
hotfix Case 2: You can receive strong ...
http://www.chicagotech.net/netforums...c1d32 00dcb7a


3. If it is WEP, make sure you setup the wireless connect to one connection
only as below.

How to limit wireless connect to only one connectionHow to limit the machine
only connect to one secure wireless network. ... Right click the Wireless
Network Connection > choose Properties. ...
www.wifimvp.com/howto/limitoneconnection.htm

4. Also I would use WPA Enterprise for the domain network.


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"Derek Stewart" <DerekStewart@discussions.microsoft.com> wrote in message
news:3DC6498A-A3B3-4C83-8772-5067123CAC59@microsoft.com...
> We're having a very frustrating issue on a new wireless implementation
> we've
> setup at one of our high schools.
>
> We have a 140 HP 6515B laptops running XP SP2 connecting to cisco access
> points using WEP encryption. All the 32 access points are centerally
> managed
> by cisco software and use one seemless SSID across all of them. The
> laptops
> have the WEP key entered and saved to them and they've all be successfully
> connected to the WAP. The Microsoft Wireless Zero client is handling all
> the
> wireless configuration on the laptops.
>
> The issue we have is about 75% of the time after you shut down or reboot
> the
> laptop it fails to connect to the WAP at the login screen. You just keep
> getting "No Domain Could Be Found", the same error you'd receive if your
> hard
> wire PC was disconnected from the ethernet cable. If the user has logged
> in
> sucesfully before it lets them in on a cached account, then it triggers
> the
> wireless and it will connect after the cached login. The user can then
> log
> out and anyone can log in, cached or non-cached. Its like the Wireless
> Zero
> client isn't connecting up at the log in screen, but instead needs a user
> logged in first to trigger the connection to the WAP. What really drives
> me
> and my technicans nuts is thats not always consistent, sometimes it will
> work
> right at bootup, but most of the time it won't. We've tried the latest
> drivers and firmware for the wireless NIC also.
>
> Is there any special configurations you have to make to enable wireless on
> a
> laptop joined to a domain? Some setting that triggers connectivity it at
> the
> login screen? Any suggestion would be greatly appreciated.
>
> Thanks,
>
> Derek

Our network admin currently has it setup to use WEP, sorry about the
confusion with WAP, I actually meant Wireless Access Point(s) with that, not
the security standard.

I'll check out the Wireless Zero settings to see what the story is, but I'm
not sure if thats an issue because we don't have other networks available for
it to see. Just the one that its trying to talk too.

Derek

"Robert L. (MS-MVP)" wrote:

> 1. Are you using WEP or WPA? You mentioned WEP and the WAP.
> 2. If it is WPA2, Microsoft has a hotfix.
>
> Hotfix: XP wireless doesn't work ...Assuming you use XP, Microsoft has
> hotfix that may fix the problem. >> >> Many Wireless issues can be fixed by
> hotfix Case 2: You can receive strong ...
> http://www.chicagotech.net/netforums...c1d32 00dcb7a
>
>
> 3. If it is WEP, make sure you setup the wireless connect to one connection
> only as below.
>
> How to limit wireless connect to only one connectionHow to limit the machine
> only connect to one secure wireless network. ... Right click the Wireless
> Network Connection > choose Properties. ...
> www.wifimvp.com/howto/limitoneconnection.htm
>
> 4. Also I would use WPA Enterprise for the domain network.
>
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
>
>
> "Derek Stewart" <DerekStewart@discussions.microsoft.com> wrote in message
> news:3DC6498A-A3B3-4C83-8772-5067123CAC59@microsoft.com...
> > We're having a very frustrating issue on a new wireless implementation
> > we've
> > setup at one of our high schools.
> >
> > We have a 140 HP 6515B laptops running XP SP2 connecting to cisco access
> > points using WEP encryption. All the 32 access points are centerally
> > managed
> > by cisco software and use one seemless SSID across all of them. The
> > laptops
> > have the WEP key entered and saved to them and they've all be successfully
> > connected to the WAP. The Microsoft Wireless Zero client is handling all
> > the
> > wireless configuration on the laptops.
> >
> > The issue we have is about 75% of the time after you shut down or reboot
> > the
> > laptop it fails to connect to the WAP at the login screen. You just keep
> > getting "No Domain Could Be Found", the same error you'd receive if your
> > hard
> > wire PC was disconnected from the ethernet cable. If the user has logged
> > in
> > sucesfully before it lets them in on a cached account, then it triggers
> > the
> > wireless and it will connect after the cached login. The user can then
> > log
> > out and anyone can log in, cached or non-cached. Its like the Wireless
> > Zero
> > client isn't connecting up at the log in screen, but instead needs a user
> > logged in first to trigger the connection to the WAP. What really drives
> > me
> > and my technicans nuts is thats not always consistent, sometimes it will
> > work
> > right at bootup, but most of the time it won't. We've tried the latest
> > drivers and firmware for the wireless NIC also.
> >
> > Is there any special configurations you have to make to enable wireless on
> > a
> > laptop joined to a domain? Some setting that triggers connectivity it at
> > the
> > login screen? Any suggestion would be greatly appreciated.
> >
> > Thanks,
> >
> > Derek
>
>

There is a known issue with the Wireless Zero applet, in that it gets
confused when it sees multiple AP's with the same SSID. It may then start
switching randomly between them.

It may be worth seeing if there is an alternative, manufacturer's applet
for the wireless card. That might eliminate the problem.

"Derek Stewart" wrote:

> We're having a very frustrating issue on a new wireless implementation we've
> setup at one of our high schools.
>