802.1x, peap, and login scripts

[Jason Major]

has anyone implemented a 802.1x network (wireless and wired) with windows
2000 clients that will process a login script. for the life of me I cannot
find anything the will allow this. my client will log in, and authenticate
but... no login script. I've seen the odesy client from funk software, but
could not get it to work like I would expect.

I basically want the user to experience the login as if there was no 802.1x
installed, like before. login script should run and no extra steps would be
required.

any help would be appreciated.

Jason

jmajor _ bjservices.com

 

[Kevin Longley]

We use a few wireless clients and the logon scripts run as long as we wait
10-20 seconds for the wireless connection to become activated. If we logon
on to quickly, the wireless connection has not been made yet in which case
cached credentials are used.

 

[Mike Mullins]

The card vendors tend to write some useful stuff around
their hardware. The 3Com 3CRDAG675 PCI dual-band card for
example allows you to add printers, run a program etc
after connection. You could probably invoke your scripts
in there. And the 3Com client seems seems reliable!

 

[Mike Mullins]

I have set up IAS (MS RADIUS) on Windows 2003 with PEAP,
and allowed the "computer" to logon as well as the
users. I am using the latest 3Com dual-band cards. The
3Com client utility is only needed to configure the
particular WLAN you want to connet to initially. After
that no need for it. You use the Windows 2000 Wireless
Service in SP4. After that remove 3Com launcher icon
from StartUp and Desktops for All Users.

It works a treat. The "computer" logs on very quickly
(to the WLAN) at boot up. Then when you do a domain
logon the wireless LAN swiftly and transparently
authenticated the "user". When you log off Windows
the "computer" again takes over the wireless connection.

Found that allowing PEAP without checking certificates
(setting) is helpful to get things going.

End result is a completely transparent wireless LAN,
relying on your excellent password policy, bug free
Microsoft code, and not user certificates as in EAP-
TLS.