Re: Intermittent terminal service session connectivity problem?!

From: dude (dude_at_aol.com)
Date: 08/03/04 

Date: Tue, 3 Aug 2004 15:27:20 -0500

Only happens on this specific machine! There are numerous other machines in
that same office joined into their own wacko domain and still able to logon
with no problems. There are no trusts between the two domains, and there
needn't be one. Users are using terminal services /RDP client software to
login remotely via terminal services sessions. My understanding is that as
long as the machine acquires a license, and user has a domain account where
that terminal server sits, then they can login and get on with no issues. I
seriously am ready to blow away that user's laptop.

We already did:
- deleted MSLicensing reg key on client machine, reboot, try to login.. same
thing
- applied SP4 on the Win2k install on his laptop
- tried the newest version of RDP client
- reset his domain password
- checked terminal services property under his domain user name
- checked that he has terminal services permission to logon
- checked keyboard caps lock status
- checked if he is typing in wrong password -> definitely NOT!

access magically goes through after a few trys every morning.

>
> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote in message
> news:Xns9534A6237232Averanoesthemutforsse@207.46.248.16...
> > Have you checked the keyboard?
> > Most common cause for intermittent login faulures, when you are
> > convinced that the user types it in correctly.
> >
> > --
> > Vera Noest
> > MCSE,CCEA, Microsoft MVP - Terminal Server
> > http://hem.fyristorg.com/vera/IT
> > *----------- Please reply in newsgroup -------------*
> >
> > "dude" <dude@aol.com> wrote in
> > news:u#UsmG$cEHA.3728@TK2MSFTNGP09.phx.gbl:
> >
> > > Ok, the exact message is:
> > >
> > > The system could not log you on. Make sure your User name and
> > > domain are correct, then type your password again. Letters in
> > > passwords must be typed using the correct case. Make sure that
> > > Caps Lock is not accidentally on.
> > >
> > > The strange thing is, he types in the correct username and
> > > password everytime. This happens only at first few attempts, it
> > > then goes through after a few trys. On that terminal server's
> > > security log. I receive Event 529 and failure reason is
> > > "Unknown user name or bad password." I've already tried
> > > deleting the license on the user's local machine.. same thing
> > > still happens. User's laptop has Win2k SP4 on it. I found MS
> > > article, Q290706, however he doesn't have automatic logon with
> > > long password. So I'm sort of at loss right now
> > >
> > > help please!
> > > thanks
> > >

Relevant Pages

  • Re: Cant log on locally to remote computer after remote desktops
    ... The problem we have is that we do not want to enable Terminal Services logon ... REMOTE LOGIN, and she gets the "Your logon privilege has been disabled" ...
    (microsoft.public.windowsxp.work_remotely)
  • Cant log on locally to XP after RDP session
    ... The problem we have is that we do not want to enable Terminal Services logon ... REMOTE LOGIN, and she gets the "Your logon privilege has been disabled" ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Cant log on locally to remote computer after remote desktops acce
    ... log off and then she tries to logon locally JUST AS SHE WAS PRIOR TO MY ... REMOTE LOGIN, and she gets the "Your logon privilege has been disabled" ... On the Terminal Services Profile tab, ...
    (microsoft.public.windowsxp.work_remotely)
  • Logon Delay problem
    ... My machine is now running Win2K SP4 and is a client ... weird problem when trying to logon to the system. ... when the user tried to press Alt-Ctrl-Enter again to login ...
    (microsoft.public.win2000.new_user)
  • How to retrieve the client address of the terminal services session?
    ... the terminal services session using the VBScript? ... like to write a login script for the users who login to a Windows ... purpose on using the Windows Terminal services and it will also log ... down the client address. ...
    (microsoft.public.scripting.wsh)