Guest ChrisW Posted August 28, 2008 Posted August 28, 2008 Hiya, How do you run Terminal Services Configuration (tscc.msc) on XP? I've tried installing adminpak.exe from the Windows 2003 setup disks. tscc is not in adminpak. So I've tried copying the files from a 2003 computer to the XP box. Tho when I run tscc.msc from XP after copying it says "MMC could not create the snap-in." So whats the right way to run the console, eh? ChrisW
Guest smlunatick Posted August 28, 2008 Posted August 28, 2008 Re: Terminal Services Configuration On Aug 28, 2:24 pm, ChrisW <chrisw...@gmail.com> wrote: > Hiya, > > How do you run Terminal Services Configuration (tscc.msc) on XP? I've > tried installing adminpak.exe from the Windows 2003 setup disks. tscc > is not in adminpak. So I've tried copying the files from a 2003 > computer to the XP box. Tho when I run tscc.msc from XP after copying > it says "MMC could not create the snap-in." > > So whats the right way to run the console, eh? > > ChrisW Terminal Services are known as Remote Desktop in Windows XP Pro. XP Home can only "connect to" a Remote Desktop "server."
Guest ChrisW Posted August 28, 2008 Posted August 28, 2008 Re: Terminal Services Configuration On Aug 28, 10:53 am, smlunatick <yves...@gmail.com> wrote: > Terminal Services are known as Remote Desktop in Windows XP Pro. > XP Home can only "connect to" a Remote Desktop "server." Right. So is there a Remote Desktop configuration console lying aroudn somewhere for XP? This is XP Professional. I need to recreate the rdp- tcp listener. Thanks, ChrisW
Guest smlunatick Posted August 28, 2008 Posted August 28, 2008 Re: Terminal Services Configuration On Aug 28, 4:18 pm, ChrisW <chrisw...@gmail.com> wrote: > On Aug 28, 10:53 am, smlunatick <yves...@gmail.com> wrote: > > > Terminal Services are known as Remote Desktop in Windows XP Pro. > > XP Home can only "connect to" a Remote Desktop "server." > > Right. So is there a Remote Desktop configuration console lying aroudn > somewhere for XP? This is XP Professional. I need to recreate the rdp- > tcp listener. > > Thanks, > > ChrisW Right Click on "My Computer" icon Select "Properties" Select "Remote" tab In Remote Desktop "section," you can activate it
Guest ChrisW Posted August 28, 2008 Posted August 28, 2008 Re: Terminal Services Configuration Thanks but activating is not the problem. I've done it and no joy. I need to run Terminal Services Configuration to delete and recreate the rdp-tcp listener port. Do you know how to do this? On Aug 28, 11:54 am, smlunatick <yves...@gmail.com> wrote: > Right Click on "My Computer" icon > > Select "Properties" > > Select "Remote" tab > > In Remote Desktop "section," you can activate it
Guest smlunatick Posted August 28, 2008 Posted August 28, 2008 Re: Terminal Services Configuration On Aug 28, 7:34 pm, ChrisW <chrisw...@gmail.com> wrote: > Thanks but activating is not the problem. I've done it and no joy. I > need to run Terminal Services Configuration to delete and recreate the > rdp-tcp listener port. Do you know how to do this? > > On Aug 28, 11:54 am, smlunatick <yves...@gmail.com> wrote: > > > Right Click on "My Computer" icon > > > Select "Properties" > > > Select "Remote" tab > > > In Remote Desktop "section," you can activate it I have not found any tool to change the default port of 3389. You can physically edit the registry.
Guest ChrisW Posted August 28, 2008 Posted August 28, 2008 Re: Terminal Services Configuration On Aug 28, 3:50 pm, smlunatick <yves...@gmail.com> wrote: > I have not found any tool to change the default port of 3389. You can > physically edit the registry. Ok, ok, check it out. I am not trying to activate rdp or to change the port. I am trying to rdp into the workstation. The port is open (as validated by telnet and netstat). The connection gets reset when rdp'ing in. Theres an event in the logs. I looked it up and the suggested fix is to recreate the rdp-tcp listener using Terminal Services Configuration. The issue there is that I do not know how to install the console on Windows XP Professional. The event long entry reads: Event Type: Error Event Source: TermDD Event Category: None Event ID: 50 Description: The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client. Thanks again for your help so far. Can you give me some tips SPECIFICALLY on fixing the problem or installing the tscc.msc console? ChrisW
Guest ChrisW Posted August 28, 2008 Posted August 28, 2008 Re: Terminal Services Configuration I also tried deleting registry keys but that didnt work. "The RDP Protocol Component "DATA ENCRYPTION" Detected an Error..." error message http://support.microsoft.com/kb/323497 On Aug 28, 4:09 pm, ChrisW <chrisw...@gmail.com> wrote: > On Aug 28, 3:50 pm, smlunatick <yves...@gmail.com> wrote: > > > I have not found any tool to change the default port of 3389. You can > > physically edit the registry. > > Ok, ok, check it out. I am not trying to activate rdp or to change the > port. I am trying to rdp into the workstation. The port is open (as > validated by telnet and netstat). The connection gets reset when > rdp'ing in. Theres an event in the logs. I looked it up and the > suggested fix is to recreate the rdp-tcp listener using Terminal > Services Configuration. The issue there is that I do not know how to > install the console on Windows XP Professional. > > The event long entry reads: > > Event Type: Error > Event Source: TermDD > Event Category: None > Event ID: 50 > Description: > The RDP protocol component "DATA ENCRYPTION" detected an error in the > protocol stream and has disconnected the client. > > Thanks again for your help so far. Can you give me some tips > SPECIFICALLY on fixing the problem or installing the tscc.msc console? > > ChrisW
Guest smlunatick Posted August 29, 2008 Posted August 29, 2008 Re: Terminal Services Configuration On Aug 28, 10:23 pm, ChrisW <chrisw...@gmail.com> wrote: > I also tried deleting registry keys but that didnt work. > > "The RDP Protocol Component "DATA ENCRYPTION" Detected an Error..." > error messagehttp://support.microsoft.com/kb/323497 > > On Aug 28, 4:09 pm, ChrisW <chrisw...@gmail.com> wrote: > > > On Aug 28, 3:50 pm, smlunatick <yves...@gmail.com> wrote: > > > > I have not found any tool to change the default port of 3389. You can > > > physically edit the registry. > > > Ok, ok, check it out. I am not trying to activate rdp or to change the > > port. I am trying to rdp into the workstation. The port is open (as > > validated by telnet and netstat). The connection gets reset when > > rdp'ing in. Theres an event in the logs. I looked it up and the > > suggested fix is to recreate the rdp-tcp listener using Terminal > > Services Configuration. The issue there is that I do not know how to > > install the console on Windows XP Professional. > > > The event long entry reads: > > > Event Type: Error > > Event Source: TermDD > > Event Category: None > > Event ID: 50 > > Description: > > The RDP protocol component "DATA ENCRYPTION" detected an error in the > > protocol stream and has disconnected the client. > > > Thanks again for your help so far. Can you give me some tips > > SPECIFICALLY on fixing the problem or installing the tscc.msc console? > > > ChrisW Which version of the Remote Desktop are you using? There is supposed to be three versions in XP Pro. Remote Desktop 5x -- XP (original, SP1 and SP2) Remote Desktop 6 -- separate download for XP SP2 and WGA. Remote Desktop 6.1 -- bundled in XP Service pack 3.
Guest ChrisW Posted August 29, 2008 Posted August 29, 2008 Re: Terminal Services Configuration Answer: Remote Desktop 6.1 -- bundled in XP Service pack 3. On Aug 29, 12:48 pm, smlunatick <yves...@gmail.com> wrote: > Which version of the Remote Desktop are you using? There is supposed > to be three versions in XP Pro.
Guest smlunatick Posted August 29, 2008 Posted August 29, 2008 Re: Terminal Services Configuration On Aug 29, 9:15 pm, ChrisW <chrisw...@gmail.com> wrote: > Answer: Remote Desktop 6.1 -- bundled in XP Service pack 3. > > On Aug 29, 12:48 pm, smlunatick <yves...@gmail.com> wrote: > > > Which version of the Remote Desktop are you using? There is supposed > > to be three versions in XP Pro. Not sure about "compatibility" between version but it seems that the newest version has "issues" when the older one try to connect to it. As stated, the versions seem to loose interconnectivity between each other.
Recommended Posts