3

I've got a Windows Server 2003 R2 Standard SP2 running. When I try to connect to this server using Remote Desktop I get the following error popup:

"The system cannot log you on due to the following error: The RPC server is unavailable."

In the event log of the server I get the following event: "Logon rejected for Domain\administrator. Unable to obtain Terminal Server User Configuration. Error: The RPC server is unavailable." (Source: Winlogon, Event ID: 1219)

What can I do to fix this problem? I got no clue which RPC server this refers to.

4 Answers 4

5

Create the following Registry key

HKLM\System\CurrentControlSet\Control\Terminal Server
Name: IgnoreRegUserConfigErrors
Type: REG_DWORD
Value: 1

Reboot the server, and try logging in via RDP.

3
  • Allright. I have VMs on VSphere, there are 2 (two) VSwitch: LAN and DMZ. Few days ago I got "Error: The RPC server is unavailable." while RDP using IP DMZ. Registry patch is working, now RDP using IP DMZ is fine. To whom had technical reference regarding this issue, please do not hesitate to share. Thank you.
    – Rhak Kahr
    Nov 26, 2014 at 6:33
  • 1
    This has been observed on more recent Windows versions too. Sadly, the root cause is still unknown.
    – Massimo
    Feb 19, 2021 at 17:04
  • @Massimo I believe the root cause is some type of incompatibility between Server 2003 and modern patched Domain Servers that causes the 2003 Server RPC Service to be unable to retrieve the RDP (Terminal Server) configuration information for the user's account from AD, and this registry setting has 2003 ignore the problem.
    – NetMage
    Mar 16, 2022 at 20:08
1

Are there any other errors in the event log, not related to terminal services? We need to determine if this is a problem with Terminal Services, or with the RPC service.

I have often seen this error 'TCP/IP NetBIOS Helper' service running? I've often seen the fact that this service was stopped cause this error.

The fact that you have an error accessing your group policy file may be related. One thing you can try is to check if "File and Print Sharing" is enabled on the adapter your trying to RDP too, if its not, turn it on and see if you can connect then.

6
  • The netbios helper service (and remote registry) are running. There are no other error messages at the same time. There are some messages because the server is unable to access the domain gpt.ini ("the format of the specified network name is invalid).
    – Sam
    Nov 9, 2009 at 13:26
  • "File and Print Sharing" already is enabled on the (only) network connection of the windows server 2003 I'm trying to connect to. I opened another question for the GP problem.
    – Sam
    Nov 9, 2009 at 14:02
  • Dang - I just installed all "optional updates" I could find, and now it works. Seems like someone already has fixed this? Thanks nonetheless!
    – Sam
    Nov 9, 2009 at 14:44
  • No problem, glad that its working now!
    – Sam Cogan
    Nov 9, 2009 at 14:52
  • 1
    Well, actually it is only working intermittendly. After some uptime connection fails, after a reboot it will work again.
    – Sam
    Aug 20, 2010 at 11:55
0

I'm having the same problem. Do you find an answer for this?

I found this link http://support.microsoft.com/kb/555839 that says

There can be a few reasons for this problem:

 1. Incorrect DNS settings.

 2. Incorrect Time and Time zone settings.

 3. The "TCP/IP NetBIOS Helper" service isn't running.

 4. The "Remote Registry" service isn't running.

I have checked all of these and file and print sharing and still get the error.

-1

Check it is accessible the Domain controller by \\<domain Controller>
Check the date, time and Time Zone
Check if any AV/firewall is blocking the traffic(software/hardware) or any traffic filtering device block the traffic

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .