Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

We don't want to give users remote desktop access to the server so we have published applications on the surver and created RDP files that the users run.

This works great on every user's pc with the exception of one machine. Each time this one machine runs the RDP file it crashes after about 10 -15 seconds. Here is the error message from the event viewer:


Event Type: Error
Event Source: Application Error
Event Category: None
Event ID:    1000
Date: 07/18/2012
Time: 10:07:26 AM
User: N/A
Computer: (X'D OUT)

Description:

Faulting application mstsc.exe, version 6.1.7600.16722, faulting module 
ntdll.dll, version 5.1.2600.6055, fault address 0x00010ef4.

The weird part is... we can run the Remote Desktop Connection from the start menu and it connects to the server just fine.

Has this happened to anybody and what did you do to fix it?

share|improve this question

migrated from serverfault.com Jul 18 '12 at 17:20

This question came from our site for professional system and network administrators.

add comment

3 Answers

I have seen this error a couple of times with mstsc.exe. I would recommend the following.

  • Do a memory test on the computer with the error. ntdll.dll errors can occur when you have a bad stick of RAM or other memory errors occur.
  • Ensure the computer is up-to-date - install all recommended system updates
  • Try repairing your installation of Windows
  • Try to RDP into another server to ensure it's nothing on that particular server that's causing the problem. I know it sounds weird but we had a user who's computer was giving us similar problems because of a remote printing tool known as ScrewDrivers. Un-installing that caused the problem to stop so we knew that was the offending service
share|improve this answer
add comment

Get the ntdll.dll from a computer that does not have this problem and replace it.

share|improve this answer
add comment
up vote 0 down vote accepted

Solved the problem by removing an invalid Printer on the client machine.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.