<br><br><div><span class="gmail_quote">On 17/05/07, <b class="gmail_sendername"><a href="mailto:A.L.M.Buxey@lboro.ac.uk">A.L.M.Buxey@lboro.ac.uk</a></b> <<a href="mailto:A.L.M.Buxey@lboro.ac.uk">A.L.M.Buxey@lboro.ac.uk</a>
> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>> >I have done all these steps except number 5. Are you saying that we can
<br>> now get machine names to authenticate prior to the user actually logging<br>> in? I can get it working fine after the user has logged in. It's just<br>> getting the machine to join the wireless network before log in so that they
<br>> join the domain ok.<br><br>oh for sure! and whats more, the login doesnt hang - because the wireless is on<br>and working. it means you arent relying on cached login credentials. as a side<br>affect, the network is 'real' when the windows box starts - so all the other parts
<br>of windows works on the wireless - eg stuff you must be in the doamin for.<br>drive mappings, GPOs, SMS bits all 'just work(tm)'</blockquote><div><br>Wow, that's awesome, I read a post which said it wasn't working so I guess it's been fixed....hoo diddly rah!!!
<br>So now I just need to see why we're getting 0 length requests and mung about with the User-Name as was stated earlier. eeek! So If I have EAP-TLS working with PEAP ie, the AD users/passwords work....am I almost there?
<br>;)<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">BUT BEWARE<br><br>one thing doesnt work. microsoft, in their wisdom, decided that the machine<->AD
<br>renegotiation of AD password key CANNOT WORK OVER AN ENCRYPTED LINK.<br><br>yes. that AD password will expire. on a wired network the machine will talk<br>to the AD to gets its new key. if you are USING the key the machine knows
<br>for the login process then that key is invalid in the AD and cannot be upgraded<br>over the PEAP encrypted wifi link. - it also cant be updated on a PPTP link<br>from what I've read. the default time for this to occur is 30 days IIRC.
<br>change it on the AD to longer if you want less pain.<br><br></blockquote></div><br clear="all"><br>-- <br>Pete Savage - cbx33::silentk<br><a href="http://wiki.ubuntu.com/PeteSavage">wiki.ubuntu.com/PeteSavage</a>