From: Absoffthewake on


"Gijs" wrote:

> Dear Vera,
>
> We're facing exactly the same problem but the solution mentioned above
> doens't work for us. We are using passthrough authentication on our VPN
> solution and if we use the settings above users have to enter their username
> and password twice.
>
> Is there any other way to solve this?
>
> Kinda regards,
> Gijs.
>
> "Vera Noest [MVP]" wrote:
>
> > Great! I'm glad that the problem is solved, and thanks for the
> > feedback!
> > _________________________________________________________
> > 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?T0M=?= <OC(a)discussions.microsoft.com> wrote on 18 jan
> > 2008 in microsoft.public.windows.terminal_services:
> >
> > > Correction! There is a checkbox saying "Always prompt for
> > > password" - it has to be checked and then the aforementioned
> > > problem is solved.
> > >
> > > I will let the users test it out for a week and see if it's OK,
> > > but I believe that was it.
> > >
> > > Great job Vera!
> > >
> > > "OC" wrote:
> > >
> > >> Thank you, Vera!
> > >>
> > >> I have entered the domain name and it now seems to default
> > >> properly to the domain, but without having the username and
> > >> password also entered it seems like I always get an error when
> > >> trying to log in. It's like the RDP client tells the server:
> > >> "use a blank username and a blank password but log in to the
> > >> DOMAIN". I can continue after I acknowledged the error, but
> > >> this won't make the users happy.
> > >>
> > >> Is there anything I can do about this?
> > >>
> > >> Thanks,
> > >> Octavian
> >
From: Absoffthewake on

I have the solution... CALL MICROSOFT AND TELL THEM TO STOP SCREWING THINGS
UP!!!

I mean, come on, why would a terminal server default to the computer name???
That is just so stupid. R2 does the same thing. Someone needs to get fired.