Re: RDP access from Windows ME client

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jeffrey Randow (MVP) (jeffreyr-support_at_remotenetworktechnology.com)
Date: 04/30/04 

Date: Thu, 29 Apr 2004 20:07:05 -0500

Try updating the client software
(http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp) 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.
>

Relevant Pages

  • force DHCP client to start with Discover?
    ... I've noticed that the typical protocol sequence for DHCP assignment in Windows ... there a registry setting or other means by which I can force my client not to ...
    (microsoft.public.win32.programmer.networks)
  • Re: Remote Destop connections to a VPN network
    ... Phillip could the application.ini be used to specify that the firewall ... > The Remote Network needs to be added to the Internal Networks Definition ... >> I am using ISA 2004 and using the Firewall Client on my desktop. ...
    (microsoft.public.isa)
  • Re: site to site vpn
    ... Unfortunately you cannot have two VPN tunnels with the same remote network ... Either you make your client reconfigure the IP serie of his LAN or you may ... Then you configure your end of the VPN to cover those NAT addresses. ... I have created a site to site vpn with one of our customers as ...
    (microsoft.public.isa.vpn)
  • Re: multiple site to site vpn
    ... Unfortunately you cannot have two VPN tunnels with the same remote network ... Either you make your client reconfigure the IP serie of his LAN or you may ... Then you configure your end of the VPN to cover those NAT addresses. ... I have created a site to site vpn with one of our customers as ...
    (microsoft.public.isaserver)
  • urgent: outgoing vpn connectivity
    ... Client connects successfully. ... Remote network is on different subnet than SBS network. ... Those users can access file shares, RDP etc. ...
    (microsoft.public.windows.server.sbs)