Re: Terminal Services Remote Desktop Login Problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



The server is running Windows 2000 with SP4. No the users are not on
the same LAN, they are all across the country connecting over the
internet. Thanks!



Vera Noest [MVP] wrote:
> Can you please include the previous contect of the thread in your
> reply? Makes it a lot easier to know what the problem was.
>
> Then it probably is a network problem.
> Are these users on the same LAN as the server?
> Which OS and SP are you running on the server?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> ybondsmile@xxxxxxxxx wrote on 05 aug 2005 in
> microsoft.public.windows.terminal_services:
>
> > The error message is:
> > Remote Desktop Disconnected
> > The connection to the remote computer was broken. This may have
> > been caused by a network error. Please try connecting to the
> > remote computer again. OK Help
> > There is nothing in the EventLog.
> > Thank you for your response!

Some of my terminal services users must log into Remote Desktop several

times before successfully connecting. Any ideas why this would be?
Thank you very much for any help!


Reply

2. Vera Noest [MVP] Aug 4, 4:05 pm show options

Newsgroups: microsoft.public.windows.terminal_services
From: "Vera Noest [MVP]" <vera.no...@xxxxxxxxxxxxxxxxxxxxxxxxx> - Find
messages by this author
Date: Thu, 04 Aug 2005 14:05:46 -0700
Local: Thurs, Aug 4 2005 4:05 pm
Subject: Re: Terminal Services Remote Desktop Login Problem
Reply | Reply to Author | Forward | Print | Individual Message | Show
original | Report Abuse

Do they get any error message when they are unable to connect?
Anything in the EventLog on the server?


______________________________­___________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___


ybondsm...@xxxxxxxxx wrote on 04 aug 2005 in
microsoft.public.windows.termi­nal_services:



- Hide quoted text -
- Show quoted text -

> Some of my terminal services users must log into Remote Desktop
> several times before successfully connecting. Any ideas why
> this would be? Thank you very much for any help!


Reply

.



Relevant Pages

  • Re: Users Cant Log Into Local Machine That Is Attached To A Domai
    ... Are you trying to access to a T.S server? ... Are you trying to access via RDC (Remote desktop connection) to a Windows ... Terminal Services Client Error Message: You Do Not Have Access to Logon to ... You do not have access to logon to the Session. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Time zone redirection
    ... Administration and full-blown Terminal Services. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... client connections:-O. ... Well - obviously that does not work in Remote Desktop Admin mode ...
    (microsoft.public.windows.terminal_services)
  • Re: terminal services and 70-290
    ... Wish they would just call it remote desktop protocol and keep it uniform. ... do have a little server set up on virtual pc and installed the remote admin ... Terminal Services uses the RDP for communicating ... Configure a server to enable Remote Desktop For Administration ...
    (microsoft.public.cert.exam.mcse)
  • Re: Does Terminal Server Licensing turn off Remote Desktop for Adm
    ... Why would you keep Terminal Server Licensing Service, ... There is no need whatsoever for TS Licensing in this situation. ... Remote Desktop for Administration does *not* need any TS CALs, ... a license after I have installed Terminal Services?" ...
    (microsoft.public.win2000.termserv.apps)
  • no remote desktop for admin
    ... I can log on to the console as administrator as shown in the above output. ... Using mstsc.exe from a command prompt on the server gives me the same result ... You should also set the Terminal Services service is to start ... and I made sure that remote desktop is checked in the remote ...
    (microsoft.public.windows.terminal_services)