After enabling Remote Desktop Connection (terminal services) on a standalone server, the server does the following when any user (including local admin) attempts to login: Processes the login, successfully authenticates user, logs the user out immediately. This happens both at the console and via terminal services. What the heck is going on?

i have the same problem, but after doing that: - install w2k server on partition C: - install w2k3 on partition D: - save those 2 partitions on 2 files with ghost 2003. - install w2k PRO on partition C: - save partition c: with ghost 2003 - restore w2k3 on partition D: At this moment, i have to use recovery console from w2k3 CDROM, in order to have dual-boot with w2k3 activated. Finally, the same problem occurs, so my w2k3 partition can't be used !!! as brian have the same problem with a different source, i suppose then that my problem may not due to partitions (MBR, etc...). But i'm not sure, because all is fine if, instead of restoring w2k3, i reinstall w2k3 completely (that is not what i want). Any idea ? Thanks for your help... Ari.

sounds like windows may have a modified or corrupted .dll file on it :) that can cause it to lock you out, and not work, especially if you got a virus that modified any of the winlogon dependancies, winlogon.exe, dpcdll.dll, licdll.dll, are just a few to name is there any other error messages it shows up, or does it just log you off? try safemode, if safemode dont work it probably is a virus or modified dll file that is causing hte problem.