contink (4th September 2008)
I seem to remember hacking around this once, and I set a registry key that delays group policy until a connection is ready. It was a long time ago though so I don't remember what they key was off the top of my head.
I've spent the last year dealing with this issue since implementing 802.1x network wide for wired machines.
The issue is this. There is no way to fix it, there are things that help, and things that can work. There is however no permanent fix.
Windows 2000 and XP have a race condition issue where the netlogon service is started independantly from the network authentication one.
I now have computers picking up the domain on boot around 95% of the time, but only after I stopped using Microsoft DHCP server for my guest vlan.
Microsoft have a KB that says gpo etc are not supported with vlan switching.
An additional 30-40 second delay can be introduced by windows xp sulking about getting NACKs from the dhcp server if it's a windows one, I'm using a third party one for just the guests and it ignores these initial requests (xp doesn't send a discover first)
This doesn't sound too hopeful then... I was under the impression that using a RADIUS server avoided all this but it seems I was wrong... In a word... *rse!
If anyone can offer any of those suggested workarounds that sometimes work they'd be appreciated...
There are currently 1 users browsing this thread. (0 members and 1 guests)