8
4
I have a Thinkpad T430s running a fresh install of Windows 10 Pro (Build 10.0.14393), and it has an issue with inbound remote desktop sessions that causes the wifi connection to be dropped as soon as the remote desktop logs in, resulting in the termination of the remote session.
Observations:
- Sometimes I can see the lock screen rendered on the remote desktop for a split second before it freezes, presumably due to wifi connection loss.
- If I'm logged in locally at the laptop, and then try to login with the same user remotely, the local login will be booted out to the lock screen. This behaviour is as I would expect.
- When the remote desktop session freezes after login, I can see on the lock screen locally that there is no wifi connection (as shown by the wifi icon). Reconnection does not occur automatically here on the lock screen.
- Wifi connection is automatically re-established after I log in locally.
- If I remove the wifi hotspot from config (either through "netsh wlan delete profile name=" or through "Forget" in the UI), add the hotspot back and connect, log in remotely without first logging out locally, then the remote session will connect successfully.
- If I reboot the laptop after doing the step described above, then the problem returns.
What I've tried:
- Updated to latest WLAN driver.
- Installed all Windows updates.
- Disabled the option to "Allow the computer to turn off this device to save power" for the WLAN device.
The user I'm trying to log in as is a local, non-domain user. Wifi hotspot is secured with WPA2-Enterprise and EAP-MSCHAPv2.
@MagicallyDelicous - I can reproduce the same behaviour starting a RDP session from another computer. There is an INFO level event in the log that says "The browser has forced an election on network \Device\NetBT_Tcpip because a master browser was stopped.", but I believe that's due to the connection drop, not the cause of it. – Shimakaze – 2017-03-10T00:44:09.620
@MagicallyDelicous - The two machines do not have the same mapped printers; however, I tried unchecking the share printer option anyway, and that did not solve the issue. This seems to be specific to this particular wifi network, as I have discovered after trying RDP successfully in other wifi networks. Possibly due to EAP-MSCHAPv2? That is the only difference I can see, but I don't know enough about wireless authentication to know if that could affect anything. – Shimakaze – 2017-03-10T17:55:48.763
Are the machines you're connecting to and from with RDP on separate subnets or making hops across routers other than the wifi connection component to talk with each other? Wonder if allowing 3389 and/or 389 TCP rules for "allowed" in any of the devices would make any difference? I assume the traffic isn't going thru any FW filters but setting up rules to bypass or proxy is another thing to at least check on potentially. – Pimp Juice IT – 2017-03-10T19:03:01.030