Users logging via PEAP-MSChapv2

Unanswered Question
Nov 27th, 2007
User Badges:

Hi, I'm having the following issue, Users authenticated via PEAP for getting WLAN access, do not run Microsoft Active Directory Login Scripts, because when they enter their computers once they don't have network yet, and only after loading their profile they get network connectivity.

How do you circunvented this issue? how to make sure users do run the login-scripts?


Thanks

Jorge

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Richard Atkin Tue, 11/27/2007 - 16:23
User Badges:
  • Silver, 250 points or more

You need to support Machine Authentication.


Enabling Machine Authentication will allow the Machine to receive an IP address, and subsequently download domain policies (etc..) BEFORE a user even logs in.


When a user does eventually log in, your user will behave in exactly the same experience as over the wire, ie, scripts will run, profile will download, mapped drives will appear and so on...


Regards,

Richard

CHRISTOPHER KANE Fri, 11/30/2007 - 20:07
User Badges:

We apply a batch script to run once wireless connectivity is established. We're using the Intel PROSet software on our client Dell laptops. There is an option within the Wireless LAN Profiles to start an application upon connection. Profiles > 'your profile' > Properties > Advanced > Start Application. Place your batch script that executes drive mappings, etc...


-chris

charles.diebold Thu, 12/20/2007 - 08:16
User Badges:

Richard,

Question on the machine authentication. Are you referring to the option under the windows wireless profile on the laptop?


We use that but all we get is the cached login creditentials and user profiles but no login scripts run.


Is there something else I am missing?


We have had success with the Funk and Meeting house client though.


Thanks....

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode