DC unavailable during wireless logon... is this a Cisco Issue?
I understand that, using only the Windows Wireless Config, the client will only process association and authentication after the user logs on either locally or with a domain account/profile which pre-exists on the machine.
unfortunately, this doesn't happen to users who do not have profiles on the machine. if a new account tries to login, obviously, the user isn't associated and authenticated yet, therefore no ip address is leased and domain is unreacheable at this point, or anything on the network. actually, when the Press Ctrl-Alt-Del screen is displayed, the machine is not associated, authenticated and has no IP address yet.
i have seen LEAP, and before Windows can display the Login dialog, one can actually see what LEAP is doing, like association, authencation and acquiring an IP address.
For compatibility reasons, the company decided to work with PEAP only to authentication via WLC 4.1.181 to ACS 4.0. Is there a way for the Windows Wireless Config to do the same thing as what LEAP is doing, in the manner that it will handle all necessary tasks to acquire an IP address before the Windows Login dialog appear..
Re: DC unavailable during wireless logon... is this a Cisco Issu
This is not a Cisco issue. What you need is to use a 3rd party utility (Intel Pro, Access Connection, etc) that allows you to obtain a wireless network connection prior to login. Using the Windows Zero Config will not allow you to do this, because your network services does not start until your desktop loads. What type of wireless card are you using?