Remote desktop connection logs off immidiatly after log on

On Fri, 2 Apr 2004 09:01:05 -0800, "=?Utf-8?B?SmFyZWQ=?="
<NOSPAMjareda@ez-net.com> wrote:

>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.

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?

--


This posting is provided "AS IS" with no warranties, and confers no rights.



"Jared" <NOSPAMjareda@ez-net.com> wrote in message
news:3A88AA5D-FA30-4DD4-8B86-A3F185B02736@microsoft.com...

> Did anyone ever find a resolution for this problem?
>
> Jared

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.

"Huei Wang [MSFT]" <hueiwang@online.microsoft.com> wrote in message
news:%23dgdTERGEHA.3764@TK2MSFTNGP12.phx.gbl...

> 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?
>
> --
>
>
> This posting is provided "AS IS" with no warranties, and confers no

rights.

>
>
>
> "Jared" <NOSPAMjareda@ez-net.com> wrote in message
> news:3A88AA5D-FA30-4DD4-8B86-A3F185B02736@microsoft.com...

>
>

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

"Huei Wang [MSFT]" <hueiwang@online.microsoft.com> wrote in message
news:%23dgdTERGEHA.3764@TK2MSFTNGP12.phx.gbl...

> 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?
>
> --
>
>
> This posting is provided "AS IS" with no warranties, and confers no

rights.

>
>
>
> "Jared" <NOSPAMjareda@ez-net.com> wrote in message
> news:3A88AA5D-FA30-4DD4-8B86-A3F185B02736@microsoft.com...

>
>

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.

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!!!

i also have the same problem as you guys

"Jared" <jareda@ez-net.com> wrote in message
news:64D3603B-AD8C-4A1B-8A0A-9CEFAB1D83F0@microsoft.com...

> 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\Servic es\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.

>
> For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

>

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

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