RE: 2008 Terminal server stops accepting connections and is solved

It looks like the problem was indeed increased user load. When looking over
the server's performance counters, the memory on the machine was hovering at
100% utilization almost all the time. Memory was added (doubled) on the
machine and since then the utilization of the memory is continuously right at
or above the amount of memory that the machine had previously.... No new
software, no configuration changes, but more users at once. I guess, in
hindsight, this should have been clear from the start, but thanks Kristin for
pointing me in the right direction.

Tony

"Kristin" wrote:

Superstrange.

Ok. Prior to that week, did you update anything on the terminal server?
Install any patches for Windows/ Office / Outlook? What about any new
configuration changes to the system? Have you added any kind of load
balancing? Have you done anything new, no matter how seemingly small?

I am sure you have thought of this, but I have to ask: Have you added any
user load? If so, is it possible that your system does not have enough power
to keep up?

Can you keep a session open for yourself until the next problem occurrs -
this way you might be able to, for instance, use TS Manager to kill a problem
app for all users etc.

What is the interval of the issue? Does it happen around the same time
everyday, such as in the morning when users are all trying to log on, or when
some kind of office event may happen (like some task that users do?)

You may not have anything in the event logs around the time of the issue,
but its possible there could be some kind of warning sign. I would re-comb
through the logs too.

KLG

"A Converse" wrote:

The problem happened again, with a couple twists... maybe the extra
information will be helpful.

First of all, telnet would open and immediately close this time. Secondly,
when connected from the console I saw one session reporting its state as
"down". There were two processes associated with this down session:
Outlook.exe running as a user account (not listed as being connected) and
csrss.exe running as SYSTEM. while looking at the problem a second session
entered this state with the same associated processes (outlook.exe was
running as a different user). I could not kill the processes or manipulate
the sessions at all. I was unable to bounce the switch port this time, maybe
I'll be able to try that next time.

thanks,

Tony

"Kristin" wrote:

Hrm. That is a weird one. Can you bounce the switch port when this is
happening? I figure, your users are already having connection issues, and
people who are already connected will get reconnected when the port comes
back up. If you bounce the switch port, and then you can get on, you know
its caused by incoming connections.

I don't think you have a license issue. A license issue would not crash
your server. If you didnt have enough licenses, then the next user would
just not be able to log on. And it wouldnt slow up users that are already
connected.

Curious as to what you find. Hope this helps,

KLG


"anthony.converse@xxxxxxxxx" wrote:

Hi,

I have a Windows server 2008 terminal server that has been running
fine for quite a while. Over the past week, it has been having a
periodic problem where the server stops accepting new sessions. I
have per user licenses installed on the server and there are available
licenses and I am able to track that they have been issued. When the
problem starts, the performance on the server is degraded for those
user already connected, but they are not initially dropped. All new
connections receive the logon page, then after entering credentials it
takes a few seconds and then the message "This client cannot connect
to the remote server" is received. I am able to telnet to the machine
and I checked that sessions were ENABLED on the server while this is
happening. I can ping the machine as well. The time that the server
crashed as a result of this, there are no events in the system log or
the event log for the 7 minutes between the crash and the reboot
starting. What steps can I take to try and troubleshoot this problem?

thanks,

Tony

.

Relevant Pages

  • Re: Configure SBS Remote Desktop for one session ONLY, BUT not locking new connection attempts
    ... Sorry, Russ, but the /console switch only connects if the server ... I log on to my own session in the server, from another workstation, ... Once at the remote site, I figure I need access to some data that I ... connections limit (whenever you're able to connect with an already ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Timeout problem
    ... the amount of buffer pool memory allocated to SQL Server ... and the amount of freely usable MEM TO LEAVE memory to use for connections. ... > The results for the "BlkBy" spid is the same. ...
    (microsoft.public.sqlserver.server)
  • Re: maximum number of sessions
    ... NAS and SAN storage devices generally run one of the free Linux ... that's also two connections. ... like to know why mapping to an ip address creates an additional session to ... We have 6 pcs connecting to a 7 pc we call our server. ...
    (microsoft.public.windowsxp.network_web)
  • RE: 2008 Terminal server stops accepting connections and is solved
    ... There were two processes associated with this down session: ... its caused by incoming connections. ... If you didnt have enough licenses, ... I have a Windows server 2008 terminal server that has been running ...
    (microsoft.public.windows.terminal_services)
  • RE: Trouble with huge amount of State Server Sessions Timed out
    ... "Unable to serialize the session state. ... > State Service or SQL Server can be memory intensive depending on the types ...
    (microsoft.public.dotnet.framework.aspnet)