RE: Can't connect to Server via Remote Desktop

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I had the exact same problem which was reolved by this article

http://support.microsoft.com/?kbid=815266

Although the error message is different it worked

"Mokupono" wrote:

Ian,

No, the server is NOT a DC. I get the logon screen but when I enter my
username and password I got this "The system cannot log you on due to the
following error: Access is denied. Please try again or consult your system
administrator."

There are no userenv errors in the event logs with the exception of a logon
failure in the security log:

Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon account: placiste
Source Workstation: SFOSRV01
Error Code: 0xC0000064

The credentials entered in the RD utility are the Domain Admin group (of
which I am a member) as well as my own. I stll can't log on.

Thanks,
Patrick



"Ian Williams" wrote:

Hi There,

Is the server you are trying to RDP onto a domain controller? the problem
can happen if the server your trying to connect to cannot query Active
Directory. check the event log for any userenv errors or AD replication
errors.

If it is a DC check communication with the PDC Emulator.

What do you see when you try to connect? does it fail to connect or do you
get the log on screen? are you connecting with the user credentials saved in
the RD Utility?

Let me know how you get on.
Ian williams


"Mokupono" wrote:

I have a W2K3 server that I can't connect to using Remote Desktop for
administrative purposes. I can log in locally and I can log in to my other
servers via Remote Desktop. In the event log I get Event ID: 1219, "Logon
rejected for DOMAIN.COM\username. Unable to obtain Terminal Server User
Configuration. Error: Access is denied."

No one in the Domain Admin group can log in using Remote Desktop.

We are not using Terminal Services, this is for Remote Admin. services only.

Your assistance is appreciated.

Thank you.


.

Relevant Pages

  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ... After that, please post any event log errors, just the EventID# and Source names, not the whole error message. ... error 15100 Win32 Error 15100. ... One is indicating it can't retrieve info about the System log. ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... test network connectivity to local domain controllers. ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ... The File Replication Service Event log test ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ... After that, please post any event log errors, just the EventID# and Source names, not the whole error message. ... (Event String (event log = Directory Service) ...
    (microsoft.public.windows.server.sbs)
  • Re: Server2003 2008 error !!
    ... Remove the x.x.1.x form the NIC of the DCs and configure it as a FORWARDER or use directly the ISPs DNS server as Forwarders in the DNS server properties in the DNS management console. ... On the 2008 make sure the internal firewall is not blocking AD replication, by default the firewall is enabled ion 2008. ... The event log File Replication Service on server ... EventID: 0x000003EE ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2k3: Terminal Services started and then stopped
    ... the terminal services service. ... There are no event log entries. ... Then, after a scheduled reboot, "Remote Desktop" stopped working. ... netstat -an reveals that the server is NOT listening on port 3389 ...
    (microsoft.public.windows.terminal_services)