none
Can ping but cannot RDP RRS feed

  • Question

  • Hello

    I have a few days of problems with RDP on my server 2012 STD

    RDP connections for server administration no longer pass

    I connected in KVM, everything is functional except the RDP

    I have opened the ports on the firewall, I activated the RDP and allowed "Everyone" without requiring the secure connection

    By entering netstat -a port 3389 does not appear, so it is not listening

    At a sfc / scannow I had corrupted files that the tool fixed, now no more worry but still my rdp inaccessible

    I also tried to forbid connections -> reboot -> allow connections ---> No result

    I tried Completely Disabling Windows Firewall and Antivirus -> Without result

    I do not have a physical firewall

    I do not know what to try ..

    Do you have any ideas ?

    Thank you in advance !

    Maxim
    Thursday, April 25, 2019 9:50 AM

All replies

  • Might try from PowerShell from source and target.

    Test-NetConnection -ComputerName "192.168.49.142" -CommonTCPPort "RDP" -InformationLevel "Detailed"


     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Thursday, April 25, 2019 1:00 PM
  • I tried but "Test-NetConnection" is not available with my Windows version (Server 2012)

    With my Windows 10 :

    AVERTISSEMENT : TCP connect to (xxxx : 3389) failed
    
    
    ComputerName            : xxxx
    RemoteAddress           : xxxx
    RemotePort              : 3389
    NameResolutionResults   : xxxx
    MatchingIPsecRules      :
    NetworkIsolationContext : Internet
    IsAdmin                 : False
    InterfaceAlias          : Ethernet
    SourceAddress           : 192.168.1.32
    NetRoute (NextHop)      : 192.168.1.1
    PingSucceeded           : True
    PingReplyDetails (RTT)  : 17 ms
    TcpTestSucceeded        : False

    • Edited by max3939 Thursday, April 25, 2019 1:31 PM
    Thursday, April 25, 2019 1:27 PM
  • Might also try portqryui tool.

    https://www.microsoft.com/en-us/download/details.aspx?id=24009

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Thursday, April 25, 2019 1:33 PM
  •  Starting portqry.exe -n 127.0.0.1 -e 3389 -p TCP ...
    
    
    Querying target system called:
    
     127.0.0.1
    
    Attempting to resolve IP address to a name...
    
    
    IP address resolved to HOSTNAME
    
    querying...
    
    TCP port 3389 (ms-wbt-server service): NOT LISTENING
    portqry.exe -n 127.0.0.1 -e 3389 -p TCP exits with return code 0x00000001.


    • Edited by max3939 Thursday, April 25, 2019 1:36 PM
    Thursday, April 25, 2019 1:36 PM
  • Looks like either Remote Desktop Services (TermService) service is not running or is listening on another port.

    https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/change-listening-port

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    Thursday, April 25, 2019 1:40 PM
  • I already checked this, but a strange thing appears ...
    in "HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Control \ Terminal Server \ WinStations \"

    I have not "RDP-Tcp"

    I checked my other servers, they have this key, but not this server

    I have "Console" and "Session", no "RDP-Tcp"

    But in "Session" key i have "PortNumber" DWORD whith value 3389

    Is it "normal" ?


    • Edited by max3939 Thursday, April 25, 2019 1:51 PM
    Thursday, April 25, 2019 1:49 PM
  • Is Remote Desktop Services (TermService) service running?

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Thursday, April 25, 2019 1:51 PM
  • Yes ! it is runnig with automatic start
    Thursday, April 25, 2019 1:52 PM
  • Also check the security filter driver mentioned here.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/c3cfc2df-fc29-4abc-acf1-01797f528333/port-3389-not-listening?forum=winserverTS

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Thursday, April 25, 2019 2:03 PM
  • I have not fouded this "security filter driver"

    i've read that's can be not implemented ov SRV2012

    I also tried to import the reg key RDP-Tcp from another server who work

    But...When I start, the key was not registered and had disappeared

    • Edited by max3939 Thursday, April 25, 2019 3:10 PM
    Thursday, April 25, 2019 3:07 PM
  • Not sure what is meant but if you think the registry is missing values you can try exporting the key

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService

    and import on problem one. Also not sure of history but you can also try;

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Thursday, April 25, 2019 3:15 PM
  • Hi,

    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Otto Wang



    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, May 1, 2019 4:41 AM
    Moderator
  • Hi

    Nothing changed, I reinstalled the server and it was ok

    Thanks anyway to Dave Patrick for your advice !


    Thursday, May 2, 2019 9:37 AM
  • On the target machine, make sure that Port 3389 is not being blocked by a firewall.  If you are using Windows Firewall, go to the Windows Firewall control panel, verify that "Don't Allow Exceptions" is not checked under the "General" tab, then click on the "Exceptions" tab and make sure there is a check mark beside "Remote Desktop".
    In remote machine, you can also make sure that a program is running to accept incoming remote desktop connections by bringing up a command prompt (Start -> Run -> "cmd") and entering the following command:

       netstat   -an   |    find   "3389"
    If all is well, you should see the following line returned:
         TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING 

    Also check the below post :

    https://www.morgantechspace.com/2015/01/can-ping-but-cannot-connect-using-remote-desktop-rdp.html

    Thursday, May 2, 2019 12:24 PM
  • Hi

    In my question post you will read that i have already done this before posting.

    Thursday, May 2, 2019 12:28 PM
  • You're welcome.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Thursday, May 2, 2019 1:03 PM