Remote Desktop available only when the account is logged in?

  • Thread starter Thread starter Kirby
  • Start date Start date
K

Kirby

This just started happening on my system, and I have no
idea what's causing it. Hopefully someone can throw a
clue my way.

I have an XP Pro desktop, latest SPs running ZoneAlarm as
a firewall. I've opened the system to port 3389 UDP/TCP
from my office IP, or from an internal IP on the trusted
side (10.0.0.*), and NAT'd 3389 from the external IP to
the box on the DSL router. (Cisco 678)

All of a sudden, whether I'm at work or at home, I have
to be logged into the PC with the account I have set up
for remote access. If I log off I can no longer connect
to the box until I physically log in again at the box.
(which is tough to do from the office). If I disconnect,
the session remains.

My question is: It didn't start doing this until this
weekend, and no settings have been changed except to tell
it not to use my local printer, and that was about two
weeks ago.

The account has admin rights, so according to the MSKB it
should be able to establish a connection at any time.
It's been working for the past several months without a
hitch. VNC always connects, but doesn't work as well as
Remote Desktop seems to.

Any suggestions as to the cause? Please send to the
address above.

Thanks in advance.

KB
 
As a PS, it does load the desktop, but a message flashes
by so quickly I can't tell what it says. On the actual
machine you see the user status change from logged in, to
logged out.

Thanks!
 
Nope.

Nothing that helps anyway.

KB

-----Original Message-----
Any thing in event log?

--


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






.
Click to expand...
 
No.

Any account has to be logged on first. Otherwise it
connects, logs in and logs out. Same with every account
including new ones.

No errors in ZoneAlarm, nor in the event logs.

Weird, since it worked fine up until a few days ago.

KB
 
It might be some critical process that fail early on during logon, can you
try "drwtsn32", this will brings up "dr. watson" setup, the important things
is "the log file path", set it to some directory you know, then try remote
desktop again, after that, check the log file see if it catch anything.
 
Nope, nothing failing.

Set up drwtsn32 to log everything, and fired up the
remote desktop without logging in. No errors, same
result. Tried all of my accounts, and made two new
ones. Same result.

Frustrating, but I made a workaround by using VNC to log
in, then swithing back to RD.

It's obviously not functiong properly, so is there
anything that a past patch or update may have caused?
Also just for fun, I fired up Win 2k Terminal servces on
another box and placed it on a different port. Works
perfectly.

Anything else to try?
 
There are some posting on other newsgroup on this issue, looks like latest
nVidia driver causing this problem, do you have nVidia driver on your
machine?
 
Back
Top