Main Nav

We just experienced an influx (or increased reporting) of issues with Win7 machines hanging on the network connection "Identifying..." delays before prompting to ask if the connected network is public / private / home. Googling the issue turns up a wide variety of assorted things :( I seem to recall this coming up shortly after the Win7 introduction and involved DHCP handling of "requests" as opposed to "discovers" and using the universal broadcast address (255.255.255.255) as opposed to subnet-local or directed unicast to the DHCP server. Or am I imagining things? If this rings any bells with anyone, please re-enlighten me as I'm trying to resolve this issue that has appeared with our VDI beta test (which is under pressure to work yesterday, not tomorrow...). Thanks in advance, Jeff ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.

Comments

Secure network? Might be slow/buggy RADIUS auth, which happens before DHCP. We just went through this on our network when our ACS servers were wiggy. Lee H. Badman Network Architect/Wireless TME Information Technology and Services (ITS) Syracuse University 315 443-3003    
On 9/28/2012 2:10 AM, Lee H Badman wrote: > Secure network? Might be slow/buggy RADIUS auth, which happens before DHCP. We just went through this on our network when our ACS servers were wiggy. This is happening primarily wired :( Jeff ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
Well- there's the problem! It's all wireless these days, that Ethernet stuff has pretty much run it's course. ________________________________________
I wish! We are doing 802.1X on wired too! :( Bruce Osborne Network Engineer IT Network Services   (434) 592-4229   LIBERTY UNIVERSITY Training Champions for Christ since 1971