Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

RemoteApp constantly showing black screen

Posted on 2010-08-18
9
Medium Priority
?
3,946 Views
Last Modified: 2013-11-21
We are running RemoteApp and constantly face user complaints that they can only see a black screen. They might be able to get it to work again something later.
What could be the cause? Anyway to monitor this?
0
Comment
Question by:frukeus
  • 5
  • 4
9 Comments
 
LVL 11

Expert Comment

by:Coast-IT
ID: 33463092
What happens when they log onto the Terminal Server directly?

Does the black screen happen at the start or during the session?

What do the event logs say on the Terminal Server?

Are the clients connecting over the WAN, how is that connection looking?  Are they suffering packet loss?

0
 
LVL 1

Author Comment

by:frukeus
ID: 33463169
It happens sometimes at start of session or when try to resume a session. I really do not have much info as they are connecting from a wan site. Connection seems to be okay though at times can be lags. Usually when they complain and I login to a server on their site and remoteapp back, I do not face the same issue.
Today I had to log off a users session and it worked normally afterwards
0
 
LVL 11

Accepted Solution

by:
Coast-IT earned 2000 total points
ID: 33469681
Sounds like a bandwidth / packet loss problem.

Maybe run a ping-t to the remote site (crude but effective),a nd see if there are any dropouts, spikes, pr packet loss from the remote location.

Also, check your own connection, make sure there is nothing untoward happening.

Good luck.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
LVL 1

Author Comment

by:frukeus
ID: 33472439
it does look like a bandwidth/connectivity issue but what is strange is when the user complains and I log onto the remote terminal server with their account and use the RemoteApp, it works seemlessly.

On one rare occasion when I was able to remote into the user's PC to run the RemoteApp, I did encounter a black screen.

It would seem that the problem arises when the RemoteApp is initiated from the user's PC but works fine on Terminal Server? The RDP client for the PCs which are running XP, Vista and Win7 are all the latest.

MSTSC.exe for Terminal Server is 6.0.6000.16549
On one of the PC facing the problem 6.1.7600.16385
0
 
LVL 11

Expert Comment

by:Coast-IT
ID: 33473269
Strange this.

I would just do some process of elimination.

Log onto the PC as a new user and see if the problem still occurs.  Maybe recreate a user profile on the affected PC.

Does sound like a bandwidth issue, but profile recreation is always a good place to start.
0
 
LVL 1

Author Comment

by:frukeus
ID: 33473492
But the problem is intermittent - not that the user cannot use the RemoteApp at all. It should not be a corrupted user profile right?

I am wondering if it would help if I shorten the "End a disconnected session" limit

0
 
LVL 11

Assisted Solution

by:Coast-IT
Coast-IT earned 2000 total points
ID: 33474377
I have my "end a disconnected session limit" to 1 minute, this way users think that if they click the X, it closes the app.

And yea, I a clutching at straws with the profile as the problem is intermittent.

Ensure that the users who are remoting to the app have an optmized MTU setting.  This causes all kinds of weird and wonderful problems.  Again, it's worth a try.

http://www.dslreports.com/faq/6266
0
 
LVL 1

Author Comment

by:frukeus
ID: 33482370
I've changed my "End a disconnected session limit" to 1 day. Cannot have it to 1 minute as it would take very long for users to start a new session everytime they try to reconnect.

Will monitor and check out the MTU settings also
0
 
LVL 1

Author Closing Comment

by:frukeus
ID: 34048517
i reckon it could be a combination of bandwidth/latency, extended session limits and high resolution used by multiple monitors causing the problem. Ending  their disconnected sessions and forcing more reconnections seems to have limited the recurrence of the black screen.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
Suggested Courses

971 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question