Re: Remote Desktop Connection Is again working! (the easy way)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The easy way:
Resolving all dependencies fixed it.
The TAPI components are probably what did it...
I began disabling the TAPI components after I had tested this
before...

I think the larger lesson for me here is:
always try a fully resolved build first.

SteveS
StevesATeyeDASHimagingDOTcom






steves wrote:
> KM
> - Thanks for your questions.
> The art of asking the right questions is a big step in seeking
> solutions.
> - I am trying a build with the TAPI components enabled right now, and
> will report back soon. (Also, answers to your previous ???s are
> interspersed with your reply, below)
>
> One higher level question, so that I can learn more myself: Did you use
> your 'Dependency Explorer' to generate your guesses as to which
> components might need to be added? or are they just based on
> experience?
>
> As I think about it right now, I could probably have identified the
> component that brings in the 'Remote Access Auto Connection Manager'
> service by myself, and then looked at it's dependencies...
>
> SteveS
> StevesATeyeDASHimagingDOTcom
>
>
> KM wrote:
>
> > 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?
>
> a) Connect via computername gives message:
> The client could not connect to the remote computer..
> Remote connections might not be enabled, or the computer might be
> too busy to accept new connections...
>
> b) If I open the Options Box I See the Remote User name that I want
> to use to connect with a domain of the computer name, and I have
> tried every combination of Name, Username, password, and domain
> settings that I can think of...
>
> > - Can you ping the XPe device from any other machine (e.g., from XP Pro computer)?
>
> Yes, and IPConfig on both machines shows valid DHCP addresses
> within the range normally assigned by our server
> (10.0.0.106, 10.0.0.108)
>
> Ping succeeds in both directions using Netbios names..
>
> > - Are you trying to connect to XPe device using its netbios name or direct IP?
>
> Successful connect from XPE to XP Pro using netbios name.
> Failed both ways from XP Pro to XPE.
>
> > - What Logon component is your image based on - Winlogon or MinLogon?
>
> Winlogon - (Darn it - I knew to mention that!)
>
> > - Did you resolve all the included component dependencies in TD?
>
> Yes - However I have some things disabled, notably Outlook Express,
> DirectX,
> IIS, TAPI components, Windows Media Player.... I will try
> a build without
> those things disabled...
>
> > 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 (PRESENT)
> > - add TAPI components such as
> > "TAPI Performance DLL",
> > "Primitive: Tapi32" (PRESENT)
> > and "Telephony"
>
> Hmm -- See above answer.... Good Guess, I'm betting?
>
> Enabling 'Tapi 2.2 Client', and 'Telephony', and a few others...
>
> > - add "IP Router Monitor Library" component (PRESENT)
> > - add "Dial-up Client for Windows", (PRESENT)
> > - "Dial-Up Networking Common Libraries", (PRESENT)
> > - "Dial-up Server for Windows " (PRESENT)
> > 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
> > >

.

Quantcast