User logs off strait after logging on

[HellslayeR]

Hello.

I'm having a problem with Windows 2008 TS and Thin Clients.

When my thin clients are using rdp to connect to the 2008 TS it works ace
and I get the screen where you are asked for username/password.

Right after I've typed that in and hit enter the user will log off.
I then have to repeate the prosess 2-3 times and then suddenly it logs on to
the TS just fine.

I can also be "lucky" and it will log on the TS on the first attempt.
I have 3 Windows 2008 TS and they all behave like this.

EventID only logs that there has been a log on and a log off from my test
user, it says nothing about failed attempts.

Does anyone have a idea? Will provide more information if needed.

 

[Vera Noest [MVP]]

Re: User logs off strait after logging on

Mmm, I believe that this can happen when users don't have
sufficients rights on the root of the C: drive.

Immediate logoffs used to be a known problem on Windows 2003 and
some Nvidia display drivers on the server. Maybe that old NVidia
problem has resurrected on 2008? What driver are you using?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?SGVsbHNsYXllUg==?=
<HellslayeR@discussions.microsoft.com> wrote on 11 aug 2008:

> Hello.
>
> I'm having a problem with Windows 2008 TS and Thin Clients.
>
> When my thin clients are using rdp to connect to the 2008 TS it
> works ace and I get the screen where you are asked for
> username/password.
>
> Right after I've typed that in and hit enter the user will log
> off. I then have to repeate the prosess 2-3 times and then
> suddenly it logs on to the TS just fine.
>
> I can also be "lucky" and it will log on the TS on the first
> attempt. I have 3 Windows 2008 TS and they all behave like this.
>
> EventID only logs that there has been a log on and a log off
> from my test user, it says nothing about failed attempts.
>
> Does anyone have a idea? Will provide more information if
> needed.

 

[HellslayeR]

Re: User logs off strait after logging on

Well these are blade servers of the type ProLiant BL460c G1 so they are using
a standard vga driver from microsoft at the moment.

The times I do manage to log on I can create/save documents etc so the user
have some rights and I cant see that they should need more rights to the c:
drive on the TS (Asuming thats the drive you are thinking of? )

"Vera Noest [MVP]" wrote:

> Mmm, I believe that this can happen when users don't have
> sufficients rights on the root of the C: drive.
>
> Immediate logoffs used to be a known problem on Windows 2003 and
> some Nvidia display drivers on the server. Maybe that old NVidia
> problem has resurrected on 2008? What driver are you using?
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*

 

[Vera Noest [MVP]]

Re: User logs off strait after logging on

Mm, yes, forget that permission idea, that would give the same
problem consistently, not only sometimes.
To be honest, I've no real idea, but it might have something to do
with the ability to load your profile. Are you using roaming or
local profiles?

I'd enable verbose userenv logging and see if that gives some more
information.

221833 - How to enable user environment debug logging in retail
builds of Windows
http://support.microsoft.com/?kbid=221833

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?SGVsbHNsYXllUg==?=
<HellslayeR@discussions.microsoft.com> wrote on 11 aug 2008:

> Well these are blade servers of the type ProLiant BL460c G1 so
> they are using a standard vga driver from microsoft at the
> moment.
>
> The times I do manage to log on I can create/save documents etc
> so the user have some rights and I cant see that they should
> need more rights to the c: drive on the TS (Asuming thats the
> drive you are thinking of? )
>
> "Vera Noest [MVP]" wrote:
>
>> Mmm, I believe that this can happen when users don't have
>> sufficients rights on the root of the C: drive.
>>
>> Immediate logoffs used to be a known problem on Windows 2003
>> and some Nvidia display drivers on the server. Maybe that old
>> NVidia problem has resurrected on 2008? What driver are you
>> using?

 

[HellslayeR]

Re: User logs off strait after logging on

We're using roaming profiles.

I followed your steps but sadly the log dosent record anything when the
logon fails.. I can see the log filling up with tonns of data when I do a
sucsessfull logon, but when it fails the log remain empety sadly.

I've started again today and discovred how strange my servers are behaving:

As said I have 3 terminal servers.. All set up the exact same way.
Today I've logged on server 1 with two different users.. Test user 1 and
test user 2.. It worked like a charm logging them both on to server 1.

So I switch to server 2 and tries to log them both on there.. Failed on both
test users.. I can see the "Welcome" text for around 1 second before my thin
clients stops and shuts down.

