Cannot RDP into server

Discussion in 'Windows Networking' started by Synapse Syndrome [KGB], Mar 30, 2009.

  1. I cannot connect to a server using RDP.

    I can connect to a Hyper-V virtual machine on the same computer okay.

    I cannot ping the 3389 port on the machine, while I can on the VM on it.

    RDP is in the exception list in the Firewall, and I still cannot connect
    with the Firewall turned off.

    This problem is driving me crazy.

    C:\>portping hubble 3389

    Tools4ever Port Ping Utility. Version 2.05
    Copyright (c) 2002 Tools4ever bv. All rights reserved.
    www.tools4ever.com

    Host: hubble
    Connection time: 20970 ms
    Connected host: -
    Connected port: -1
    Error code: 10060
    Error text: Error 10060 connecting socket. A connection attempt failed
    because the connected party did not properly respond after a period of time,
    or established connection failed because connected host has failed to
    respond.



    C:\>portping hubble 80

    Tools4ever Port Ping Utility. Version 2.05
    Copyright (c) 2002 Tools4ever bv. All rights reserved.
    www.tools4ever.com

    Host: hubble
    Connection time: 230 ms
    Connected host: 192.168.1.66
    Connected port: 80
    Error code: 0
    Error text: -


    C:\>portping polaris 3389

    Tools4ever Port Ping Utility. Version 2.05
    Copyright (c) 2002 Tools4ever bv. All rights reserved.
    www.tools4ever.com

    Host: polaris
    Connection time: 40 ms
    Connected host: 192.168.1.70
    Connected port: 3389
    Error code: 0
    Error text: -


    Does anybody know what could be going on??

    Cheers

    ss.
     
    Synapse Syndrome [KGB], Mar 30, 2009
    #1
    1. Advertisements


  2. Okay, with NETSTAT, I can see that TCP 3389 is not LISTENING.

    There are no details for port 3389 at all, unlike on the other machines.

    So why is that the case, when RDP is set to on?

    ss.
     
    Synapse Syndrome [KGB], Mar 30, 2009
    #2
    1. Advertisements

  3. Synapse Syndrome [KGB]

    Dave Patrick Guest

    Control Panel|Admin Tools|Services. Is Terminal Services started?



    --

    Regards,

    Dave Patrick ....Please no email replies - reply in newsgroup.
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    http://www.microsoft.com/protect
     
    Dave Patrick, Mar 30, 2009
    #3
  4. Yes. Everything looks fine, but it is not listening on port 3389.

    More info:



    D:\>psexec \\hubble sc query Termservice

    PsExec v1.94 - Execute processes remotely
    Copyright (C) 2001-2008 Mark Russinovich
    Sysinternals - www.sysinternals.com



    SERVICE_NAME: Termservice
    TYPE : 20 WIN32_SHARE_PROCESS
    STATE : 4 RUNNING
    (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
    WIN32_EXIT_CODE : 0 (0x0)
    SERVICE_EXIT_CODE : 0 (0x0)
    CHECKPOINT : 0x0
    WAIT_HINT : 0x0
    sc exited on hubble with error code 0.

    D:\>psexec \\hubble sc qc termservice

    PsExec v1.94 - Execute processes remotely
    Copyright (C) 2001-2008 Mark Russinovich
    Sysinternals - www.sysinternals.com


    [SC] QueryServiceConfig SUCCESS

    SERVICE_NAME: termservice
    TYPE : 20 WIN32_SHARE_PROCESS
    START_TYPE : 2 AUTO_START
    ERROR_CONTROL : 1 NORMAL
    BINARY_PATH_NAME : C:\Windows\System32\svchost.exe -k
    NetworkService
    LOAD_ORDER_GROUP :
    TAG : 0
    DISPLAY_NAME : Terminal Services
    DEPENDENCIES : RPCSS
    : TermDD
    SERVICE_START_NAME : NT Authority\NetworkService
    sc exited on hubble with error code 0.

    D:\>psexec \\hubble sc query rpcss

    PsExec v1.94 - Execute processes remotely
    Copyright (C) 2001-2008 Mark Russinovich
    Sysinternals - www.sysinternals.com



    SERVICE_NAME: rpcss
    TYPE : 20 WIN32_SHARE_PROCESS
    STATE : 4 RUNNING
    (NOT_STOPPABLE, NOT_PAUSABLE,
    IGNORES_SHUTDOWN)
    WIN32_EXIT_CODE : 0 (0x0)
    SERVICE_EXIT_CODE : 0 (0x0)
    CHECKPOINT : 0x0
    WAIT_HINT : 0x0
    sc exited on hubble with error code 0.

    D:\>psexec \\hubble sc qc rpcss

    PsExec v1.94 - Execute processes remotely
    Copyright (C) 2001-2008 Mark Russinovich
    Sysinternals - www.sysinternals.com


    [SC] QueryServiceConfig SUCCESS

    SERVICE_NAME: rpcss
    TYPE : 20 WIN32_SHARE_PROCESS
    START_TYPE : 2 AUTO_START
    ERROR_CONTROL : 1 NORMAL
    BINARY_PATH_NAME : C:\Windows\system32\svchost.exe -k rpcss
    LOAD_ORDER_GROUP : COM Infrastructure
    TAG : 0
    DISPLAY_NAME : Remote Procedure Call (RPC)
    DEPENDENCIES : DcomLaunch
    SERVICE_START_NAME : NT AUTHORITY\NetworkService
    sc exited on hubble with error code 0.

    C:\>psexec \\hubble netstat -an | grep 3389

    PsExec v1.94 - Execute processes remotely
    Copyright (C) 2001-2008 Mark Russinovich
    Sysinternals - www.sysinternals.com


    netstat exited on hubble with error code 0.

    ss.
     
    Synapse Syndrome [KGB], Mar 30, 2009
    #4
  5. Synapse Syndrome [KGB]

    Dave Patrick Guest

    Maybe the listening port was altered.

    http://support.microsoft.com/kb/187623



    --

    Regards,

    Dave Patrick ....Please no email replies - reply in newsgroup.
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    http://www.microsoft.com/protect


     
    Dave Patrick, Mar 30, 2009
    #5
  6. Have you ever been able to connect to this server? If yes, what did
    you change immediately before it stopped working?
    Does a reboot solve the problem?
    _________________________________________________________
    Vera Noest
    MCSE, CCEA, Microsoft MVP - Terminal Server
    TS troubleshooting: http://ts.veranoest.net
    *----------- Please reply in newsgroup -------------*
     
    Vera Noest [MVP], Mar 30, 2009
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.