1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Re: Terminal Services not working - Port 3389 not listening

Discussion in 'Windows Home Server' started by nickbsd, Oct 5, 2009.

  1. nickbsd

    nickbsd Guest

    mgorman@elitefoodco.com@ THANK YOU SO MUCH for your resolution.

    I did a P2V in VMWARE on a Windows 2000 server which went fine.
    Performed anther P2V and it booted into the OS fine but I couldn't RDP
    TO it and couldn't figure out why.

    After performing two additional P2V's and adding/removing the terminal
    services via add/remove programs I could not figure it out. Thank
    goodness scouring the net paid off after finding your post.

    Thanks for the hardwork and the effort to post the resolution online
    for the rest of us.


    --
    nickbsd
    ------------------------------------------------------------------------
    nickbsd's Profile:
    View this thread:


     
  2. "nickbsd" <nickbsd.3zld3b@DoNotSpam.com> wrote in message
    news:nickbsd.3zld3b@DoNotSpam.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > mgorman@elitefoodco.com@ THANK YOU SO MUCH for your resolution.
    >
    > I did a P2V in VMWARE on a Windows 2000 server which went fine.
    > Performed anther P2V and it booted into the OS fine but I couldn't RDP
    > TO it and couldn't figure out why.
    >
    > After performing two additional P2V's and adding/removing the terminal
    > services via add/remove programs I could not figure it out. Thank
    > goodness scouring the net paid off after finding your post.
    >
    > Thanks for the hardwork and the effort to post the resolution online
    > for the rest of us.
    >
    >
    > --
    > nickbsd
    > ------------------------------------------------------------------------
    > nickbsd's Profile:
    > View this thread:
    >

    >
    >

    ><!--colorc--><!--/colorc-->


    Nickbsd,

    Techarena pulls and pushes posts to the Microsoft public newsgroups. That is
    where all posts originate or are sent. However, they expire at the
    newsgroups in 90 days, therefore we cannot see what you are replying to. I
    am posting the previous suggested reasons why the problem you are
    experiencing occured and the suggested solution for others to benefit.
    Please keep in mind for future references to post the previous relevant post
    to help others in the MIcrosoft public groups.

    ---
    Re: Terminal Services not working - Port 3389 not listening

    --------------------------------------------------------------------------------

    Found the solution to my particular problem. Article:


    CAUSE
    This problem can occur if the server has been booted by using the Last
    Known Good Configuration option more than once. When the server has
    been booted into the last known good configuration more than once, the
    ControlSet001 registry key is deleted. However, the following registry
    value is hard-coded to use the ControlSet001 registry key:
    Key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Terminal
    Server\VIDEO\rdpdd\

    Value name: \Device\Video0
    Value type: REG_SZ
    Value data:
    \REGISTRY\Machine\System\ControlSet001\Services\RD PDD\Device0
    Back to the top

    RESOLUTION
    WARNING: If you use Registry Editor incorrectly, you may cause serious
    problems that may require you to reinstall your operating system.
    Microsoft cannot guarantee that you can solve problems that result from
    using Registry Editor incorrectly. Use Registry Editor at your own
    risk.

    To resolve this problem, obtain the latest service pack for Windows
    2000. For additional information, click the following article number to
    view the article in the Microsoft Knowledge Base:
    260910 (
    ) How to Obtain
    the Latest Windows 2000 Service Pack
    To resolve this problem: 1. Start Registry Editor (Regedt32.exe).
    2. Locate and click the following registry key:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Terminal
    Server\VIDEO\rdpdd\
    Note If you do not have this key, use Registry Editor to create it.
    3. Do one of the following:· If you did not have to create the key in
    step 2, change the following value
    Name: \Device\Video0
    Type: REG_SZ
    Value: \REGISTRY\Machine\System\ControlSet001\Services\RD PDD\Device0
    to the following:
    Name: \Device\Video0
    Type: REG_SZ
    Value:
    \REGISTRY\Machine\System\CurrentControlSet\Service s\RDPDD\Device0
    · If you had to create the registry key in step 2, add the following
    value:
    Subkey name: RDPDD
    Name: \Device\Video0
    Type: REG_SZ
    Value:
    \REGISTRY\Machine\System\CurrentControlSet\Service s\RDPDD\Device0

    4. After you change (or create) the value, restart the computer that is
    running Terminal Services.
    ---


    --
    Ace

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

    Please reply back to the newsgroup or forum for collaboration benefit among
    responding engineers, and to help others benefit from your resolution.

    Ace Fekay, MCT, MCTS 2008, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA
    Messaging
    Microsoft Certified Trainer

    For urgent issues, please contact Microsoft PSS directly. Please check
    for regional support phone numbers.
     

Share This Page