Re: Remote Desktop Connection no longer working ...

Steve,

A few quick questions:
- When you say you can't login to the XPe system what exactly is happening? RDP client fails to connect to the XPe remote system
or the connect is successful but you cannot bypass the login screen?
- Can you ping the XPe device from any other machine (e.g., from XP Pro computer)?
- Are you trying to connect to XPe device using its netbios name or direct IP?
- What Logon component is your image based on - Winlogon or MinLogon?
- Did you resolve all the included component dependencies in TD?


Also a few things you may want to try right away but I will be guessing here without answers to the questions above:
- add "System Event Notification Service (SENS)" component
- add TAPI components such as "TAPI Performance DLL", "Primitive: Tapi32" and "Telephony"
- add "IP Router Monitor Library" component
- add "Dial-up Client for Windows", "Dial-Up Networking Common Libraries", "Dial-up Server for Windows " components and resolve
their dependencies. Be aware that these are pretty heavy components and you may want to back up your current configuration before
adding those.

=========
Regards,
KM


>I had the Remote Desktop working before, but haven't tested it since
> pre-SP2 build. Currently I can use Remote Desktop from the XP
> Embedded system to my XP Pro Development system, but I cannot login to
> the XPE system from the XP Pro system.
>
> I have searched the NG and checked many things as listed below, The
> only thing that I can see that looks like a problem is that the
> 'Remote Access Connection Manager' Service will not start.
> Detailed info is presented below, thanks in advance...
>
> SteveS
> StevesATeyeDASHimagingDOTcom
>
> COMPONENTS PRESENT IN BUILD:
> a.. Remote Assistance Automation Framework
> b.. Remote Assistance Channel
> c.. TCP/IP Networking with Client For MS Networks
> d.. Terminal Server Components:
> Client, Dev Redirector,
> Keyboard, Mouse, Remote Desktop)
> e.. Terminal Services Components:
> Client Active X core, Core, Core Mgmt Tools,
> Remote Assistance Component,
> Remote Management and Command Line Tools
> Runtime, Web Control Core, Web Control Extension,
> WMI Provider
> f.. RPC Remote over Named Pipes
> (As required for Remote Registry, per SP2 Known Issues)
>
>
> DOMAIN PARTICIPATION Variations Tried:
> a) Both computers joined to domain (nope)
> b) Both computers not domain members (nope)
> c) XP Pro computer is domain member, XPE is not (nope)
> In general, which of these three configurations is supported?
> Is domain membership a requirement for Remote Desktop connectivity?
>
> WINDOWS FIREWALL
> Configured to allow Remote Desktop on Default Port (Both Computers).
> Also Disabled on Both Computers, still no go.
>
> GROUP POLICIES (Both Computers)
> Administrative Templates\Terminal Services\ machine and computer
> branches both look OK.
> XPE system has this policy enabled in the User Configuration branch:
> 'Set Rules for Remote Control of Terminal Services' Enabled,
> with value 'Full Control Without user's permission'
>
> No other policies appear in either.
>
> SYSTEM PROPERTIES, Remote Tab (Both computers)
> Allow Remote Assistance Invitations = Checked (OK)
> Advanced Button, Remote Control:
> "Allow this computer to be controlled remotely' = Checked (OK)
>
> Allow Users to Remotely Connect to this Computer = Checked (OK)
> Remote Users Button: Administrator on each machine has access.
> Added and tried various users...
>
> VERIFIED REGISTRY SETTINGS on XPE System as follows:
>
> [HKLM\Software\Microsoft\Remote\Desktop\Policies]
> fAllowToGetHelp = 1 ;(this is only entry in this key)
>
> [HKLM\System\CurrentControlSet\Control\TerminalServer]
> ; (All DWORD values)
> fAllowFullControl=1
> fAllowRemoteAssistance=1
> fAllowToGetHelp=1
> fAllowUnsolicited=1
> fDenyTSConnections=0
> TSAdvertise=1
> TSEnabled=1
> TSUserEnabled=1
>
> RUNNING SERVICES ON XPE SYSTEM
> Terminal Services (Automatic, Started)
> Terminal Services Session Directory (Manual, Not Started)
> Remote Registry (Automatic, Started)
> Remote Desktop Help Session manager (Automatic, Started)
> Routing and Remote Access (Automatic, not started)
> Remote Access Connection Manager
> (Manual, Will not start on XPE System only)
> The error upon attempting to start is:
> "Could Not Start the Remote Access Connection Manager Service
> on Local Computer."
> " Error 1075: The dependency service does not exist or is
> marked for deletion"
>
> (Dependencies shows that 'Remote Access Auto Connection Manager"
> depends on this service, this service shows 'no dependencies')
>
> Remote Access Auto Connection Manager
> (Manual, Will not start), similar error as above.
>
> Tried this SP1 trick:
> (Actually deleted these entries in Registry, then Restarted...
> - They return automatically)
>
> Go to "Virtual Display Driver" component Registry section in your
> Configuration and manually delete the following entries:
>
> [HLKM\System\CurrentControlSet\-Services\mnmdd\Enum]
> "0"="Root\LEGACY_MNMDD\0000"
> "Count"=dword:00000001
> "NextInstance"=dword:00000001
>


.