RE: Terminal Services



Hi SKC,

Thanks for your posting here.

For your description, I understand that you can not connect to client
computers using terminal services. If I am off base, please don't hesitate
to let me know.

Only if Remote Desktop Connection or Terminal Services client installed on
the client computer you can remotely connect to them. Windows 2000
professional edition doesn't provide remote desktop connection so you can
not connect to them. Windows XP only support one remote desktop connection
session.

Please follow my suggestion to troubleshooting the issue on client
computers running Windows XP Professional:

Suggestion 1:
=================
Cause: The client computer running Windows XP Professional is not
configured to allow Terminal Services connections.

Solution: Configure the client computer running Windows XP Professional to
use Remote Desktop.

To configure the client computer running Windows XP Professional to use
Remote Desktop
*Note: To complete this procedure, you must be logged on as a member of the
Domain Admins security group.

1. On the client computer, click Start, click Control Panel, and then click
System.
2. On the Remote tab, select the Allow users to connect remotely to this
computer check box.

Suggestion 2:
=================
Cause: This problem can occur if the user account does not have permissions
to log on by using Remote Desktop. Please ensure you have permissions to
log on by using Remote Desktop

Solution: Assign the user permissions to use Remote Desktop.

To assign user permissions to use Remote Desktop, Please refer to following
steps:
*Note: To complete this procedure, you must be logged on as a member of the
Domain Admins security group.

1. On a computer running Windows Small Business Server 2003, click Start,
and then click Server Management.
2. In the console tree, click Users.
3. In the details pane, right-click the user account that requires
permissions to log on to Terminal Services, and then click Change User
Properties.
4. On the User Properties page, click the Terminal Services Profile tab.
4. Check the Allow to log on to Terminal Server check box.

Suggestion 3:
=================
Cause: The client computer running Windows XP Professional is not
configured to allow the user to access it remotely.

Solution: Allow a user to connect remotely to the client computer by using
Remote Desktop.

To allow user to connect remotely to the client computer by using Remote
Desktop
*Note: To complete this procedure, you must be logged on as a member of the
Domain Admins security group.

1. On the client computer, click Start, point to Settings, click Control
Panel, and then click System.
2. On the Remote tab, under Remote Desktop, click Select Remote Users.
3. In the Remote Desktop Users dialog box, click Add.
4. In the Select Users dialog box, click Locations to specify the search
location.
5. To specify the types of objects that you want to search for, click
Object Types.
6. In Enter the object names to select, type the names of the objects that
you want to search for.
7. Click Check Names.
8. When the name is located, click OK. The name appears in the list of
users in the Remote Desktop Users dialog box.

More info:
Remote Administration using Terminal Services
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Serve
rHelp/45cb64f3-c4ad-4b16-bb8f-e518e27fe6e9.mspx

If the issue persists, please give me the screenshot of the error message
and related event error log to further analyze.

Hope this helps. I am currently standing by for you about the test result.
I am always happy to be of further assistance.

Have a nice day!

Best Regards,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: Terminal Services
>thread-index: AcWXWtYrnzmJjNipSRmYbRaruZ540Q==
>X-WBNR-Posting-Host: 83.104.194.213
>From: =?Utf-8?B?U2tj?= <Skc@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: Terminal Services
>Date: Tue, 2 Aug 2005 05:08:04 -0700
>Lines: 16
>Message-ID: <BA6D42AF-5AB9-4116-BDD8-58E9D161A225@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:140721
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>We are running SBS2003 Premier. We have around 60 clients, 50 WinXP Pro
and
>10 Win2K Pro.
>
>When I open Manager on the SBS, Client Computers, and right-click a client
>and select Connect using Terminal Services (this is to a Win2K machine), I
>get:
>
>Remote Desktop Disconnected.
>The client could not connect to the remote computer...
>
>How do I get a connection to all clients? I tried a WinXP Pro client and
>get the same message.
>
>Please help!
>
>skc
>

.



Relevant Pages

  • RE: sbs 2008 remote computer connection problem
    ... it much seems that the terminal services client ... all ActiveX controls are disabled after you install Windows XP Service Pack ... Please understand that in the SBS 2008 environment, the RWW remote desktop ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Services Advanced Client
    ... Microsoft MVP - Terminal Server ... >> So I'm hoping Terminal Services is a solution to this problem. ... the rdp connection from the client to the Terminal ... > Here is a link to information about the Remote Desktop Web Connection ...
    (microsoft.public.windows.terminal_services)
  • RE: RWW Issue
    ... client via RWW or RDP. ... Use the following steps to start Remote Desktop service on this client: ... | DNS server failed the update request. ...
    (microsoft.public.windows.server.sbs)
  • Beginners questions: TS between offices
    ... The closest I've come to installing or using terminal services is to use ... Remote Desktop on XP Pro, Now I have a client who wants to use a specific ... I'd be really grateful for some advice on this! ...
    (microsoft.public.windows.terminal_services)
  • Re: Remote Desktop Issue
    ... target I get the error message, that the client cannot connect to the remote ... It seems that the Remote Desktop on the target isn't enabled. ... Terminal Server Client ... Terminal Services Client ActiveX Core ...
    (microsoft.public.windowsxp.embedded)