TS lockups

[Guest Tim Gowen]

I'm seeing a lot of lock-ups with remote users on a particular W2K3 server.

I've tried the KeepAlive registry fix, but it was already set to the

recommended setting. Power management or screen savers don't seem to be the

issue either. The screens of the remote session just go to the background

colour, with no icons. They're still shown as connected in the

Administrator, but they cannot be made to come alive.

 

 

Tim

[Guest Vera Noest [MVP]]

Re: TS lockups

 

Any errors or warning in the EventLog?

Which error message do you get when you try to establish a new

session to the server (I'am assuming that you can't start a new

session)?

Which SP is the server running?

When this happens, can you still ping the server? Connect to a

shared drive on the server?

Check if this applies:

 

883670 - FIX: The Terminal Services service stops responding in

Windows Server 2003 and you receive an "The RPC service is

unavailable" error message when you try to connect to the terminal

server by using the Remote Desktop Connection program

http://support.microsoft.com/?kbid=883670

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Tim Gowen" <tim.gowen@rafmuseum.org> wrote on 25 sep 2007 in

microsoft.public.windows.terminal_services:

> I'm seeing a lot of lock-ups with remote users on a particular

> W2K3 server. I've tried the KeepAlive registry fix, but it was

> already set to the recommended setting. Power management or

> screen savers don't seem to be the issue either. The screens of

> the remote session just go to the background colour, with no

> icons. They're still shown as connected in the Administrator,

> but they cannot be made to come alive.

>

>

> Tim

[Guest Tim Gowen]

Re: TS lockups

 

Nothing in the event logs that's out of the ordinary; some 1010 errors

MSGina about a user's home directory, but this user doesn't seem to have the

problem:

 

Event Type: Error

Event Source: MsGina

Event Category: None

Event ID: 1010

Date: 25/09/2007

Time: 11:12:54

User: N/A

Computer: LYSANDER

Description:

Failed to set the user's home directory (Drive H: connected to Share

\\York\SSmith).

 

When the user starts a session they get only a black screen... as if

reconnecting to an existing locked up session. SP is 2 and I'm running PAE

because it's got >4Gb RAM. This issue is intermittent, and the server

finctions normally in all other respects.

 

I'm not getting the error message discussed, so I'm not sure if that fix

applies to this one.

 

 

Tim

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns99B6D0EC7EF81veranoesthemutforsse@207.46.248.16...

> Any errors or warning in the EventLog?

> Which error message do you get when you try to establish a new

> session to the server (I'am assuming that you can't start a new

> session)?

> Which SP is the server running?

> When this happens, can you still ping the server? Connect to a

> shared drive on the server?

> Check if this applies:

>

> 883670 - FIX: The Terminal Services service stops responding in

> Windows Server 2003 and you receive an "The RPC service is

> unavailable" error message when you try to connect to the terminal

> server by using the Remote Desktop Connection program

> http://support.microsoft.com/?kbid=883670

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "Tim Gowen" <tim.gowen@rafmuseum.org> wrote on 25 sep 2007 in

> microsoft.public.windows.terminal_services:

>

>> I'm seeing a lot of lock-ups with remote users on a particular

>> W2K3 server. I've tried the KeepAlive registry fix, but it was

>> already set to the recommended setting. Power management or

>> screen savers don't seem to be the issue either. The screens of

>> the remote session just go to the background colour, with no

>> icons. They're still shown as connected in the Administrator,

>> but they cannot be made to come alive.

>>

>>

>> Tim

[Guest Vera Noest [MVP]]

Re: TS lockups

 

Are the clients and the server on the same network?

If not, check this, from the Terminal Services FAQ

http://www.microsoft.com/technet/community/en-

us/terminal/terminal_faq.mspx

 

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

screen. Why does this occur?

 

A. This typically occurs if there is a device between the client

and the server that is receiving packets but not passing them on.

One way around this problem is to change the MTU size for the

network adapter that is being used as a terminal server connection

to clients.

 

Ethernet uses a maximum MTU size of 1500. You can start with 500

and then slowly move up until you notice the problem to find the

correct value to set

 

http://support.microsoft.com/?kbid=314825

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Tim Gowen" <tim.gowen@rafmuseum.org> wrote on 27 sep 2007 in

microsoft.public.windows.terminal_services:

> Nothing in the event logs that's out of the ordinary; some 1010

> errors MSGina about a user's home directory, but this user

> doesn't seem to have the problem:

>

> Event Type: Error

> Event Source: MsGina

> Event Category: None

> Event ID: 1010

> Date: 25/09/2007

> Time: 11:12:54

> User: N/A

> Computer: LYSANDER

> Description:

> Failed to set the user's home directory (Drive H: connected to

> Share \\York\SSmith).

>

> When the user starts a session they get only a black screen...

> as if reconnecting to an existing locked up session. SP is 2

> and I'm running PAE because it's got >4Gb RAM. This issue is

> intermittent, and the server finctions normally in all other

> respects.

>

> I'm not getting the error message discussed, so I'm not sure if

> that fix applies to this one.

>

>

> Tim

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns99B6D0EC7EF81veranoesthemutforsse@207.46.248.16...

>> Any errors or warning in the EventLog?

>> Which error message do you get when you try to establish a new

>> session to the server (I'am assuming that you can't start a new

>> session)?

>> Which SP is the server running?

>> When this happens, can you still ping the server? Connect to a

>> shared drive on the server?

>> Check if this applies:

>>

>> 883670 - FIX: The Terminal Services service stops responding in

>> Windows Server 2003 and you receive an "The RPC service is

>> unavailable" error message when you try to connect to the

>> terminal server by using the Remote Desktop Connection program

>> http://support.microsoft.com/?kbid=883670

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "Tim Gowen" <tim.gowen@rafmuseum.org> wrote on 25 sep 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> I'm seeing a lot of lock-ups with remote users on a particular

>>> W2K3 server. I've tried the KeepAlive registry fix, but it was

>>> already set to the recommended setting. Power management or

>>> screen savers don't seem to be the issue either. The screens

>>> of the remote session just go to the background colour, with

>>> no icons. They're still shown as connected in the

>>> Administrator, but they cannot be made to come alive.

>>>

>>>

>>> Tim