Hi Kevin, Have a look at : http://www.boyce.us/gp/gpcontent.asp?ID=39
On 2/26/08, Kevin Lundy <[EMAIL PROTECTED]> wrote: > > Thanks Clay. That seems specific to group policy and we aren't having an > issue with that. It's only logon scripts. However, I'll give it a try as > it may still work. > > Kevin > > > On Mon, Feb 25, 2008 at 5:36 PM, Walker, Clay <[EMAIL PROTECTED]> > wrote: > > > http://support.microsoft.com/kb/840669/en-us > > > > There is a regkey you can add that may help: * > > GpNetworkStartTimeoutPolicyValue* > > > > ------------------------------ > > *From:* Kevin Lundy [mailto:[EMAIL PROTECTED] > > *Sent:* Monday, February 25, 2008 12:37 PM > > *To:* NT System Admin Issues > > *Subject:* 802.1x logon processing > > > > > > We are in the process of rolling out 802.1x across our network - wired > > and wireless. We are using both machine and user certificates. We change > > vlans based on the user. So we have a logoff vlan for all company computers > > that don't have an interactive user session. So the logoff vlan has access > > to the DCs and CA to authenticate the machine and user. > > > > We've run into one minor issue. Sometimes our logon script kicks in > > before EAP and the switches have completed the vlan change. This means that > > drives and printers sometimes don't map properly as the logoff vlan doesn't > > have access to file servers. > > > > Short of putting an arbitrary wait statement in the login script, does > > anyone have any ideas on a better solution? > > > > Thanks > > Kevin > > > > > > > -- Boaz. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
