Sign in with
Sign up | Sign in
Your question

RDP access from Windows ME client

Tags:
  • Windows Me
  • Connection
  • Windows XP
Last response: in Windows XP
Share
Anonymous
April 27, 2004 5:21:01 PM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Hi,

I am trying to set up a client's remote access to a central PC running
Windows XP Pro SP1 from his home machine (Windows ME). He is connecting to
the internet via ISDN and can successfully connect to the central site's VPN
(Windows 2000 SBS w/SP4). When he attempts to run RDP client to connect to
the client machine it starts the connection (title bar appears), the screen
goes black and then nothing happens for 1-2 mins after which a protocol
error appears (error code 0x10cb) and it disconnects.

Also, an error appears in the Windows XP client event log :

Event Type: Error
Event Source: TermDD
Event ID: 50
Description: The RDP protocol component WD detected an error in the protocol
stream and has disconnected the client.

The user was able to connect successfully a few times, we then changed the
screen resolution and tried to reconnect without success ever since. I have
used other remote clients to test the connection and they all work fine
(Windows 98SE, Windows XP Pro) and an internal RDP session also works so it
must be something on his local machine.

Anyone got any suggestions? I have searched Microsoft and used Google for
this event ID and found lots of references to component "DATA ENCRYPTION"
but not WD.

Help!!!!!

Mike Wells.

More about : rdp access windows client

Anonymous
April 30, 2004 12:07:05 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Try updating the client software
(http://www.microsoft.com/windowsxp/pro/downloads/rdclie...) to
help rule out any corruption in the application...

Are these other machines you tested on the same remote network as the
XP Pro SP1 machine in question?

Jeffrey Randow (Windows Net. & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

On Tue, 27 Apr 2004 13:21:01 +0100, "Michael Wells"
<mikew@sigma-office.net> wrote:

>Hi,
>
>I am trying to set up a client's remote access to a central PC running
>Windows XP Pro SP1 from his home machine (Windows ME). He is connecting to
>the internet via ISDN and can successfully connect to the central site's VPN
>(Windows 2000 SBS w/SP4). When he attempts to run RDP client to connect to
>the client machine it starts the connection (title bar appears), the screen
>goes black and then nothing happens for 1-2 mins after which a protocol
>error appears (error code 0x10cb) and it disconnects.
>
>Also, an error appears in the Windows XP client event log :
>
>Event Type: Error
>Event Source: TermDD
>Event ID: 50
>Description: The RDP protocol component WD detected an error in the protocol
>stream and has disconnected the client.
>
>The user was able to connect successfully a few times, we then changed the
>screen resolution and tried to reconnect without success ever since. I have
>used other remote clients to test the connection and they all work fine
>(Windows 98SE, Windows XP Pro) and an internal RDP session also works so it
>must be something on his local machine.
>
>Anyone got any suggestions? I have searched Microsoft and used Google for
>this event ID and found lots of references to component "DATA ENCRYPTION"
>but not WD.
>
>Help!!!!!
>
>Mike Wells.
>
July 23, 2004 12:34:02 PM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I am experiencing this exact same problem with a Windws ME user. He had been successfully connecting from a remote site via VPN and then using RDP to connect to a Windows 2003 Server. We get the same error whether he tries to rdp to the server or a Windows XP workstation. However, he was able to successfully connect to a Windows 2000 Server which had terminal services enabled for administrative mode.

We did download the client for MS's web site, uninstall the RDP client and re-install it. However, we still have the same problem.

Any more advice? Anyone?

"Jeffrey Randow (MVP)" wrote:

> Try updating the client software
> (http://www.microsoft.com/windowsxp/pro/downloads/rdclie...) to
> help rule out any corruption in the application...
>
> Are these other machines you tested on the same remote network as the
> XP Pro SP1 machine in question?
>
> Jeffrey Randow (Windows Net. & Smart Display MVP)
> jeffreyr-support@remotenetworktechnology.com
>
> Please post all responses to the newsgroups for the benefit
> of all USENET users. Messages sent via email may or may not
> be answered depending on time availability....
>
> Remote Networking Technology Support Site -
> http://www.remotenetworktechnology.com
> Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
>
> On Tue, 27 Apr 2004 13:21:01 +0100, "Michael Wells"
> <mikew@sigma-office.net> wrote:
>
> >Hi,
> >
> >I am trying to set up a client's remote access to a central PC running
> >Windows XP Pro SP1 from his home machine (Windows ME). He is connecting to
> >the internet via ISDN and can successfully connect to the central site's VPN
> >(Windows 2000 SBS w/SP4). When he attempts to run RDP client to connect to
> >the client machine it starts the connection (title bar appears), the screen
> >goes black and then nothing happens for 1-2 mins after which a protocol
> >error appears (error code 0x10cb) and it disconnects.
> >
> >Also, an error appears in the Windows XP client event log :
> >
> >Event Type: Error
> >Event Source: TermDD
> >Event ID: 50
> >Description: The RDP protocol component WD detected an error in the protocol
> >stream and has disconnected the client.
> >
> >The user was able to connect successfully a few times, we then changed the
> >screen resolution and tried to reconnect without success ever since. I have
> >used other remote clients to test the connection and they all work fine
> >(Windows 98SE, Windows XP Pro) and an internal RDP session also works so it
> >must be something on his local machine.
> >
> >Anyone got any suggestions? I have searched Microsoft and used Google for
> >this event ID and found lots of references to component "DATA ENCRYPTION"
> >but not WD.
> >
> >Help!!!!!
> >
> >Mike Wells.
> >
>
>
!