NEO RDP Manager logoNEO RDP Manager
DEEN
Download

Troubleshooting

Fixes for the most common stumbling blocks – from installation to individual protocols.

Windows SmartScreen warns during installation

The installer is not code-signed yet. Click “More info” → “Run anyway”. If you want to be sure, compare the file's SHA-256 checksum first.

I forgot my master password

Then the stored passwords can no longer be decrypted – there is deliberately no back door. To start over, quit the app and rename %APPDATA%\NeoRDPManager\neordp.db. On the next start you set up a new vault and import your connections again, for example from an earlier mRemoteNG export or the original confCons.xml.

The RDP session still asks for the password

  • Check in the details where the credentials come from – if it says “none”, nothing is stored, or a folder stops the inheritance.
  • Check the notation: user and domain separately (CORP and admin) or as a UPN in the user box (admin@corp.example).
  • If a group policy forbids saving credentials, the app can't hand the password to Windows briefly either – mstsc then asks by itself.

The resolution doesn't adapt

Dynamic resolution needs Windows 8.1 / Server 2012 R2 or newer on the server. For older targets choose “fixed resolution, scaled (smart size)” for the connection. In a running session the scale button fits the picture to the window; if that doesn't help, “reconnect” connects with the current window size.

A certificate warning appears on every connection

The server uses a self-signed or untrusted certificate. The clean fix is a certificate from your PKI on the server. “Ignore certificate errors” in the connection's security options is meant for test environments only.

My Default.rdp has changed

The app replaces Documents\Default.rdp only for the moment of the start and restores it bit for bit afterwards, even when mstsc writes its settings into it at the end of a session. After a crash it restores the backup %APPDATA%\NeoRDPManager\default_rdp.backup on the next start. If you need the file right away, copy that backup back by hand. If you don't want the mechanism, set the launch method to “classic via .rdp file”.

SSH warns: the host key has changed

That happens when a server was reinstalled or its SSH key replaced – or when someone has put themselves in between. Compare the fingerprint shown through another channel (e.g. at the server console with ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub) and only then confirm.

The SSH key isn't accepted

The app reads keys in OpenSSH or PEM format. Export PuTTY keys (.ppk) first with PuTTYgen via “Conversions → Export OpenSSH key”. Also check that the public key is listed in ~/.ssh/authorized_keys on the server.

PowerShell remoting doesn't connect

  • Remoting must be enabled on the target: Enable-PSRemoting (as administrator).
  • Targets outside the domain or addressed by IP must be listed as trusted on your computer: Set-Item WSMan:\localhost\Client\TrustedHosts -Value "10.20.0.5" -Concatenate
  • Port 5986 needs an HTTPS listener with a valid certificate on the target.

The VNC server refuses the connection

The built-in client handles standard VNC authentication and connections without a password. Switch servers that only accept their own methods (such as vendor-specific encryption or system account sign-in) to a classic VNC password.

The dot is red although the server is running

The check opens a TCP connection to the configured port. If it's red, a firewall usually blocks the port from your computer, or the service listens on a different port. Ping isn't used. F5 checks again right away.

Import problems

  • mRemoteNG reports a wrong password: it means the password you set in mRemoteNG for the connection file – not your Windows password.
  • RDCMan connections without a password: RDCMan binds passwords to the old computer; store them again, ideally on the folder.
  • Active Directory finds nothing: the computer must be a domain member and reach a domain controller. Also check the notation of the search base (OU=…,DC=…).

Logs for troubleshooting

The app writes its logs to %APPDATA%\NeoRDPManager\logs (in portable mode to data\logs). For more detailed entries, start the app with the environment variable NEORDP_LOGLEVEL=DEBUG:

$env:NEORDP_LOGLEVEL = "DEBUG"
& "C:\Program Files\NeoRDPManager\NeoRDPManager.exe"

Passwords never show up in the logs.