I jump back to server 1 again.. Works like a charm.

So I try server 2 again and this time test user 1 logs on like a charm, but
test user 2 fails at the welcoming screen again.

Test user 1 created a lot of data in the logfile.. Would that be of any
interest?

"Vera Noest [MVP]" wrote:

> Mm, yes, forget that permission idea, that would give the same
> problem consistently, not only sometimes.
> To be honest, I've no real idea, but it might have something to do
> with the ability to load your profile. Are you using roaming or
> local profiles?
>
> I'd enable verbose userenv logging and see if that gives some more
> information.
>
> 221833 - How to enable user environment debug logging in retail
> builds of Windows
> http://support.microsoft.com/?kbid=221833
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?SGVsbHNsYXllUg==?=
> <HellslayeR@discussions.microsoft.com> wrote on 11 aug 2008:
>
> > Well these are blade servers of the type ProLiant BL460c G1 so
> > they are using a standard vga driver from microsoft at the
> > moment.
> >
> > The times I do manage to log on I can create/save documents etc
> > so the user have some rights and I cant see that they should
> > need more rights to the c: drive on the TS (Asuming thats the
> > drive you are thinking of? )
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Mmm, I believe that this can happen when users don't have
> >> sufficients rights on the root of the C: drive.
> >>
> >> Immediate logoffs used to be a known problem on Windows 2003
> >> and some Nvidia display drivers on the server. Maybe that old
> >> NVidia problem has resurrected on 2008? What driver are you
> >> using?
>

 

[Vera Noest [MVP]]

Re: User logs off strait after logging on

The profiles are 2008-specific, right? You're not logging on to
both 2003 and 2008 Terminal Servers with the same profile?

I think that I would call Microsoft Support.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?SGVsbHNsYXllUg==?=
<HellslayeR@discussions.microsoft.com> wrote on 12 aug 2008:

> We're using roaming profiles.
>
> I followed your steps but sadly the log dosent record anything
> when the logon fails.. I can see the log filling up with tonns
> of data when I do a sucsessfull logon, but when it fails the log
> remain empety sadly.
>
> I've started again today and discovred how strange my servers
> are behaving:
>
> As said I have 3 terminal servers.. All set up the exact same
> way. Today I've logged on server 1 with two different users..
> Test user 1 and test user 2.. It worked like a charm logging
> them both on to server 1.
>
> So I switch to server 2 and tries to log them both on there..
> Failed on both test users.. I can see the "Welcome" text for
> around 1 second before my thin clients stops and shuts down.
>
> I jump back to server 1 again.. Works like a charm.
>
> So I try server 2 again and this time test user 1 logs on like a
> charm, but test user 2 fails at the welcoming screen again.
>
> Test user 1 created a lot of data in the logfile.. Would that be
> of any interest?
>
> "Vera Noest [MVP]" wrote:
>
>> Mm, yes, forget that permission idea, that would give the same
>> problem consistently, not only sometimes.
>> To be honest, I've no real idea, but it might have something to
>> do with the ability to load your profile. Are you using roaming
>> or local profiles?
>>
>> I'd enable verbose userenv logging and see if that gives some
>> more information.
>>
>> 221833 - How to enable user environment debug logging in retail
>> builds of Windows
>> http://support.microsoft.com/?kbid=221833
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?SGVsbHNsYXllUg==?=
>> <HellslayeR@discussions.microsoft.com> wrote on 11 aug 2008:
>>
>> > Well these are blade servers of the type ProLiant BL460c G1
>> > so they are using a standard vga driver from microsoft at the
>> > moment.
>> >
>> > The times I do manage to log on I can create/save documents
>> > etc so the user have some rights and I cant see that they
>> > should need more rights to the c: drive on the TS (Asuming
>> > thats the drive you are thinking of? )
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> Mmm, I believe that this can happen when users don't have
>> >> sufficients rights on the root of the C: drive.
>> >>
>> >> Immediate logoffs used to be a known problem on Windows 2003
>> >> and some Nvidia display drivers on the server. Maybe that
>> >> old NVidia problem has resurrected on 2008? What driver are
>> >> you using?

 

[HellslayeR]

Re: User logs off strait after logging on

The DC is a 2003, but the terminal servers are all 2008 indeed.

I seem to have located the source of the problem altho I dont know why it
causes it.

