Remote desktop connection logs off immidiatly after log on

[dvir]

Hello

I have a home network between two computers which are
running windows XP pro.

When I try to log on from one computer to the other using
remote desktop connection, the connection logs off
immidiatly after log on.

Can someone please tell how to prevent this from happening?

Thanks

Dvir

 

[Huei Wang [MSFT]]

Any eventlog? Any software you installed on your machine? what's machine CPU
speed, memory size, ...?

 

[kirby]

I have the same issue.

I went so far as to connect the systems with a crossover
cable to eliminate any problem between the boxes, and
what I found is that if I'm not logged in as the user my
system won't connect. Try that and see if it helps.

I've got another thread open that will hopefully yield a
solution, and will forward it if one becomes available.

I have my logs set to log everything, and nothing of any
use comes up. Only thing that looks weird is that the
GPO is failing to work. I don't have one set up, but
could this be the cause?

If I log in to the system, I can connect remotely and do
everything except log off and it will work fine. Log
off, and I can't log back in to any of the accounts on
the box.

My system is XP Pro all current patches, 3.2G HT CPU,
1Gig RAM, 1.5/1.0 DSL connection with Zonealarm pro
running (I've tried disabling it to no avail)

Any help would be appreciated.

 

[Huei Wang [MSFT]]

Any error message on GPO failing, can you check if you have "Log user off
when roaming profile failes" GP set, does it work if you create/use another
user account?

 

[Guest]

Both of my machines are home machines so I'm not using
group policies at all. Same effect on every account I
create. Log on/Log off.

 

[Guest]

I'm also having this problem. I have a fresh install of Windows XP Pro and am all patched up

I did find an article that directed me to delete the Certificate value from [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters], and that seemed to work for a while, but by the end of the day, it was back at it. I've also tried getting in with my Administrator account, but yielded the same result

Below are the entries showing up in my event log

Event Type: Erro
Event Source: Useren
Event Category: Non
Event ID: 106
Date: 3/30/200
Time: 6:17:48 P
User: NT AUTHORITY\SYSTE
Computer: FIZBA
Description
Windows ended GPO processing because the computer shut down or the user logged off

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

Event Type: Erro
Event Source: Useren
Event Category: Non
Event ID: 108
Date: 3/30/200
Time: 6:17:49 P
User: NT AUTHORITY\SYSTE
Computer: FIZBA
Description
Windows cannot set the background refresh timer for Group Policy. WaitForMultipleObjects (The handle is invalid. ). Group Policy processing aborted.

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

 

[Bob]

Did anyone ever find a resolution for this problem?

Yes, get UNIX.


--

Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/

You know you are in Hell when you have to make a
distinction between what is moral and what is legal.

 

[Huei Wang [MSFT]]

There are some posting on other newsgroup regarding this issue, it looks
like latest
nVidia driver causing this problem, do you have nVidia driver on your
machine?

 

[Brendan Perez]

I'm having this same problem. It's limited in how it works(Fails) and yes I
have an Nvidia, latest driver downloaded april 1, 2004.

If I restart the PC and try to connect remotely using any account but the
builtin local admin, I'm immediately logged off. I tried conenctiing my
other admin account as well as a power user w/RD privs to the consolse
session mstsc -console, this was also unsuccesful. I can establish a
connection to the remote PC using the local admin and then remote to the
console session using the account I want tp use and this works. Logging in
at the workstation and the remoting to it has no issues whatsoever.

I'm going to disable the nvidia driver service and downgrade my Nvidia
driver and will report the results of each one momentarily.

 

[Brendan Perez]

Disabling the NVidia Driver Service will fix the problem, but I don't know
what effect that has on anything else.

 

[Third_of_Five]

I have the same problem. If I reboot my PC (so that its no longer
logged on) I can no longer connect to the box using RDC, it starts
loading profile, then starts logging off and the RDC closes.

I am running the very recent nVidia drivers (v 56.64).

If I disable (not just stop, but disable) the nVidia service, I can
then log in using RDC.

 

[Guest]

Hello all

Wah - thanks very much for the fix! I'll disable the nVidia driver help service, and hopefully the next Detonators don't have this problem. Thanks again!!!

 

[Sean]

i also have the same problem as you guys

I'm also having this problem. I have a fresh install of Windows XP Pro and am all patched up.

I did find an article that directed me to delete the Certificate value

from
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters
], and that seemed to work for a while, but by the end of the day, it was
back at it. I've also tried getting in with my Administrator account, but
yielded the same result.

Below are the entries showing up in my event log:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1068
Date: 3/30/2004
Time: 6:17:48 PM
User: NT AUTHORITY\SYSTEM
Computer: FIZBAN
Description:
Windows ended GPO processing because the computer shut down or the user logged off.

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

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1082
Date: 3/30/2004
Time: 6:17:49 PM
User: NT AUTHORITY\SYSTEM
Computer: FIZBAN
Description:
Windows cannot set the background refresh timer for Group Policy.

WaitForMultipleObjects (The handle is invalid. ). Group Policy processing
aborted.

 

[Jerome@Neotek]

After many hours of frustration I have the answer. You do not need to
revert to a previous version of nVidia drivers, just disable the
nVidia Display Driver service.

This can be done from within Administrative Tools, Services

 

[Guest]

Had the exact same problem...recently like everyone else...disabled the nvidia driver...worked as soon as I did that. Thanks for the advice..
Hector V
Houston, T
A+, Network+, MCP, MCSA