remote desktop won't work...TS MVP suggested I post here.



Ok, I'm posting here after the suggestion from a MVP in Windows
Server/Terminal services.

I can't seem to get remote desktop to work. Obviously I'm pretty
inexperienced with it

I'm posting at the bottom the 4 (in sequence) events I get that I believe
are related.

This is my home network. Same subnet. Desktop (host) is running XP
professional, other machine (laptop/client) is running xp home. Yes, both are
sp2.

When I try to remote access in I get the following error message on the
client.

"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. It is also possible that network problems are preventing your
connection"

I have traced the problem to what I believe is this.

The terminal server service is not started and won't start on the host. Yes
even if I try to manually start it. I get an error message.

"Could not start the terminal server service on local computer. Error 1068:
the dependency service or group failed to start"

Environment:

Host is xp pro sp2 (desktop)

Client is xp home sp2 (laptop)

Cable internet connection with router installed and enabled for port 3389
and 80.

Troubleshooting:

This should not matter since both machines are on same subnet but I'll state
it anywise. I HAVE!!! Already physically disconnected the router/firewall
from the network. Connected; desktop (host) directly to cable modem,
verifying that I could establish and maintain and be pinged from the outside
(put laptop on separate...neighbors...wireless network) and pinged
successfully my desktop (host). Then tried to remote desktop in.

Result: same problem or error message.

I've traced the dependency services to one that was not running.” Net
Logon". It was set to manual. So I tried starting it manually (in
services)........I get the following error message.

"The net logon service on the local computer started and then stopped. Some
services stop automatically if they have no work to do, for example, the
Performance logs and alerts service."

The net logon services dependency is the workstation service ........it is
running.

I've rebooted the machine, I've turned the net logon on service to automatic
and rebooted. Etc. etc. Doesn't help.

In researching I've discovered (been reminded) that the net logon service is
designed for domain environments; since I'm in a workgroup (thus) I'm
assuming it shuts down at the end of the boot sequence (or something) when it
discovers there is no domain. My guess would be that a remote desktop
connection wakes the net logon service to just.....service (sorry for the
redundancy) the logon attempt.

So why can't I get it to come on. Or am I going completely down the wrong
path.

Yes I have a software firewall installed also on both machines. Zone alarms.
Yes it’s turned OFF (as opposed to "disabling" it) when trying to
troubleshoot the above.

Here is the event log sequence that cycles with the issue.

Event 1:


Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 3095
Date: 6/21/2006
Time: 1:54:47 PM
User: N/A
Computer: XPPRO
Description:
This computer is configured as a member of a workgroup, not as a member of a
domain. The Netlogon service does not need to run in this configuration.


Event 2:


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 6/21/2006
Time: 1:54:47 PM
User: N/A
Computer: XPPRO
Description:
The Terminal Services service depends on the Net Logon service which failed
to start because of the following error:

Event 3:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 6/21/2006
Time: 1:54:47 PM
User: N/A
Computer: XPPRO
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The dependency service or group failed to start.

Event 4:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 6/21/2006
Time: 5:21:02 PM
User: N/A
Computer: XPPRO
Description:
The Terminal Services service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid
for the account name specified.


I don't understand this last one, is this generated when I try to access the
host (I get no prompt at the client regarding anything)? I'm using the same
creditials (user id, password) when trying to access the host remotely as
when I do it locally.

I know I'm doing something (or not doing) something basic. I also know I'm
not stupid, probably just need a second pair of eyes. Unfortuantly I'm at
home without a second set of I.T. eyes to depend on. Your assistance is much
appreciated.



Questions or clarifications?


.



Relevant Pages

  • RE: Remote Desktop/Term. Serv information leakage
    ... connection settings for your given connection, ... ability to have your hard drive mapped on the remote host. ... They asked us to test if the isolated network was adequately ...
    (Pen-Test)
  • RE: PCanywhere: security of it and operation over DSL/cable modems
    ... I have had PC Anywhere running over a VPN connection quite happily. ... However I have setup laptops for remote support running PC Anywhere before, ... By giving both the host and remote PC Anywhere packages the ... have any better encryption on the communication link then definitely use it. ...
    (Security-Basics)
  • Re: remote connection not always available with PCAnywhere, XP
    ... I don't know what's happening with PCAnywhere, ... Have you considered trying Remote Desktop instead--to see whether it works ... > server for the business software is our PCanywhere host. ... > is that PCAnywhere is waiting to make a connection. ...
    (microsoft.public.windowsxp.work_remotely)
  • Strange Error?
    ... After installing SP4 on our company SQL200 Standard Server, ... An existing connection was forcibly closed by the ... remote host. ... This normally results if the peer application on the remote ...
    (microsoft.public.sqlserver.security)
  • Re: Connecting a remote workstation to a domain
    ... If you have more than a couple of remote workstations connecting to the SBS ... server via VPN, you really need to consider a Terminal Server in the main ... "Log in using a dial up connection" checkbox, ... roaming profile then synchronizes with the server over the VPN); ...
    (microsoft.public.windows.server.sbs)