Forum / Remote Desktop Manager Mac - Bug Report

Not able to connect to server. 131081 error

  • Create an Issue
  • Cancel

Hi Devin,

Unfortunately, the log file you sent us doesn't contain much that can help us.
I've looked into it with our in house RDP specialist and our conclusion is:
-The unable to set TCP_NODELAY error shouldn't crash the session
-The log is missing some information about what is crashing.

The last entry in the log file is not consistent with the rest of the file but it contains an error that suggests that RDM is not able to resolve your Gateway name. You could try to use the IP Address in your session on the Gateway and the ones who connect through it.

One other thing you could try is to change the Transport parameter from Default to RPC in your session that connects through the Gateway.
It's the older way to communicate with a Gateway server but it could workaround the issue you might have if it's with RDP 8.

One more thing you could do to help us find out what is going on:
-Export a working session with Microsoft Remote Desktop to an rdp file
-Export a non-working session with Remote Desktop Manager to an rdm file
-Send me the 2 files in a Private Message.

We will analyse if there is something we missed that could cause an issue.

Best regards,

Benoît Sansregret

signaturesignature

Clock3 yrs

Hello,

Sorry for the delay, it has been abnormally busy around here. I've created an RDP file for a server that doesn't work in RDM, however the RDP file connects successfully. I'm sending it in a PM now. Thanks!


Thank You,

Devin Walker

Clock3 yrs

Hello,

Just checking up to see if there were any discoveries. Did those RDP and RDM Files help?


Thanks,

Devin Walker

Clock3 yrs

Hi Devin,

We are still working on your issue and we didn't made any notable progress.
We are also working on a complete rewrite of our RDP Engine that should make it more stable.
I'll update you as soon as I have something

Best regards,

Benoît Sansregret

signaturesignature

Clock3 yrs

Hi Devin,

I forgot to ask you yesterday did you try to change the Transport to RPC?
2016+11+10+10+45+23

Also, could you tell me what is the version of windows you are using on the gateway?

Best regards,

Benoît Sansregret

signaturesignature

2016-11-10_10-45-23.png
Clock3 yrs

Hello,

Switching to RPC didn't help. The gateway server is running Windows Server 2012R2. Please let me know if you need any additional info. I will be on vacation until next Tuesday after this work day.


Thanks,

Devin Walker

Clock3 yrs

Hi Devin,

After speaking with our in-house RDP specialist about your issue, we are still a little baffled by your issue.
We would like you to check the Gateway logs on your gateway server.
You should be able to access them through the Event Viewer under this path Application and Service Logs\Microsoft\Windows\TerminalServices-Gateway\Operational

We don't know exactly what kind of entry to look for but there should be something showing up when you are unable to connect.
Also, there might be a policy configured that is getting in the way of establishing the connection between your Mac and the Gateway through RDM.
As we are using an openSource named FreeRDP for our RDP session there might be a message that is not sent correctly and one of the policy you might have is blocking the connection.

If we can identify what is blocking you it will be easier for us to fix the issue.

Thank you for your patience.

Benoît Sansregret

signaturesignature

Clock3 yrs

Hi There,

Sorry for the delay, I got back from vacation and was playing catch up. It seems you've recently released a new version which addresses this issue. Thanks for the help.


Thanks,

Devin Walker

Clock3 yrs

Hi Devin,

The fix that was included in the latest version did not address your issue directly.
If it has fixed your connection problem then it's a good news.

We are also reworking the FreeRDP integration and we are already seeing promising improvement on connection stability and reliability.
We can't wait to have something to release.

Best regards,

Benoît Sansregret

signaturesignature

Clock3 yrs