Remote Not working while not logged in

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hey folks For some odd reason my Client (home) PC Will not allow Remote
Desktop to access it unless im physically logged into Windows. I set my user
account up in the Remote Desktop Group. Opened the ports on my Router Set up
a permanant Private IP Address on my PC and all that jazz so nothing would
change incase of power failure or something... But i can not for the life of
me get access to the PC unless im already logged on. Why? Does anyone know?
Its beginning to drive me insane. Simply because i would love to access my
Home PC while at school but i wont leave my user name logged in. Any
suggestion would be great. Thanks
 
On Mon, 28 Mar 2005 20:23:03 -0800, TFredrickson wrote:

I have the same symptoms but no solution. Let's compare notes.
In addition to RDC not working if the host account is not already logged
on, another symptom I have is that after a disconnect, RDC cannot
(re)establish a session with the host until it has been rebooted. Please
read post "RDC working-one session per boot(MDBJ)". Can you post your host
and client operating system version and level, and identify any firewall or
antivirus software. I am using Windows XP Pro SP2, Outpost Firewall, Norton
Antivirus 2005, and a D-Link Router/Firewall. There has to be something
unique about our setups or else this problem would reported more
frequently.
 
OK... Host PC has XP Pro SP2, eTrust AV, and a Trendnet Router. I've set the
Router up so it opens the Port That I've specified for RDT and the only other
firewall I have is the Windows Firewall. One Client is XP Home with Norton
2004 AV and No Router or Firewall as far as i know. Another Client is a PC
on campus XP Pro SP2. Its on a Domain so that Might be a prollem but I've
seen others RDT soooo... Other than that I've done Everything i know of for
RDT....
 
On Thu, 31 Mar 2005 12:39:03 -0800, TFredrickson wrote:

The poster of "Can't connect until remote computer logged in...(Al) made an
interesting comment. He thought that "the remote service is not started
until someone first logs on". That got me thinking. For security reasons,
some PC users, including myself, either disable or set the Terminal Service
to manual. I set mine to manual but I was not sure what that meant. I
thought that it meant that I had to open the service management screen and
manually start the service. But that can't be right because after I logon,
the service has been started. So it is possible that something else, like
the logon, causes the service to start. To confirm this, one would have to
see the terminal service status of the host PC before the first logon. I
don't know if there is a way to establish this status except for an
external test. I don't know if there is a direct relationship between RDC
port 3389 listening and the start of the service. I will do some tests to
follow up on this theory. In the meantime could you check your Terminal
Services start setting. Is it on Automatic or manual?
To try to eliminate some variables, I noticed that both Al and yourself are
setting up RDC access across the "network". Just to be sure we are using
the same testing condition, to try to reduce the chance that maybe router
firewall filtering is interfering with the connection, I do my tests with
the router disconnected from the Internet, and both the client and host on
the same subnet. In other words, I am duplicating the problem on the local
network. I may be wrong but I think that under those conditions it is not
necessary to ensure that port 3389 is opened on the router to the host. I
think I have proven that on my router by being able to set up RDC
connections between both PC, alternating client and host, without any
special setup considerations on the router. So my question is, can you
duplicate the problem locally?
 
Back
Top