Re: Windows XP



What Vera said, pkus if you have multiple users, you'll have to configure
seperate ports for those users in the registry, all the users cannot use
port 3389 unless they plan to use the same computer one person at a time.

those other users will have to connect ip:port in the remote desktop program


"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns9703E96395189veranoesthemutforsse@xxxxxxxxxxxxxxxx
> Yes and no :-)
> Technically, you will be using the terminal services technique,
> which is built in to XP Pro, but it's not called Terminal Services,
> it's called Remote Desktop.
> The main difference with a full-scale Terminal Server is that
> Remote Desktop gives you only one single connection to each
> workstation, but as long as every user is connecting to his or her
> own workstation, that should be just fine with you.
>
> On your XP, open Control Panel - System - properties - Remote -
> Remote Desktop, and Add the user to the allowed remote Desktop
> users Group.
>
> If you have a firewall (which I assume you have), you have to open
> port 3389.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?TkMgQmVhY2ggQnVt?=
> <NCBeachBum@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 03 nov 2005 in
> microsoft.public.windows.terminal_services:
>
> > We need to setup home access for our Accounting Department
> > Comptroller. Our preference is to use Terminal Services since
> > it's free; however, they would be connecting into their
> > workstation PC running Windows XP Pro.
> >
> > Is it possible for Terminal Services to run on a Windows XP Pro
> > workstation?
> > If so, how do you set it up?
> >
> > Thanks!


.



Relevant Pages

  • Re: Terminal Services temporary client liense
    ... I have already explained why a new workstation will not give you ... uninstall Terminal Services, since you only want Remote Desktop ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.win2000.termserv.clients)
  • RE: Windows Server 2003 Service Pack2
    ... attack on the server. ... (for a long time I couldn't run remote desktop between our sites, ... stopped and started the rdp connection in terminal services configuration. ... to check port 3189. ...
    (microsoft.public.windows.server.general)
  • Re: remote desktop
    ... Have you checked the remote desktop properties of your server to sure the Remote desktop is allow and is allowed for you? ... network to the sbs 2003 machine or any workstation on the domain. ... i opend up the router to allow all traffic to port 3389 and pointed it ...
    (microsoft.public.windows.server.sbs)
  • Remote desktop on domain: The local policy of this system does not permit you to logon interactively
    ... Added the users I want remote desktop for to the Remote Users ... Set Allow log on locally and Allow log on through Terminal Services ... I can't add domain accounts to the remote ... desktop users group on the workstation, so I don't know what I'm ...
    (microsoft.public.windowsxp.work_remotely)
  • RE: Remote Desktop used to work but now no longer
    ... Have you tried applying Windows Server 2003 SP1? ... If terminal services isn't working, can you telnet to port 3389 on the ... > We have several machines behind a single firewall using remote desktop. ...
    (microsoft.public.windows.terminal_services)