n rdp

Remote Desktop readiness check & repair (local or remote)

Usage — n rdp

═══════════════════════════════════════════════════════════════════════════════
  Netscrew ("n") — rdp (remotedesktop, mstsc) — Remote Desktop readiness (local) or reachability (remote)
═══════════════════════════════════════════════════════════════════════════════

USAGE:
  n rdp .                              is THIS Windows PC set up to accept RDP? (traps included)
  n rdp . --fix                        fix the fixable items (asks; leaves NLA on)
  n rdp <host>                         check a remote PC: 3389 open, NLA required, computer name

Target: . = this machine · <host> = remote
Deeper: n rdp -h = the concept/theory behind this command  ·  n -h ssh-windows

The concept behind it — n rdp -h

═══════════════════════════════════════════════════════════════════════════════
  Netscrew ("n") — Remote Desktop (RDP) Readiness & Repair
═══════════════════════════════════════════════════════════════════════════════

COMMANDS:
  n rdp                 Check whether THIS Windows PC is set up to accept RDP
  n rdp --fix           Fix the fixable items (asks first; leaves NLA ON)
  n <host> rdp          Check a remote PC: is 3389 open, is NLA required, its computer name

WHY RDP SAYS "YOUR CREDENTIALS DID NOT WORK" (THE TWO TRAPS):
  1. Microsoft-account sign-in. If you sign into Windows with a Microsoft account, the RDP
     username must be MicrosoftAccount\your-email — not your short local name. n rdp detects this.
  2. Passwordless / Windows Hello. The setting "only allow Windows Hello sign-in" hides the
     password box, so Windows may never have cached the password RDP needs. n rdp --fix turns it
     off; then sign in once with the password (or runas /u:MicrosoftAccount\your-email cmd) to cache it.

WHAT n rdp CHECKS (local, Windows):
  • Windows edition (Home can't host RDP)      • TermService running
  • Remote Desktop enabled (fDenyTSConnections) • 'Remote Desktop' firewall rule
  • Network profile (RDP is blocked on Public)  • NLA on/off (reported, never disabled)
  • The two traps above

WHAT n <host> rdp CHECKS (any OS, no access to the target needed):
  • Is TCP 3389 open   • Does the server require NLA (it performs the RDP negotiation)
  • The remote computer name from its RDP TLS certificate

Back to main help: n -h