About Wraeth_

Wraeth_ · ‎01-03-2012

Hi all, I've found a couple of post relating to this issue but I'm not sure about the version of Windows used in the "windows 2008 and microsoft native agent issue" post. 'Rabbit' responded in that post with the following: In addition to allowing nt4 crypto, you will have also have to configure the DC to send LM &NTLM responses as it has been disabled by default in Server 2008 and our Samba code requires it. I was fairly sure that I got this working about a year ago in staging, but now that I need to get it happening in production I can't remember how! I'm using an IC4000 with 4.0R3 and trying to get the native Win7 and other 802.1x supplicants to authenticate using MS-CHAP-V2. The system is completely functional the second I point it to a 2003 server. Is the note above what I'm after?

Wraeth_ · ‎11-30-2010

Not that many will be interested, but we've decided to go with the native supplicant on Win 7 due to awful roaming performance (8 - 12 seconds when using auto-scan lists) and poor integration (won't log in to domain, can't customize). Reasons for native supplicant are: roams in under a second, logs into domain, will fall back to other networks if primary SSID isn't found, users can add a home network without a user doc, and looks a lot better... Problems are: no heartbeat so sessions stay open, no host checking (though not relevant for this deployment), windows supplicant seems to need max sessions of at least two to authenticate in the first place and to roam :/... fyi I'm using 4.0R3...

Wraeth_ · ‎07-19-2010

Yep. That's what I meant! The WLAN in question uses WPA2/AES only, with 802.1x auth key management. Session resumption is already enabled. I've got 1142 APs which support 802.11i... Does the OAC have issues with non-broadcast SSIDs?

Wraeth_ · ‎07-18-2010

Hi all, I was wondering if anyone here has had much experience with using the Odyssey client in a wireless environment that uses 802.1x authentication. Particularly anyone using preemt and/or autoscan lists. I have deployed a system using 5500 Cisco WLC with about thirty five 1142 LAPs that authenticate clients against an IC that returns VLAN assignements based on AD groups. I'm using pre-login authentication using OAC on Win7. Autoscan lists are being used too due to a multicampus setup. All of this works really well (except for the fact that I can't get windows to try the domain when using the OAC credential provider :@) and the user ends up on the right VLAN with no addressing issues - sessions are effectively ended after heartbeat loss too! What I want to know is if anyone has any tips to speed up roaming using OAC? With 802.1x it seems to take around 10 seconds which isn't an issue when sitting in the one spot but for a user who's moving around you can see that this would be quite a frustrating problem... When I use my mac book with the OS X supplicant I usually only loose 2 or 3 pings during a roam. When I use a Win7 machine with OAC I loose 8-10 which just the one WLAN selected, and 8-15 with the preemt/autoscan list. Anyone have any tips?

Wraeth_ · ‎07-04-2010

Still battling with the login issue... To explain again: - User clicks on Odyssey tile and enters correct credentials without domain ("user", "password") - Odyssey login successful, connection open - Windows login fails with result "Incorrect username or password" (suggesting local login, yes?) - User re-enters correct credentials with domain ("domain\user", "password") - Odyssey login successful, connection open - Windows login succeeds This is a really silly problem - I can't believe that this hasn't come up before? In short, is there away, either on the OAC or windows end to get the login to use the domain without the decoration?? Our users really are far too stupid to type in the domain...

Wraeth_ · ‎06-23-2010

My problem is actually that the OAC login works but the windows7 machine tries to login to the local computer rather than the domain... Anyone from Juniper on the OAC Login tile and text customisation??

Wraeth_ · ‎06-18-2010

...anyone?? Also, is anyone aware of a way to have the "Odyssey" login prepend the Client's domain to a login on Win7? I know users can type it but they're too stupid to trust with such a task...

Wraeth_ · ‎06-17-2010

Hi all, Might be a stupid question, but is it possible to modify the login tile(picture)/text for the Odyssey login on Windows 7?

EAP-PEAP/TTLS and MSCHAPV2 with Windows 2008 R2

Re: OAC GINA with Windows 7

Re: 802.1x on Wireless with OAC: roaming

802.1x on Wireless with OAC: roaming

Re: OAC GINA with Windows 7

Re: OAC GINA with Windows 7

Re: OAC GINA with Windows 7

OAC GINA with Windows 7