The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

    • @Voersterin Wie mein Toilettenbesuch dann sehr lang ist (normalerweise jede 1.5 Stunden kurz). Grrrrrrrr. 0 minutes ago
    • RT @WIRED: The Apple II computer ceased production in 1993, but that hasn’t stopped fans from continuing to create new programs for it http… 3 hours ago
    • RT @chrisklomp: Dat zeg ik. Dit zijn geen demonstranten. Dit is tuig. 3 hours ago
    • RT @ginnymooy: Oh ah ok. Dus dít zijn de jongeren voor wie een kwart van de bevolking zich maar eindeloos moet isoleren, het 'dor hout op t… 3 hours ago
    • RT @christogrozev: Finally, an official confirmation to our data-driven investigation last summer that proved Jan Marsalek defected to Bel… 3 hours ago
  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,230 other followers

Windows RDP error 3489661694 when connecting from a Mac, connecting from Windows fails without any message

Posted by jpluimers on 2016/05/16

Connecting from Mac OS X edition of Microsoft Remote Desktop
Sometimes I connecting to various Windows systems over RDP fails. On Windows the mstsc (Remote Desktop Connection) application recognises the server has a certificate, presents you with a login dialog, then just stops without any message.

Connecting from Mac OS X edition of Microsoft Remote Desktop does give you error message “The server denied the logon with reason: 3489661694”.

So far I’ve had this only with physical machines running Windows 7 and 8.1 both after a Windows Update did a reboot taking a very long time and I wasn’t physically present to see what was happening (hey: that’s why I use RDP in the first place).

Somehow during the reboot, the server side of Remote Desktop (which is just termsrv.dll in the context of an svchost.exe instance) is in a limbo state: it does listen, but won’t get you any further.

No chance of rebooting either, as most prosumer physical systems lack out-of-band management that server-like systems have.

I found one relevant Japanese post from someone who had the same from Android RDP.

Too bad I could not find anything in the eventlogs, not even why the update took that long (the Windows 8.1 system took from about 23:00 in the evening until 15:00 in the afternoon to get booted).

–jeroen

via:

Screenshot:

 

4 Responses to “Windows RDP error 3489661694 when connecting from a Mac, connecting from Windows fails without any message”

  1. Sam said

    This error happened to me while Windows was restarting to install some updates.

  2. WarrenP said

    What version of OS X and what version of the RDP client is this?

    I use the Mac OS X Microsoft RDP client all the time without incident. You might be able to get some more details by running the client inside ktrace.

    • jpluimers said

      The current RDP client from Microsoft. It gives error messages when the Windows version just times out. So having the error codes is actually a good thing.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

 
%d bloggers like this: