Can't connect to Windows Server 2012 - Error 131084

Hi,

Sorry it took us a long time to reply.
The error message you get comes from tcp timeout check.
I'm not entirely sure the error your error is a timeout and the function maybe hiding something else.
I have builded a debug version for you to try to get more information.
You can download it here https://www.dropbox.com/s/ydjuf6tu01wq7vc/RemoteDesktopManager.app.zip?dl=0

You will also need to set your log filter to com.freerdp.*:trace.

Regards,

Just sent you the log through Private Message.

Thank you looking at it right now

Hi Jesper,

After reviewing your log and FreeRDP code it seems the 15 sec. timeout is not enough for you.
When you connect with Microsoft Remote Desktop of Windows is it long to connect?

Just to make sure there is no other issue hidden behind it, could you try with this version which has the timeout removed:
https://www.dropbox.com/s/l5dlm6w3z6pr22o/RemoteDesktopManager2.app.zip?dl=0

Best Regards,

Benoit, Microsoft Remote Desktop connects instantly (a couple of seconds), but I will try the version without the timeout and see what happens.

Now I get this after a LOOOONG time: The RDP client terminated unexpectedly, I will send the log through Private Message.

I've looked into your log file and the only odd thing is that it looks like it tried to connect 4 or 5 times. It took around 1 min 15 sec, each attempt.

Is there something different with this computer? Is it on another network?

Another few questions:
Are you connection through a Gateway?
Did you try to connect with the IP address?

Best Regards,

This one in particular is not behind a gateway, but behind a VPN. All other servers are fine, and so is it when using Microsoft Remote Desktop Connection.

I will try the IP address first and let you know.

Ok, the last response was from me, not sure why it got marked as "Guest"...


IP address is the same. If I try it a few times, it often starts working, but I noticed something else, when using the Microsoft Remote Desktop application, it takes 7-8 seconds before it gets to the "Negotiating Credentials..." screen, almost consistently. Other remote desktops are "instant", so there is something in the original protocol negotiation that drags it out somehow, and RDM seems to fail on that.

I wish I could give you more info, I'm happy to do more debug files, just let me know.

Hi Jesper,

The problem seems to be related to your VPN.

May I ask what kind of VPN do you use?

Is it possible for you to give us access to a computer on the other side of this VPN.

Best Regards,