I decided to go back to square 1 and start over to see when the problem came.
So I removed NLB and TS Session Broker, and changed it so that I would log
into one server at a time.

Now I have allready tried logging in to one server at the time but not
without uninstalling NLB and session broker.

So I did and then tried to log on twice with two different users on each
TS.. Sucsess.. Not a single failed login.

I implemented TS Session Broker again on all the servers since it's required
for NLB and just like that I have problems logging in again.

So it would seem TS Session Broker is the problem here. I will have to start
looking for other load balancing solutions now then.

"Vera Noest [MVP]" wrote:

> The profiles are 2008-specific, right? You're not logging on to
> both 2003 and 2008 Terminal Servers with the same profile?
>
> I think that I would call Microsoft Support.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*

 

[Vera Noest [MVP]]

Re: User logs off strait after logging on

OK, that's a huge step forward!
I wouldn't immediately give up on Session Broker, this must be
solvable. There are lots of people out there using it without this
problem.

Let me get one thing clear: you are trying to connect to the farm
each time, right? And you would expect to either start a new
session (if you have no existing session as that user), or you
expect to be connected to your existing session.

Have you configured all terminal servers in the farm to restrict
each user to a single session?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?SGVsbHNsYXllUg==?=
<HellslayeR@discussions.microsoft.com> wrote on 12 aug 2008:

> The DC is a 2003, but the terminal servers are all 2008 indeed.
>
> I seem to have located the source of the problem altho I dont
> know why it causes it.
>
> I decided to go back to square 1 and start over to see when the
> problem came. So I removed NLB and TS Session Broker, and
> changed it so that I would log into one server at a time.
>
> Now I have allready tried logging in to one server at the time
> but not without uninstalling NLB and session broker.
>
> So I did and then tried to log on twice with two different users
> on each TS.. Sucsess.. Not a single failed login.
>
> I implemented TS Session Broker again on all the servers since
> it's required for NLB and just like that I have problems logging
> in again.
>
> So it would seem TS Session Broker is the problem here. I will
> have to start looking for other load balancing solutions now
> then.
>
> "Vera Noest [MVP]" wrote:
>
>> The profiles are 2008-specific, right? You're not logging on to
>> both 2003 and 2008 Terminal Servers with the same profile?
>>
>> I think that I would call Microsoft Support.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*

 

[Jeff Pitsch]

Re: User logs off strait after logging on


This problem almost sounds like the 2nd server's remote desktop user group
isn't populated correctly.
--
Jeff Pitsch
Microsoft MVP - Terminal Services

"Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote in message
news:Xns9AF886480672Cveranoesthemutforsse@207.46.248.16...
> OK, that's a huge step forward!
> I wouldn't immediately give up on Session Broker, this must be
> solvable. There are lots of people out there using it without this
> problem.
>
> Let me get one thing clear: you are trying to connect to the farm
> each time, right? And you would expect to either start a new
> session (if you have no existing session as that user), or you
> expect to be connected to your existing session.
>
> Have you configured all terminal servers in the farm to restrict
> each user to a single session?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?SGVsbHNsYXllUg==?=
> <HellslayeR@discussions.microsoft.com> wrote on 12 aug 2008:
>
>> The DC is a 2003, but the terminal servers are all 2008 indeed.
>>
>> I seem to have located the source of the problem altho I dont
>> know why it causes it.
>>
>> I decided to go back to square 1 and start over to see when the
>> problem came. So I removed NLB and TS Session Broker, and
>> changed it so that I would log into one server at a time.
>>
>> Now I have allready tried logging in to one server at the time
>> but not without uninstalling NLB and session broker.
>>
>> So I did and then tried to log on twice with two different users
>> on each TS.. Sucsess.. Not a single failed login.
>>
>> I implemented TS Session Broker again on all the servers since
>> it's required for NLB and just like that I have problems logging
>> in again.
>>
>> So it would seem TS Session Broker is the problem here. I will
>> have to start looking for other load balancing solutions now
>> then.
>>
>> "Vera Noest [MVP]" wrote:
>>
>>> The profiles are 2008-specific, right? You're not logging on to
>>> both 2003 and 2008 Terminal Servers with the same profile?
>>>
>>> I think that I would call Microsoft Support.
>>> _________________________________________________________
>>> Vera Noest
>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>> TS troubleshooting: http://ts.veranoest.net
>>> *----------- Please reply in newsgroup -------------*