RE: SOLUTION
- From: v-kzhao@xxxxxxxxxxxxxxxxxxxx (Ken Zhao [MSFT])
- Date: Wed, 09 Nov 2005 12:43:46 GMT
Hello Zuke,
Thank you for your reply and the detailed additional feedback on how you
were successful in resolving this issue. I believe your solution will
benefit many other users, and we really value having you as a Microsoft
customer. At this point, I would like to provide a simple summary for your
reference in the future:
Problem Description:
A domain user is not able to logon AD via wireless connection on a laptop
Resolution:
Change the setting "Let windows manage" in the Atheros wireless chip
configuration utility
If you have any other questions or concerns, please do not hesitate to
contact us. It is always our pleasure to be of assistance.
Thanks & Regards,
Ken Zhao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "zuke" <lgilmore@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <uFvs60#4FHA.3292@xxxxxxxxxxxxxxxxxxxx>
| Subject: SOLUTION
| Date: Tue, 8 Nov 2005 11:30:51 -0800
| Lines: 68
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Response
| Message-ID: <#fROwrJ5FHA.156@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.win2000.active_directory
| NNTP-Posting-Host: w160.z064002063.sjc-ca.dsl.cnc.net 64.2.63.160
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.win2000.active_directory:35536
| X-Tomcat-NG: microsoft.public.win2000.active_directory
|
| Hello,
|
| There is an option in the Atheros wireless chip config utility labled,
"Let
| windows manage..."
|
| Once I checked this, I opened the windows (WinXP SP2) wireless Networks
| config and checked the box "Use Windows to configure my wireless
settings",
| opened the windows utility, entered my WPA/AES key, and rebooted.
|
| Logons work fine now.
|
| Whoot!
| Zuke
| "zuke" <lgilmore@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
| news:uFvs60%234FHA.3292@xxxxxxxxxxxxxxxxxxxxxxx
| >I cannot log onto a AD wirelessly. I can join the computer to the domain
| >and make a computer account, unjoin the domain, and join again
wirelessly,
| >but the user cannot log on. At the logon screen the complaint is
"...domain
| >unavailable." Event viewer shows domain controller can't be found (but
I
| >can join the computer to the domain using an admin logon account that
then
| >cannot log onto the AD from this computer which I had just used to
create
| >it own account in AD over the wire). I am using an Atheros chip in a
| >Toshiba Satallite and a Linksys WRT54G with WPA/AES. Everything is
| >statically addressed (no DHCP).
| >
| > There is a thread with several posting on this issue in the newsgroup
| > public.win2000.security: with the subject "Domain unavailable for some
| > logins"
| >
| > The final post by the MVP is copied below:
| >
| > "The info shown in the reports generated for netdiag contain all the
info
| > that is included in ipconfig /all. Your reports all look great in that
the
| > domain controllers and domain clients are configured correctly and
| > communicating with each other [well at least after startup] . I believe
| > the problem is your wireless network. What happens is that wireless
| > network
| > cards often do not initialize fast enough at startup to have network
| > connectivity and contact a domain controller. One solution to fix the
| > problem is to have the users that need to logon to the computer do so
when
| > it is connected to the network by cable. That should create a cached
logon
| > for that user and by default a domain computer can store 10 cached
logons.
| > This behavior is a security option controlled in Local Security Policy
| > under
| > local policies/security options - number of previous logons to cache.
Once
| > the user has a cached logon he can logon via the wireless network via
the
| > cached logon and then after the wireless network adapter initializes it
| > will
| > have network connectivity and the user will be able to use domain
| > resources.
| >
| > Beyond that you could contact the manufacturer of your wireless
equipment
| > and ask them if they have any solution which could be a driver upgrade
or
| > a
| > registry change for the wireless adapter or you may be stuck with
| > performance as is. There may be particular brand of wireless network
| > adapters that work better in an Active Directory domain environment but
I
| > can't recommend any based on my experience. You might also want to post
in
| > the Active_directory newsgroup with a topic along the lines of "wireless
| > domain user logon problems" to see if anyone there has any
recommendations
| > or experience with that problem. --- Steve"
| >
| > ANY SUGGESTIONS WOULD BE WELCOME,
| > ZUKE
| >
| >
|
|
|
.
- References:
- WireleSs domain user logon problems
- From: zuke
- SOLUTION
- From: zuke
- WireleSs domain user logon problems
- Prev by Date: RE: Corrupt Profiles lead to nearly empty desktops, Win2k3 & XPSP1
- Next by Date: Domain not available to users
- Previous by thread: SOLUTION
- Next by thread: Accessing domain printer from non-domain computer
- Index(es):
Relevant Pages
|
