The subject explains it a bit. Target machine is Win 7 x64 using 802.1x authentication -- user auth, not machine auth -- on the wired connection (not wireless). When I connect using RDP from a remote machine (I tried both 7 and XP), I'm getting the Event ID 56 (The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. Client IP: aaa.bbb.ccc.ddd.) and the target machine's network connection goes down and remains in that state, making it completely unreachable ... offline. It's a problem on both parts as I can no longer reach it and the machine also can no longer reach the internet, needed for various running application. I have to physically go to the machine and disable and re-enable the network adapter to re-trigger the 802.1x re-authentication. The status of the network connection when I get to the machine is "Authentication failed". This problem appeared after I started using 802.1x authentication -- a requirement of the network provider. I found some conflicting info on RDP and 802.1x. Some official Microsoft report for XP says that RDP does not work when the target machine is using 802.1x authentication but that this has been fixed in Windows 2008 and Vista (so implicitly in 7 as well). Some say that it does not work because RDP creates another session which does not have the 802.1x credentials and that the only way to make it work is to use 802.1x machine authentication and not user authentication. I can't use machine auth as the provider only supports user auth. I did save the user credentials and enabled single sign-on, which I thought should work for any user that is logged in. Moreover, the user I'm connecting using RDP is the same user for which I set up the 802.1x credentials. The funny thing is that it works for a few brief seconds: starting the RDP session I get to see some of the windows but after 1-2 seconds it dies, bringing the target machine's network connection down with it. Any clues to fix this? Is there at least a way to trigger the target machine 802.1x re-authentication so that it does not remain offline? Many thanks in advance

Some say that it does not work because RDP creates another session which does not have the 802.1x credentials and that the only way to make it work is to use 802.1x machine authentication and not user authentication. I can't use machine auth as the provider only supports user auth. That is the fix, to use machine authentication. You will need to use another remote control software product if they are unable to do machine auth.Ketan Thakkar | Microsoft Online Community Support