wireless access issue

Started by RickG, February 11, 2015, 10:09:54 AM

Previous topic - Next topic
Print
Go Down Pages1
User actions

RickG

February 11, 2015, 10:09:54 AM
We have a classroom that has about 30 machines. All connect wireless. when the machines login, they hang and take anywhere from 5 to 20 minutes to complete the logon process. During  testing we found that the machines are hanging on the windows profile service. All are win 7 and use Extreme wireless to connect. The big caveat is the card drivers are Winxp. Wired computers work fine.

Networking is blaming the windows profile. Desktop support is blaming the network. There are three access points in the room.

I am looking for ideas on what is happening and how to fix it. Wiring the room is not an option...

SimonV

#1
February 11, 2015, 10:34:23 AM
Are you using Roaming Profiles on the PCs?

deanwebb

#2
February 11, 2015, 10:36:30 AM
How many domain controllers are involved? And do the wireless clients have full access to all the domain controllers? If not, there's a funny thing in Win7 about how it can try to contact ALL the DCs and then time out if one can't respond right away with a "No, I *don't* handle your request" or a "Why, yes, I *do* handle your request."
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

SimonV

#3
February 11, 2015, 10:41:11 AM
Quote from: deanwebb on February 11, 2015, 10:36:30 AM
If not, there's a funny thing in Win7 about how it can try to contact ALL the DCs and then time out if one can't respond right away with a "No, I *don't* handle your request" or a "Why, yes, I *do* handle your request."

This. Make sure your wireless subnet is included in the AD Sites and Services!

deanwebb

#4
February 11, 2015, 11:26:32 AM
I've even seen that happen *with* the subnet defined in AD Sites and Services. There are some other settings Win7 uses that were changed from WinXP that make it behave the way it does, with concomitant needs to tweak AD to keep that from happening.
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

RickG

#5
February 11, 2015, 01:50:16 PM
I am going to check the ad sites and services, we are using a mandatory profile, not roaming. similar but not quite the same. this is to keep the kiddies from changing the systems.

RickG

#6
February 11, 2015, 01:56:32 PM Last Edit: February 11, 2015, 02:00:32 PM by RickG
we had a 10.0.0.0/8 for one of the entries, it should have covered the network but I added a network for the actual wireless networks.

Otanx

#7
February 11, 2015, 03:03:39 PM
A few other things to check.

1. Are all the clients booting and logging in at the same time? It could overload the wireless. Try just one with all the others turned off, and see if the problem persists.
2. Can you try a different wireless card that has updated drivers? If the problem persists with different wifi cards, and does not happen when wired you have pretty much eliminated the client.

-Otanx
Print
Go Up Pages1
User actions