Terminal Services logon problem

Posted on 2004-04-09
Last Modified: 2010-04-19

I have a windows 2003 server box in "remote desktop for administration" mode. It has worked fine until very recently where now if I connect to the box via remote desktop, I am asked for my username and password, which I enter, but when I click OK it gets as far as "applying settings", then it says "saving settings", then "logging off", and then the RDP connection is dropped. This is the same for all users including the administrator. Nothing is logged in the event log.

Any ideas?
Question by:tomt84
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
LVL 20

Expert Comment

ID: 10796778
See if someone has disabled remote desktop option on the server. Could be that simple ;-)

Author Comment

ID: 10796984
No it all appears to be switched on in the ts manager.

Cheers for your suggestion, any  other ideas?

LVL 20

Expert Comment

ID: 10799296
Check under My Computer - properties - Remote and see if Remote Desktop is ticked.
(Ignore the XP part 2003 is the same):
Industry Leaders: 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!


Author Comment

ID: 10801568
yup remote desktop is indeed already ticked. Sorry!!

Accepted Solution

berdt earned 500 total points
ID: 10854620
I had the same problem, in my case it was caused by the (WHQL!) NVIDIA detonator driver I downloaded from
Other video drivers might have the same problem.
Uninstall your video driver, reboot and try to connect with RDP again.

The driver I downloaded from works fine with RDP sessions.

In my case, nothing was being logged either.

Removing everything related with nvidia from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run and HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run did not solve the problem, so it must be the driver itself.

Very weird, I spend hours to figure this out!


Berdt van der Lingen

Author Comment

ID: 10856637
Genius. You're a star. Many thanks!!

Featured Post

Enroll in June's Course of the Month

June’s Course of the Month is now available! Experts Exchange’s Premium Members, Team Accounts, and Qualified Experts have access to a complimentary course each month as part of their membership—an extra way to sharpen your skills and increase training.

Question has a verified solution.

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

Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …

734 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