I'm having trouble getting a new user connected to one of our servers via RDP. I can't account for any security-policy settings on the new user's laptop; so the problem could be there. However, in order to understand where the problem might be, I have to understand why I see all these different scenarios, when the RDP session DOES work. Please refer to screenshots. In accessing different servers, I see different authentication scenarios:
Sometimes my session goes A-B-Desktop (auth on desktop)
Sometimes my session goes A-D-Desktop (auth before seeing desktop)
Sometimes my session appears as in "C". (Ends up working fine after accepting cert error.)
The user who is broken, does A-D, then "Login Failed" is reported on screen-D. (client is win7, server is 2008 R2) Now, in accessing the same server, *my* credentials, and the broken user's credentials work FINE on my desktop's RDP client. When I remote-control the broken user's PC, and I use *my* credentials (which work on my desktop), they fail consistently on the broken user's RDP client. This tells me that something about the configuration of the Broken user's RDP client is preventing it from auth'ing to my server. The Broken User can bring up other RDP sessions to other Server2008 systems with scenario "A-D-Desktop", but the Broken client can't auth to my server to save our lives...
↧