Black Screen after TSADMIN remote session with client.

[Guest ChrisRob]

*Server is 2003 Enterprise - client is on xp pro*

 

First of all i posted this a while back, and must have forgot about it.

Sorry Munindra for not getting back to you.

 

Basically what happens, is i'll log into a session to help the user. When

i'm done I'll ctrl+* to get out, and there screen will go black/blank. If

they hit the X to disconnect they get the same screen when they log back in

(unless the session times out first). It's not just when i remote their

sessions it also happens when Senior PMs help their junior PMs. It doesn't

happen all the time either. One user i'm working with says it happens 75% of

the time. Thanks for any help anyone can offer up.

 

The steps

1. I RDP into the terminal server

2. I start TSADMIN

3. I right click their session and choose remote control

4. We work/train for a little while

5. I ctrl+* to exit the remote control session.

6. User contacts me letting me know her terminal server session has gone

black.

7. I log the person off through tsadmin so they can log back in.

 

Thanks again, for anyone's help.

[Guest Vera Noest [MVP]]

Re: Black Screen after TSADMIN remote session with client.

 

I can't say that I can explain what happens, but I'm thinking that

the default screen saver on the TS is just a black screen, with a

default idle time of 10 minutes. Can you check to see if this only

happens when you are remote controlling the user session for 10

minutes or more?

 

Another thing that you might want to rule out is some sort of

corruption in the bitmap caching. Could you ask some users to turn

of bitmap caching in their rdp client and see if that makes a

difference?

 

A third cause for a black screen on a TS could be a problem with

the MTU size of the connection. Check these 2 Q&A's:

 

Q. Sometimes when I connect to my terminal server, I see a black

screen. Why does this occur?

 

Q. How can I test for 'black hole' dropouts in my network?

 

in the TS FAQ at

http://technet.microsoft.com/en-us/ts/cc671614.aspx

_________________________________________________________

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?Q2hyaXNSb2I=?= <ChrisRob@discussions.microsoft.com>

wrote on 18 jul 2008 in

microsoft.public.windows.terminal_services:

> *Server is 2003 Enterprise - client is on xp pro*

>

> First of all i posted this a while back, and must have forgot

> about it. Sorry Munindra for not getting back to you.

>

> Basically what happens, is i'll log into a session to help the

> user. When i'm done I'll ctrl+* to get out, and there screen

> will go black/blank. If they hit the X to disconnect they get

> the same screen when they log back in (unless the session times

> out first). It's not just when i remote their sessions it also

> happens when Senior PMs help their junior PMs. It doesn't happen

> all the time either. One user i'm working with says it happens

> 75% of the time. Thanks for any help anyone can offer up.

>

> The steps

> 1. I RDP into the terminal server

> 2. I start TSADMIN

> 3. I right click their session and choose remote control

> 4. We work/train for a little while

> 5. I ctrl+* to exit the remote control session.

> 6. User contacts me letting me know her terminal server session

> has gone black.

> 7. I log the person off through tsadmin so they can log back in.

>

> Thanks again, for anyone's help.

[Guest ChrisRob]

Re: Black Screen after TSADMIN remote session with client.

 

Thanks Vera, I'll see what I come up with and let you know how it goes.

 

"Vera Noest [MVP]" wrote:

> I can't say that I can explain what happens, but I'm thinking that

> the default screen saver on the TS is just a black screen, with a

> default idle time of 10 minutes. Can you check to see if this only

> happens when you are remote controlling the user session for 10

> minutes or more?

>

> Another thing that you might want to rule out is some sort of

> corruption in the bitmap caching. Could you ask some users to turn

> of bitmap caching in their rdp client and see if that makes a

> difference?

>

> A third cause for a black screen on a TS could be a problem with

> the MTU size of the connection. Check these 2 Q&A's:

>

> Q. Sometimes when I connect to my terminal server, I see a black

> screen. Why does this occur?

>

> Q. How can I test for 'black hole' dropouts in my network?

>

> in the TS FAQ at

> http://technet.microsoft.com/en-us/ts/cc671614.aspx

> _________________________________________________________

> 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?Q2hyaXNSb2I=?= <ChrisRob@discussions.microsoft.com>

> wrote on 18 jul 2008 in

> microsoft.public.windows.terminal_services:

>

> > *Server is 2003 Enterprise - client is on xp pro*

> >

> > First of all i posted this a while back, and must have forgot

> > about it. Sorry Munindra for not getting back to you.

> >

> > Basically what happens, is i'll log into a session to help the

> > user. When i'm done I'll ctrl+* to get out, and there screen

> > will go black/blank. If they hit the X to disconnect they get

> > the same screen when they log back in (unless the session times

> > out first). It's not just when i remote their sessions it also

> > happens when Senior PMs help their junior PMs. It doesn't happen

> > all the time either. One user i'm working with says it happens

> > 75% of the time. Thanks for any help anyone can offer up.

> >

> > The steps

> > 1. I RDP into the terminal server

> > 2. I start TSADMIN

> > 3. I right click their session and choose remote control

> > 4. We work/train for a little while

> > 5. I ctrl+* to exit the remote control session.

> > 6. User contacts me letting me know her terminal server session

> > has gone black.

> > 7. I log the person off through tsadmin so they can log back in.

> >

> > Thanks again, for anyone's help.

>