Re: Error messages for remote desktop connection attempt

Mmm, that's really strange.
I would post this in the microsoft.public.windowsxp.work_remotely
newsgroup, because chances are that this problem is specific to XP.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?VHJlYXN1cjI=?= <Treasur2@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 22 jun 2006:

Yes, I've double, triple checked even rebooted making sure
remote desktop was checked.

Your comments about terminal service as a dependcy is what
confuses me. I thought it depended on the RPC service
also.....but heres my event log error message.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 6/21/2006
Time: 5:20:50 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:
%%0

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

"Vera Noest [MVP]" wrote:

Did you enable Remote Desktop connections on the XP Pro host?
In Control Panel - System - Remote?

If that doesn't fix it, have you checked the EventLog on the
host?

FYI, on my XP pro client, the Terminal Services service is
dependent on the Remote procedure Call service, not on the
NetLogon service.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?VHJlYXN1cjI=?= <Treasur2@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 21 jun 2006 in
microsoft.public.windows.terminal_services:

Ok, I can't seem to get remote desktop to work.

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.

Questions or clarifications?
.

Relevant Pages

  • Remote Desktop Disconnect
    ... precisely the time you attempt a connection, ... receive the following error message: ... The terminal server cannot issue a client license. ... >Remote Desktop Disconnected ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Unable to RDP
    ... Which error message do you get? ... Terminal Server and are you trying to connect from within Terminal ... I am able to ping and browse to the remote ... land and I am also able to remote to other computers from the ...
    (microsoft.public.windows.terminal_services)
  • Re: Easiest way to share existing files saved on SBS server with remote users?
    ... on a SBS machine to a server-less remote office? ... The best method is Terminal Server, no matter what else, it's the only ... The key reason for terminal server is the savings in support, security, ...
    (microsoft.public.windows.server.sbs)
  • Re: Getting rid of old, obsolete kernels
    ... > to login via terminal server, enter user/password, hard reset the ... LILO and make the system unrecoverable without a boot disk. ... You need a remote serial concentrator to do this effectively. ... Some of the higher end ones support SSH now, ...
    (comp.os.linux.setup)
  • Terminal server keeps expirering
    ... in remote admin you need a licencing ... By installing programs on a terminal server, ... without requiring Terminal Server Licensing. ... >Wizard to install and configure a terminal server. ...
    (microsoft.public.windows.server.general)