1

I've read that on Windows Server 2008, raising the DFL can cause XP and Linux/rdesktop clients to not be able to connect, but only if Network Level Authentication is enabled. However, we're only on Windows Server 2003 SP2, which doesn't even have the option to enable NLA, IIRC. So I thought we'd be safe.

I went and upgraded our DFL to Windows Server 2003, and now I can't log in via remote desktop. The error message, which appears almost immediately after clicking, is:

---------------------------
Remote Desktop Connection
---------------------------
This computer can't connect to the remote computer.

Try connecting again. If the problem continues, contact the owner
of the remote computer or your network administrator.
---------------------------
OK   Help   
---------------------------

Is this a coincidence, or did the DFL raise break RDP? (I didn't see any warning about this in the documentation.)

Kev
  • 994

1 Answers1

1

I don't believe that action alone would cause this. Were there any domain controller changes to go along with it? I'm suspecting that a group policy was set to require NLA or something like that. Can you telnet to the RDC port (3389)? Firewall blocking it now? Do you have NLA enabled for your XP clients?

NLA for XP SP3

sinping
  • 2,090
  • 14
  • 13