Using Remote Desktop Connection in Vista, I used to be able to successfully connect to a couple of servers running Windows Server 2003 Enterprise running Remote Desktop Admin (not full Terminal Server licensing in place).
Both of these machines were upgraded to Windows Server 2003 R2. Now, when a Vista (or XP for that matter) client tries to connect to either of those servers with RDC, they find the server (name resolution seems to work), and I’m prompted for credentials. The RDC applet greys out as if it’s about to connect, then about 1 second later, nothing happens and I’m back to the RDC prompt (asking me for the server name again). No error. This occurs on both of the R2 servers (both running Enterprise, one is a domain controller, the other is not).
RDC functions fine when connecting to non-R2 2003 servers.
I don’t show anything in the security log for these R2 servers that show that credendials were wrong. If I purposely enter the wrong credentials, the same effect, no prompt that the credentials were wrong.
DNS seems to be fine as I can ping and remote connect to these machines using other remote control software (Radmin). I’ve tried un-installing that thinking it was a problem with R2 and the video hook drivers, but no luck.
Firewall settings on the R2 servers also show that Remote Desktop is enabled as an exception. I’ve also tried completely turning off the firewall, no luck.
Terminal Services Manager is running fine and showing that RDP-TCP listener is running.
Thanks all.