Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 445
  • Last Modified:

Terminal Services logon problem

Hi

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?
Tom
0
tomt84
Asked:
tomt84
  • 3
  • 2
1 Solution
 
What90Commented:
See if someone has disabled remote desktop option on the server. Could be that simple ;-)
0
 
tomt84Author Commented:
No it all appears to be switched on in the ts manager.

Cheers for your suggestion, any  other ideas?

0
 
What90Commented:
Check under My Computer - properties - Remote and see if Remote Desktop is ticked.
(Ignore the XP part 2003 is the same):
http://www.microsoft.com/windowsxp/pro/using/howto/gomobile/remotedesktop/enableremote.asp
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
tomt84Author Commented:
yup remote desktop is indeed already ticked. Sorry!!
0
 
berdtCommented:
I had the same problem, in my case it was caused by the (WHQL!) NVIDIA detonator driver I downloaded from nvidia.com.
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 windowsupdate.com 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!

regards,

Berdt van der Lingen
0
 
tomt84Author Commented:
Genius. You're a star. Many thanks!!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now