RE: Remote Web Workplace
- From: v-shshao@xxxxxxxxxxxxxxxxxxxx ("Shawn Shao [MSFT]")
- Date: Tue, 18 Dec 2007 08:59:21 GMT
Hi Edward,
Thank you for posting there.
From your post, I understand that after terminating two RWW connections,new remote connection cannot be established normally through RWW.
Before we go any further, I would like to confirm if you are trying to
remote to the SBS server.
As you may know, Small Business Server 2003 does not include Terminal
Server. However, you can remotely administer computers using Remote Desktop
for Administration (in Windows 2000 Server, this was called Terminal
Services in Remote Administration mode), which allows you to connect to the
console or to create up to two new sessions from another computer. Thus, it
is an expected behavior if you try to create the third connection to SBS
server.
Moreover, when you close the remote desktop window, the session is not
terminated. Rather, it is held in memory so that the client can reconnect
and re-establish the session. So, in your case, the two sessions still work
and you are able to reconnect via Remote Desktop.
To close the disconnected sessions completely, we can perform the following
steps from the SBS Server
=========
1. Click Start and then Run.
2. Type in tsadmin and press Enter. Terminal Services Manager opens.
3. Switch to the Sessions tab. Right click the Disconnected connection and
then choose Reset. Click OK.
Regarding this issue, I also would like to share the following information
with you:
When you "log off" from the remote desktop, the session ends. To perform a
log off, you can enter Ctrl+Alt+End. After that you can use another User
account log on who won't be encounter the Warning.
Here is some information of Timeout Settings for Terminal Session:
Timeout Settings (Run tscc.msc to open Terminal Services Configuration,
click Connections, in the right panel, double click RDP-Tcp and then choose
Sessions tab to configure)
==========
Here you can choose how long a connection should be maintained, how long a
disconnected session should be maintained in memory, and how long a session
should be allowed to be idle before disconnecting it.
The Connection Timeout determines how long the client can stay connected,
regardless of whether the session is idle or not.
The Disconnected Session Timeout determines how long a disconnected session
should be held in memory. If a client disconnects (rather than logging
off), the session is not terminated. Rather, it is held in memory so that
the client can reconnect and re-establish the session. Applications that
were running previously should still be available.
The Idle Session Timeout determines how long a session with no activity
should remain connected. Note that turning on the Menu Bar clock will
generate enough continuous traffic to keep a session from being idle.
If you uncheck No Timeout, the default for Connection is 120 minutes, for
Disconnection is 10 minutes, and for Idle is 30 minutes.
Setting these values here affects every Client that uses this connection.
If you want to modify the values for a specific user, you can do so in User
Manager. However, keep in mind that Connection Configuration values
override values in User Manager. If you need both advanced options set in
Connection Configuration AND separate options set for individual users in
User Manager, you will need to add multiple network adapters to your
Terminal Server and define a different connection for each adapter.
For more information, please refer:
186566 Connection Configuration in Terminal Server
http://support.microsoft.com/?id=186566
Hope this addresses your concern, please feel free to let me know if you
have anything unclear.
Best regards,
Shawn Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
from the web interface: Partner Feedback
from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
.
- References:
- Remote Web Workplace
- From: Edward
- Remote Web Workplace
- Prev by Date: Re: RDP into Small Business Server 2003
- Next by Date: Re: Exchange user mailbox for "smtp"
- Previous by thread: Remote Web Workplace
- Next by thread: RE: Remote Web Workplace
- Index(es):
Relevant Pages
|
Loading
