10-05-2010 06:19 AM
I am fairly certain I am dealing with a Windows XP "Feature" and am hoping that someone in this community has experienced the same thing and will have an answer for me.
I am trying to figure out why Windows Remote Desktop connections to a wireless computer initially connect and then after a short time (30 seconds or so) the connection fails. I assume this is somehow related to the computer going into a locked state locally when being accessed remotely. Does this cause the Wireless NIC to shut off?
Here is the scenario.
- Wireless client (Windows XP SP3) is connected to the WLAN and functioning properly.
- Help Desk initiates a Windows Remote Desktop session to remotely administer the wireless client.
- Help Desk successfully connects to and logs into the wireless client.
- Everything appears to function normally and then after about 30 Seconds, the wireless client appears to lock up. The desktop is still displayed and the mouse pointer moves but there is no response to any action.
- after another 30 seconds or so, the remote desktop session errors saying the connection was lost.
10-15-2010 02:41 AM
Are there any values you can check inside the Aruba or what could it be?
10-15-2010 03:01 AM
" Q. Do Remote Desktop connections work to Windows wireless clients that use 802.1X authentication?
A. Not at this time. All 802.1X-based wireless connections are affected, including those using EAP-TLS or PEAP-MS-CHAP v2. Connections using a static WEP key or WPA-PSK are not affected. Microsoft has addressed this issue in Windows Vista and Windows Server 2008."
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base