Remote Connections Time out and cannot reconnect

[ReneeColorado]

Here's the situation. I am running Terminal Services on a Windows Server
2003 OS. We have 3 remote locations that are using Remote Desktop Connection
to get into the terminal server. Each location has at least 2 Remote Desktop
Connections running at one time. Everything has been running fine (for about
a year and a half) until about 3 weeks ago. About once every week all of the
remote users at each of the remote locations lose connectivity. The message
states "the connection has timed out - please try again". When they try
again, it acts as if it is going to connect, but it will not reconnect. I
have rebooted the server everytime to get them back up and running. I
haven't had any errors recorded in the event log, and I have checked all of
my terminal server settings. Any ideas as to what could be happening? It's
very odd that they all get the same error at the same time, because they all
sign on at various times in the morning. Any suggestions would really be
appreciated.

Thanks,

[Vera Noest [MVP]]

Since this happens to all users simultaneously, the cause must lie
inside the TS itself, or some network component close to the TS.

Next time this happens, can you ask users if they still can ping
the Terminal Server? And can you check if the server is still
listening on port 3389 (with netstat)?
And how about connections over the LAN? Are they also disconnected?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?UmVuZWVDb2xvcmFkbw==?="

Post by ReneeColorado
Here's the situation. I am running Terminal Services on a
Windows Server 2003 OS. We have 3 remote locations that are
using Remote Desktop Connection to get into the terminal server.
Each location has at least 2 Remote Desktop Connections running
at one time. Everything has been running fine (for about a year
and a half) until about 3 weeks ago. About once every week all
of the remote users at each of the remote locations lose
connectivity. The message states "the connection has timed out
- please try again". When they try again, it acts as if it is
going to connect, but it will not reconnect. I have rebooted
the server everytime to get them back up and running. I haven't
had any errors recorded in the event log, and I have checked all
of my terminal server settings. Any ideas as to what could be
happening? It's very odd that they all get the same error at
the same time, because they all sign on at various times in the
morning. Any suggestions would really be appreciated.
Thanks,

[ReneeColorado]

Thank you Vera,

I will try all of these things the next time that it happens.
--
Renee

Post by Vera Noest [MVP]
Since this happens to all users simultaneously, the cause must lie
inside the TS itself, or some network component close to the TS.
Next time this happens, can you ask users if they still can ping
the Terminal Server? And can you check if the server is still
listening on port 3389 (with netstat)?
And how about connections over the LAN? Are they also disconnected?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___
"=?Utf-8?B?UmVuZWVDb2xvcmFkbw==?="

Post by ReneeColorado
Here's the situation. I am running Terminal Services on a
Windows Server 2003 OS. We have 3 remote locations that are
using Remote Desktop Connection to get into the terminal server.
Each location has at least 2 Remote Desktop Connections running
at one time. Everything has been running fine (for about a year
and a half) until about 3 weeks ago. About once every week all
of the remote users at each of the remote locations lose
connectivity. The message states "the connection has timed out
- please try again". When they try again, it acts as if it is
going to connect, but it will not reconnect. I have rebooted
the server everytime to get them back up and running. I haven't
had any errors recorded in the event log, and I have checked all
of my terminal server settings. Any ideas as to what could be
happening? It's very odd that they all get the same error at
the same time, because they all sign on at various times in the
morning. Any suggestions would really be appreciated.
Thanks,