Only the PC Clients get disconnected???

[Guest]

I have a Windows 2000 Server running terminal services that my PC users have
a problem staying connected to. Once the PC users connect to the RDP Session
and leave it idle for a undetermined amount of time - they get dissconnected
from their session. The oddity is that all of the users using Thin Clients
have no problems staying connected, even when idle.

The Server is a new Dell Poweredge with Intel NICs multihomed for a LAN and
Wan. The Wan is a DMZ to the SonicWall firewall. I Have all of the RDP
sessions configured so that is not the cause of the disconnects. I am
starting to grasp a straws. The event viewer shows no errors and their are
plenty of licenses for Windows and Terminal Server CALS (Per Seat)

The server is a member server to a domain and the computer itself has been
placed in a group policy in Active Directory to lock down the entire server.
I have removed the group policy and still receive the same disconnect.

All of the branch offices connect over T1s using SonicWall TZ170s (VPN
Connection) to the host SonicWall 3060 Connecting to the internet via OC3.
Our connectivity is solid for the datacenter and have had no connectivity
problems form the branch offices either.

I am convinced that there is something wrong with the server itself, but I
am open to any suggestions.

Thank you in advance!!!!!!!!!!!!

Chris

 

[Vera Noest [MVP]]

Are your thin clients on a different network as your PCs?
If so, it could well be that there is a router between your
clients and your server, which sees no traffic and decides that
the session must have ended and throws it out. The solution in
that case is to enable KeepAlives. For the correct registry key,
check:

216783 - Unable to Completely Disconnect a Terminal Server
Connection
http://support.microsoft.com/?kbid=216783

Also check this link:
http://terminal.servebeer.com/php/flaky_connections.php

 

[Guest]

Their are 11 branch locations that have a combination of PC's and Thin
clients. The disconnects occur at each of the branch locations. Each Branch
location is connected via a full T1 and the PC's and Thin Clients at each
branch use their repective same circuit. I think that if it was a keepalive
problem that it would effect both thin clients and PC's.

Let me know if you need any more info.

 

[Vera Noest [MVP]]

I agree, if the thin clients and PCs are mixed, then KeepAlives is
probably not the solution.

This is a long shot: how are the Power Management settings on your
PCs? Is it possible that they go to sleep and cause a disconnect
in that way?

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

 

[Guest]

All of the power management features are "off". We do not allow the monitor
to turn off, no Hibernate, No disks get turned off, and I have the NICs set
so that they
can not turn this devise off to save power.

I am still thinking that there is a problem with the terminal server itself.
Last night I stopped the Terminal Server Licensing server and removed the
LServer folder. Then I recreated the folder and started the server. I then
re initialized the open licenses for the Per Device (40 CAL), just to rule
out that there was any licensing issue. The problem is still occurring with
the PC's only at no specific times. I have a network monitor that verifies
that there are no breaks in the connectivity and my event viewer has NO red
or Yellow warnings. (That is a first) I am becoming desperate as this is
causing my client to become very frustrated. Again I appreciate any help.

Chris

 

[Vera Noest [MVP]]

A licensing problem can never cause this, since the licensing
situation is only checked at logon time, and not during the rest
of the session.
I've run out of ideas, but I know what I would try in your
situation. I'd implement KeepAlives anyway, just for
troubleshooting purposes. You've got nothing to loose, and even if
it doesn't work, you would have ruled out yet another possible
area of potential problems.

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

 

[Guest]

I have been looking around on the server and noticed the Jumbo framing is
enabled on the NIC. Do you know if there are any known conflicts with the
Intel Pro/1000MT NIC and Terminal Services. Also I have set the default MTU
to 1492.

If you or any one else have any more suggestions, they are all welcome. We
are monitoring the packets that are sent and referencing them to the users
that are being disconnected to see if there are any network problems. So far
so good on the network connection.

I know there has to be a fix - it is just a computer.

Thanks again for the help.