Windows 7 Thread, For random users (wireless Lan) logon.bat does not run??? How to troubleshoot! in Technical; I have been having quite frankly a s**t time trying to replace 13 windows XP wireless laptops with 16 Windows ...
For random users (wireless Lan) logon.bat does not run??? How to troubleshoot!
I have been having quite frankly a s**t time trying to replace 13 windows XP wireless laptops with 16 Windows 7 SP1 wireless laptops.
The logon times are slower and I get seemingly random laptops who refuse to run the logon.bat (from the users AD profile) one moment and then run it fine the next.
It tests I can have 5 laptops setup in my office connected to the AP on the optimum driver settings - files are copied to and from in tests at 8M/s.
If I simultaneosly logon a test student account at least 2-3 will not have the drives mapped.
Eventviewer seems to offer no clues.
Is it possible that network speed (or lack of) or network congestion can cause the logon.bat file to somehow timeout?
Interestingly when I logon as a domain admin (less GPO's applied) the drive mappings are always there...
It's the random nature of this issue that annoys me the most....and of course with fixed PC's or even using the laptops on a wired connection it all works fine.
Other than concede defeat and perhaps trying to set the mapped drives via a GPO what could I do to work-out WHY oh WHY the logon.bat does not run under certain *unknown conditions?
I'm guessing your logon scripts are stored in the NETLOGON share (where they should be)?
Do you have more than one domain controller?
I would recommend mapping network drives via GPO. It does work well in Windows 7 and it will work with XP too.
Depending what your logon script looks like, always use the FQDN where possible. As Synack, myself and others have noticed, Windows 7 and 2008 R2 seems to favour the FQDN over NETBIOS. That's not to say NETBIOS doesn't work, it's just the FQDN seems to work infinitely better.
I've had similar problems with wireless clients and it was down to old wireless access points. From reading your other posts however, your wireless system is new, so I would recommend creating a secondary SSID with no security (initially) then try maybe WEP, WPA, then the strongest WPA2 AES.
Another thing to look at is drivers. Although Windows 7 SP1 has a fab driver database, downloading the latest driver (if available) is another step to try.
We have now installed Windows 7 32 bit from the original DVD to 6 of the samsung laptops.
The generic bluetooth adapater is disabled.
The following drivers were installed:
free fall protection device
In the wLAN properties the power management allow OS to turn off device has been unticked and the Bluetooth AMP unticked - everything else at default values.
The wLAN is running WPA2 - PSK - AES on Radio 2.4G - autochannel - on ch4.
Each laptop is currently pulling down large data from the network using the wLAN card.
The speed reported by each laptop during the copy process is:
Does this seem low? or is this acceptable throughput for 6 laptops connected to a single N-band AP?
LAN Port Status on the AP
2 eth2 None Up Up 1000Mbps full 10/100/1000 PoE
Other details from the AP
Wireless Mode: 11ng -- Operates with 802.11n, 802.11g and 802.11b devices in 2.4 Ghz spectrum only
Channel: Channel 4 [SmartSelect]
Channel Width: 20 Mhz
Country Code: GB
These are client details as reported by the AP for one of the laptops:
Good Packets: 1733086 (1801.0/sec)
Number of Retries: 948473 (291.0/sec)
Physical Layer Data Rate: 130.0 Mbps
Throughput Estimate: 98.2 Mbps
Packet Error Rate: 0 %
Estimated SNR: 11 dB
Good Packets: 937746 (999.0/sec)
Discards by CRC Error: 50099 (7.0/sec)
Anyone got any comments to make?
Does it look good?
Is it not going to get any better?
Yep - the AP was on smartselect on ch7 - apparently it's been learing the ch with the least interference - although we have no other nearby AP's etc.
I've manually set to ch1 and the transfer rates are 20KB/second - well they are before the \\server\share becomes unaccessible...
Just racking my brains for random Wireless issues I've had in the past.
Are both the APs and the wireless cards configured to Open authentication not shared.
Also try windows config or the 3rd party config utilities.
One test I do when setting up is ping the laptop continuously from my desktop and reboot it to see at what point the laptop regains network connectivity. Our laptops here take up to 30 seconds from standby to regain connectivity. I believe the wait for network GPO helps with these sort of issues.