Good Evening,
I wanted to share an experience with this problem. First the background:
Windows 7 Enterprise Laptop Clients 30 Per Room
10 Rooms of this setup
Each Room 2 Aruba AP 105s and 30 T460i Lenovo Laptops with the 6300 Centrino Chipset from Intel
All machines joined to a mixed 2003/2008 Active Directory Domain with about 140,000 User Objects
Controller Environment:
| Controller Model | Aruba6000-US |
| ArubaOS Version | 6.1.2.3 |
| Compiled | 2012-02-09 at 15:38:38 PST (build 32293) by p4build |
| ROM | System Bootstrap, Version CPBoot 1.2.0.0 (build 20527) 2009-01-20 18:56:10 |
| Controller Uptime | 29 days 19 hours 25 minutes 46 seconds |
| Processor | XLR 732 (revision C4) with 2017M bytes of memory. |
| Memory | 32K bytes of non-volatile configuration memory. |
| System Flash | 512M bytes of Supervisor Card System flash (model=CF 512MB). |
Two of these controller with 2 x10 Gig Connections to each core Nortel 8600 Routing Switch
GigE Connection to the Internet with 3 Way ISP Diversity
DHCP and DNS Supplied by InfoBlox Appliances
Problem:
Student power on the T460i Laptops and when the login screen comes(msgina) immediately try to login
They get "No Logon servers available" or "Cannot establish trust relationship"
Everyone immediately throws up their hands and scream this doesn't work!!!!
Technicians arrive on site and everything works no problems.
Actions Taken:
Making changes to the default machine auth role to authenticated from a special guest role.
Enabling PMKID
Increasing the 4 way radius hand shake from 1000 to 5000
Flipped back and forward between the Windows Zero Config client and the Intel Wireless client
Findings:
All of the above had absolutely nothing to do with the problem and provided no relief.
The problem with these laptops and the installed Windows 7 Image is that it takes the
integrated network adapter a full minute to come online after you are presented with the
logon screen.
Secondly, when the laptops wake up from their sleep mode or from the lid being closed and reopened
it takes almost 40 seconds for the wireless card to re-activate.
We currently have several labs in our remote centers connected to Aruba 600 controllers and they experience none of these issues.
So to that end we grabbed an ASUS USB-N13 adapter that we stock for those sites and installed the driver on the T460i.
The adapter was lit and connected before the logon screen was displayed to the user. There is no way to beat the
adapter and create this condition.
We upgraded to the driver to the 15.02 code that was release August 13, 2012 and may have shaved two seconds off of the enormous delay.
We also found that all of the T460s laptop we got at the beginning of the year did not have this same problem.
Internet Solutions:
We found this article which we may decide to implement:
I'm not sure if this solves your question or if it even is what you are asking, but it seems like your computer
is trying to logon to a domain server before the network is ready. If this is case, you might want to change
the group policy.
Go to Start -> type in "gpedit.msc" in the run/search field.
In the Local Group Policy Editor that pops up, go to "Computer Configuration" -> "Administrative
Templates" -> "System" -> "Logon" -> "Always wait for the network at computer startup and logon"
Double click the latter and set it to "enabled".
and this:
I was trying to get our computers to autologin as a domain admin user after imaging. To get this to work I
did the following
1. In the Local Group Policy Editor, go to "Computer Configuration" -> "Administrative Templates" ->
"System" -> "Logon" -> "Always wait for the network at computer startup and logon" as @bloodphilia
said
2. In the Local Group Policy Editor go to "Computer Configuration" -> "Administrative Templates" ->
"System" -> "Group Policy" -> set "Startup policy processing wait time" to 120.
For some reason the "Always wait for the network at computer startup and logon" doesn't always work, it
seems like it was just a matter of timing. About 80% of the time I would get an error of "no domain
controllers available". The added delay of the "Startup policy processing wait time" made it so the
autologin always works.
We are contemplating implementing these changes but are concerned about slowing down other machines that don't suffer this problem.
I may record a video and post it so that you can actually see the problem.
Bottom Line: The Aruba wireless system was functioning flawlessly but was the convenient target for failing to do some research and make detailed observations. Twenty years ago as a mainframe system programmer, my mentor told me to "Sit on your hands" when you've done everything and rechecked everything. We made lots of changes and opened tickets etc because we foolishly didn't take a clinical approach to diagnosing the problem.