05-14-2007 10:24 AM - edited 07-03-2021 02:03 PM
Hello. Users are complaining that their drives are not being mounted with a script that automatically runs as the user logs in. This makes sense since I am using EAP-Fast authentication and the computer does not have an IP address until after the user logs in. The work around I am using is to log off and back on to force the cached script to run and that does work but it is very annoying.
Is there any work around for this issue or something I can do to help the users out?
I am using Autonomous AP 1200 with Windows 2000 and XP clients all are joined to an Active Directory infrastructure.
Thank you
05-14-2007 11:20 AM
Hi there,
the problem lays as you so rightly point at in the fact that a connection is not rearly established untill after a client logs on. A client of ours that had this problem resolved it by installing an Intel wireless card as their client software supports pre-logon profiles. How this works is that you can define and setup a profile that runs before the user logs on and hense alows logon scripts to run!
Not too sure of this can be done in Active Directory group policy but i will have a look and post back if it can be.
Hope that this helps
Mark
*Pls rate all useful posts
05-14-2007 11:29 AM
Not to sure if you are usuing the active direcotry wirless network group policy but this is an interesting document. Try using the "Computer only". When this option is selected, authentication is always performed using the computer credentials. User authentication is never performed
Cheer Mark
*Pls rate all useful posts
05-14-2007 12:18 PM
Try with machine authentication. After the computer passes the machine authentication, it get network connection before log on. It works great with us.
Hope it helps.
Zhenning
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide