Terminal Services sessions timeout?

I used to remotely administrate a Windows 2000 server with TightVNC.
With TightVNC, I could log onto the server and start processes that
run in DOS windows, lock the server and disconnect. I could then
reconnect later on to the same session.

Since the server was rebuilt, I am having to use Remote Desktop from a
Windows XP client to administer the server. The problem with this is
that it appears that these Remote Desktop sessions are timing out. I
say this because when I remotely connect to the server I find no
evidence that the processes that run in DOS windows are still
running. The DOS windows have disappeared, and when I start the
processes they begin a catch-up process that would not be necessary
had they been running continuously.

I have tried reinstalling TightVNC as a system service, but when I
reboot the server and attempt a connection, I am informed that the
server does not have a password set and until one is set I won't be
able to connect to it. This is spite of having set the password!

Any thoughts on the solution to either the Remote Desktop or TightVNC
problem would be most gratefully received!

These settings are controlled on the terminal server.
Start|Run|%SystemRoot%\system32\tscc.msc /s


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

<alex.birchall@gmail.com> wrote:
>I used to remotely administrate a Windows 2000 server with TightVNC.
> With TightVNC, I could log onto the server and start processes that
> run in DOS windows, lock the server and disconnect. I could then
> reconnect later on to the same session.
>
> Since the server was rebuilt, I am having to use Remote Desktop from a
> Windows XP client to administer the server. The problem with this is
> that it appears that these Remote Desktop sessions are timing out. I
> say this because when I remotely connect to the server I find no
> evidence that the processes that run in DOS windows are still
> running. The DOS windows have disappeared, and when I start the
> processes they begin a catch-up process that would not be necessary
> had they been running continuously.
>
> I have tried reinstalling TightVNC as a system service, but when I
> reboot the server and attempt a connection, I am informed that the
> server does not have a password set and until one is set I won't be
> able to connect to it. This is spite of having set the password!
>
> Any thoughts on the solution to either the Remote Desktop or TightVNC
> problem would be most gratefully received!