<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Windows 2003 Terminal Service sessions will not logoff</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/windows-2003-terminal-service-sessions-will-not-logoff/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/windows-2003-terminal-service-sessions-will-not-logoff/</link>
	<description></description>
	<pubDate>Mon, 09 Nov 2009 11:33:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: klick1</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/windows-2003-terminal-service-sessions-will-not-logoff/#comment-42882</link>
		<dc:creator>klick1</dc:creator>
		<pubDate>Wed, 22 Dec 2004 16:14:48 +0000</pubDate>
		<guid isPermaLink="false">#comment-42882</guid>
		<description>We have a similiar situation on Win 2003 Term Svr. 

Here are some of the things I've found:

Just tried to run an Ad-Aware remover - and now i can log off within seconds rather than minutes. Didn't think that this was a problem - looking at the problem in the wrong way.....


Article ID : 828326 
Last Review : November 3, 2004 
Revision : 1.0 

SYMPTOMS

It may take 30 to 60 seconds to log off from a Terminal Services session. This length of time is longer than expected.

CAUSE

This problem may occur after you install Microsoft Windows 2000 Service Pack 4 or Windows Server 2003, and if your Remote Desktop Protocol (RDP) Client has two or more redirected printers through the client.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. 



Terminal Server hangs with Novell Client 4.83 SP2
Document ID:    CTX103265
Created:            Feb 9, 2004
Updated:           Mar 2, 2004

Products:          Citrix MetaFrame XP 1.0 for Microsoft Windows 2000, Citrix MetaFrame XP 1.0 for Microsoft Windows 2003

Symptoms

A Metaframe XP server with the Novell 4.83 Service Pack 2 client may experience a fatal system error after an amount of time.

The problem occurs only after the machine has been running for a day or more.

Cause

This is a problem with the Novell client.

Resolution

Novell fixed the issue in client 4.9 Service Pack 1. See TID10086900 for further information.

I am still searching for answers to this.</description>
		<content:encoded><![CDATA[<p>We have a similiar situation on Win 2003 Term Svr. </p>
<p>Here are some of the things I&#8217;ve found:</p>
<p>Just tried to run an Ad-Aware remover - and now i can log off within seconds rather than minutes. Didn&#8217;t think that this was a problem - looking at the problem in the wrong way&#8230;..</p>
<p>Article ID : 828326<br />
Last Review : November 3, 2004<br />
Revision : 1.0 </p>
<p>SYMPTOMS</p>
<p>It may take 30 to 60 seconds to log off from a Terminal Services session. This length of time is longer than expected.</p>
<p>CAUSE</p>
<p>This problem may occur after you install Microsoft Windows 2000 Service Pack 4 or Windows Server 2003, and if your Remote Desktop Protocol (RDP) Client has two or more redirected printers through the client.</p>
<p>To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. </p>
<p>Terminal Server hangs with Novell Client 4.83 SP2<br />
Document ID:    CTX103265<br />
Created:            Feb 9, 2004<br />
Updated:           Mar 2, 2004</p>
<p>Products:          Citrix MetaFrame XP 1.0 for Microsoft Windows 2000, Citrix MetaFrame XP 1.0 for Microsoft Windows 2003</p>
<p>Symptoms</p>
<p>A Metaframe XP server with the Novell 4.83 Service Pack 2 client may experience a fatal system error after an amount of time.</p>
<p>The problem occurs only after the machine has been running for a day or more.</p>
<p>Cause</p>
<p>This is a problem with the Novell client.</p>
<p>Resolution</p>
<p>Novell fixed the issue in client 4.9 Service Pack 1. See TID10086900 for further information.</p>
<p>I am still searching for answers to this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->