Share via

we can't connect to the server through RDP neither able to connect to the application on it

Adeniyi Ezekiel 0 Reputation points
2026-05-15T16:00:13.6+00:00

we can't connect to the server through RDP neither able to connect to the application on it, we cannot access the server by any means

Windows for business | Windows Server | Networking | Network connectivity and file sharing
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Domic Vo 22,685 Reputation points Independent Advisor
    2026-05-15T16:37:02.68+00:00

    Hi Adeniyi Ezekiel,

    Because neither Remote Desktop nor the hosted application is reachable, the server is completely isolated from the network, making out-of-band console access your mandatory first step. You must connect directly to the hardware management interface like iDRAC or iLO, the hypervisor console if it is a virtual machine, or the serial console for cloud environments. This console access bypasses the standard network stack, acting exactly like a physical monitor and keyboard plugged into the machine. Once logged in, open a command prompt and verify the base network configuration by pinging your default gateway and checking the adapter status to rule out a disconnected virtual switch or a static IP conflict on your subnet.

    If the core network is operational, you must verify the Remote Desktop protocol status by running the qwinsta command to see if the listener is active. If the RDP interface is down or missing, open the Registry Editor and navigate exactly to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server to inspect the fDenyTSConnections value. Changing this key to 0 stops the operating system from actively blocking remote management sessions. Finally, open the Windows Services console to ensure the Remote Desktop Services are running under their default permissions, and verify that the Windows Firewall allows inbound TCP traffic on port 3389. Once network and RDP access are restored, you can use this exact methodology to check your specific application's service state and firewall port bindings.

    Hope this answer brought you some useful information. If it did, please hit “accept answer”.

    Domic V.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-05-15T16:00:32.6066667+00:00

    Use console-level access first, then narrow down whether the issue is with the server itself, the RDP listener, or the network.

    1. Verify the server is actually running
      • If this is a physical server, use its out-of-band console (for example, iLO/DRAC).
      • If this is a VM (for example, Hyper‑V), use the hypervisor console.
      • If the machine is not in a running state or the console itself cannot connect, this must be fixed first.
    2. Check if the RDP listener is working (from console)
      • Open a command prompt and run: 
             qwinsta
      • Confirm there is a line like: 
             rdp-tcp                    65536 Listen
      • If rdp-tcp is not present or not in Listen state, fix the listener:
        1. Open Registry Editor and verify:
          • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp
            • fEnableWinStation = 1 (DWORD)
          • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
            • fDenyTSConnections = 0 (DWORD)
          • If a policy is configured: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services
            • fDenyTSConnections = 0 (DWORD)
        2. Ensure services are running:
          • Remote Desktop Services (TermService)
          • Remote Desktop Services UserMode Port Redirector (UmRdpService)
        3. If services fail to start, add Network Service to local Administrators and restart TermService: 
                  Add-LocalGroupMember -Group Administrators -Member "Network Service"
          Then restart Remote Desktop Services.
        4. Confirm the server is not in Sysprep state:
          • HKEY_LOCAL_MACHINE\SYSTEM\Setup
            • SystemSetupInProgress = 0
            • OOBEInProgress = 0
        5. If the RDP‑TCP key is suspected corrupt, export HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp from a working server with the same OS, back up the existing key on the broken server, delete it, and import the good one.
    3. Verify network and RDP port
      • From the server console, test local RDP stack:
        1. Run mstsc.
        2. Connect to localhost.
        • If this fails, the issue is on the server (RDP stack/config), not the network.
      • From another machine on the same network, run in PowerShell: 
             Test-NetConnection -ComputerName <ServerNameOrIP> -Port 3389 -InformationLevel Detailed
        • If TcpTestSucceeded = False, there is a connectivity problem.
      • Check the RDP port in the registry on the server:
        • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp
          • PortNumber should be 0x00000d3d (3389).
        • If a different port is configured, connect using server:port.
    4. Check firewall and network security
      • On the server, ensure Windows Firewall allows RDP: 
             Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Set-NetFirewallRule -Enabled True
      • To temporarily rule out firewall (for testing only): 
             Set-NetFirewallProfile -Profile Domain,Public,Private -Enabled False
      • If using Azure or similar, verify Network Security Group (NSG) or other network devices allow inbound TCP 3389 to the server’s NIC/subnet.
    5. Check DNS and name resolution
      • From a client, try connecting by IP instead of hostname.
      • If IP works but hostname fails, fix DNS records or client name resolution.
    6. If RDP works but the application is still unreachable
      • Once RDP is restored, troubleshoot the application separately (service status, port bindings, firewall rules for that app’s port, etc.).
    7. If none of the above restores connectivity
      • If the server is reachable only via out-of-band console and all RDP/network checks fail, or if RDP‑TCP listener cannot be brought to Listen state, escalate to Microsoft Support for deeper analysis.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.