Remote Desktop Connection no longer working ...

[steves]

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

 

[KM]

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

 

[steves]

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

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

 

[steves]

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

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

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

 

[steves]

So, while I was waiting for my painfully slow Target Designer, that I
have spent four days trying to fix, and finally concluding that i need
to reinstall XP, which i have been unwilling to do...

I tried to think how I could have resolved this myself. I guess what
I'm wondering is, 'What would KM do' to solve this problem... How long
should I bang my head against the wall before going to the newsgroup?

So, I am presenting the steps that I took as a possible educational
device for others, and would welcome any comments, such as 'that is way
too much work, why didn't you just resolve the dependencies', or 'you
are on the right track, but since you don't understand device driver
development and installation/windows architecture, you missed the fact
that ___. 'Read this book ____'. Or, 'This is how I approach these
problems'...




-------------------------------------------------------------------------
Problem: Remote Desktop Connection Not Working:
-------------------------------------------------------------------------

STEP 1) Compare services on XP Pro and XPE installation
-------------------------------------------------------------------------
Discover that 'Remote Access Auto Connection Manager is not working.
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"

Examine the service properties:
Startup Type: Manual, Will not start on XPE System only
The service manager properties claims that there are no
dependencies.
Path to executable is C:\Windows\System32\svchost.exe -k netsvcs

STEP 2) Try to locate the service executable
------------------------------------------------------
On xp pro search for files named 'netsvcs' - 'NetSvcs.inf'

On xp pro search windows\ for files containing text 'netsvcs'
This locates several .inf files, notably 'netrass.inf', 'netserv.inf'

Hmm file - 'NetRass.inf' contains text 'Remote Access Connection
Manager'

How about if I look at the 'Services' Key in the registry?
On XP Embedded:
Browse - [HKLM\System\Current Control Set\Services]
Search for 'Remote Access Connection Manager' in data

Gets me to key 'RasMan'
What's this? 'DependOnService'=Tapisrv ??
That didn't appear in the depends on list!

-------------------------------------------------------------------------
STEP 3) Look at Telephony service in XPE system.
-------------------------------------------------------------------------
a) Located 'Telephony' service on XP Pro
obtain filename 'Tapisrv.dll' from properties.
b) copied tapisrv.dll from XP Pro to XP embedded
c) Attempted Regsvr32 tapisrv.dll (Failed)
d) Copied HKLM\System\Current Control Set\Services\TapiSrv
registry branch from XP pro to XP embedded

After restarting the computer, I can have a working 'Telephony'
service, and can now start the 'Remote Access Connection Manager'
service on the XP Embedded system. I have made some progress!

However - Remote Desktop Client still didn't work at that point, so I
went ahead with the full resolved build - which fixed the problem.

Potential Problem: Copying the 'Service' key only to the 'Current
Control Set' branch leaves me with a possible problem of what about the
other control set...

-------------------------------------------------------------------------
WHAT DID I LEARN?
-------------------------------------------------------------------------
a) ALWAYS - when stuck - TRY A FULL BUILD WITH ALL DEPENDENCIES
RESOLVED!

Was this excercise valuable? I'm not sure. Comments?

steves
stevesATeyeDASHimagingDOTcom.

**Again, Thanks KM... **

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

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

 

[KM]

steves,

Nice tutorial !

Actually many of us here follow similar process while resolving issues with their XPe images.
Search is one of the tools we have to use daily while working with XPe since it includes too many components and it is impossible to
keep them all remembered.

Answering some of your earlier questions.
With regards to the RasMan I just knew the TAPI relevance to it so I suggested to add the TAPI related components. (in other words,
I was not guessing in that post)

Unfortunately it is one of the current biggest issues of XPe componentization - some [most] components are not broken down in their
dependencies good enough to be able to minimize image footprints.


Although I do use the 'Dependency Explorer' very often it is not the way to answer all questions. But it gives me more and more
information about various XPe components every day (well.. it is >12,000 components in database - I will keep myself busy for a
while ).

Another good approach to investigate some XPe issues is to use the fully blown image that includes all software components of XPe -
XPProEmulation project. You can find the SLX and instructions on how to use it (adopt it for your platform) on www.xpefiles.com.

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

So, while I was waiting for my painfully slow Target Designer, that I
have spent four days trying to fix, and finally concluding that i need
to reinstall XP, which i have been unwilling to do...

I tried to think how I could have resolved this myself. I guess what
I'm wondering is, 'What would KM do' to solve this problem... How long
should I bang my head against the wall before going to the newsgroup?

So, I am presenting the steps that I took as a possible educational
device for others, and would welcome any comments, such as 'that is way
too much work, why didn't you just resolve the dependencies', or 'you
are on the right track, but since you don't understand device driver
development and installation/windows architecture, you missed the fact
that ___. 'Read this book ____'. Or, 'This is how I approach these
problems'...




-------------------------------------------------------------------------
Problem: Remote Desktop Connection Not Working:
-------------------------------------------------------------------------

STEP 1) Compare services on XP Pro and XPE installation
-------------------------------------------------------------------------
Discover that 'Remote Access Auto Connection Manager is not working.
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"

Examine the service properties:
Startup Type: Manual, Will not start on XPE System only
The service manager properties claims that there are no
dependencies.
Path to executable is C:\Windows\System32\svchost.exe -k netsvcs

STEP 2) Try to locate the service executable
------------------------------------------------------
On xp pro search for files named 'netsvcs' - 'NetSvcs.inf'

On xp pro search windows\ for files containing text 'netsvcs'
This locates several .inf files, notably 'netrass.inf', 'netserv.inf'

Hmm file - 'NetRass.inf' contains text 'Remote Access Connection
Manager'

How about if I look at the 'Services' Key in the registry?
On XP Embedded:
Browse - [HKLM\System\Current Control Set\Services]
Search for 'Remote Access Connection Manager' in data

Gets me to key 'RasMan'
What's this? 'DependOnService'=Tapisrv ??
That didn't appear in the depends on list!

-------------------------------------------------------------------------
STEP 3) Look at Telephony service in XPE system.
-------------------------------------------------------------------------
a) Located 'Telephony' service on XP Pro
obtain filename 'Tapisrv.dll' from properties.
b) copied tapisrv.dll from XP Pro to XP embedded
c) Attempted Regsvr32 tapisrv.dll (Failed)
d) Copied HKLM\System\Current Control Set\Services\TapiSrv
registry branch from XP pro to XP embedded

After restarting the computer, I can have a working 'Telephony'
service, and can now start the 'Remote Access Connection Manager'
service on the XP Embedded system. I have made some progress!

However - Remote Desktop Client still didn't work at that point, so I
went ahead with the full resolved build - which fixed the problem.

Potential Problem: Copying the 'Service' key only to the 'Current
Control Set' branch leaves me with a possible problem of what about the
other control set...

-------------------------------------------------------------------------
WHAT DID I LEARN?
-------------------------------------------------------------------------
a) ALWAYS - when stuck - TRY A FULL BUILD WITH ALL DEPENDENCIES
RESOLVED!

Was this excercise valuable? I'm not sure. Comments?

steves
stevesATeyeDASHimagingDOTcom.

**Again, Thanks KM... **

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

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