Forum / Remote Desktop Manager Mac - Bug Report

Not able to connect to server. 131081 error

  • Create an Issue
  • Cancel

I just downloaded the latest version of Remote Desktop Manager Free - v2.5.0.0, I created a new embedded connection and when I try to connect I get the error Failed to connect to the host. Check your credentials and try again (131081). I'm using a gateway server to connect, so I tried unchecking "use my RD Gateway credentials for remote computer" and entering my credentials for the gateway. Now I get the error "The peer connection was lost"
Next I changed the display type to External, when I tried to open a session I see that the Microsoft Remote Desktop program is launched, I'm prompted for my password and I connect w/o a problem.


Why is the embedded session not able to connect?


thanks,
John.

Clock5 yrs

Hi Rossini,

The External mode launches Microsoft Remote Desktop with your session information with the limitation that the credential cannot be provided.

The Embedded/Undocked mode uses FreeRDP to connect to your server.

The error message you received when you were using the Embedded mode means that the authentication failed. Normally this is caused by a mistake in User Name/Password. It can also be caused by checking/unchecking the Activate Network Level Authentication check box in the connection tab of the session.

Tell me if that solved your issue

Benoît Sansregret

signaturesignature

Clock5 yrs

Hi Benoit,
I have verified my username & password are correct, I've tried connecting to several servers but I always get the same error.
I hadn't noticed the "Activate network level authentication" before so left it at the default of checked.
I tried unchecking it, I know you said it could cause the problem, but I tried anyway, and I still got the same error.

John.

Clock5 yrs

Hi John,

Thank you for your report will look into that as soon as possible

Benoît Sansregret

signaturesignature

Clock5 yrs

Hi,

Your issue seems a little more complicated than expected.
I would suggest to try our previous version http://cdn.devolutions.net/download/Mac/Devolutions.RemoteDesktopManager.Mac.2.0.4.0.dmg

Tell me if it works for you

Benoît Sansregret

signaturesignature

Clock5 yrs

Hi,
v1.1.16.0 and v2.0.4.0 both give me the same error
John.

Clock5 yrs

Hi,

We just released a new version that might help you with the sessions issues but it also contain 2 new really nice features.
You can download it here http://mac.remotedesktopmanager.com/Home/Download.

The first feature is RDP session logging. This will allow your Embedded RDP session to log everything it does behind the scene in a file.
Just set the filter like the screen shot and set the file to a unique file for your session like this:
Session+FreeRDPLogging%5b3%5d

You can then send the file to us so we can analyse what is going on. Careful this file will contain sensitive data so you might want to check it first and you certainly don't want to post it on the forum.

The second feature is the option to rollback to previous version of the RDP Engine without having to download the previous version entirely.
You can do this for an individual entry in the session configuration:
RDPEngine+++Session%5b3%5d

Default means it will take the value from the preferences (see below).
V2 is the stable version from previous version
V3 is the latest version with fixes and instability

Or you can change it for all session with the preferences:
RDPEngine+++Session%5b3%5d

Default is the Latest version (V3 right now)

V2 is the stable version from previous version
V3 is the latest version with fixes and instability


Try it and tell us what you get.
edited by Benoit Sansregret on 7/29/2015

Benoît Sansregret

signaturesignature

RDPEngine - Session[3].png
RDPEngineMac-Pref[3].png
Session FreeRDPLogging[3].png
Clock4 yrs

I have downloaded the latest version, and have created the .log file for you to look at, where should I send it?

Clock4 yrs

Hi,

You can send it directly to me bsansregret@devolutions.net
I will make sure someone look into it.

Benoît Sansregret

signaturesignature

Clock4 yrs

Hi,

We just released a new version that improve RDP stability.
I'm not absolutely sure it will fix your issue but i hope there is an improvement.

You can download it here http://mac.remotedesktopmanager.com/Home/Download

Tell me if it worked for you,

Benoît Sansregret

signaturesignature

Clock4 yrs

Benoit
I've downloaded the latest version, and it has the same issue.
John.

Clock4 yrs

Hi John,

We just released another version which contain fixes for Embedded RDP session.
You can download it here http://mac.remotedesktopmanager.com/Home/Download
I don't think it will fix you issue but if you could try it, it would be great.
If it doesn't fix your issue send me an other log as your problem might have change to something else.

Best Regards

Benoît Sansregret

signaturesignature

Clock4 yrs

Hi Benoit,

I hate to revive an old thread but I'm having this issue with the Enterprise version. Funny thing is it only happens with newer servers we add to the list. Servers that have been in the list for a while work fine. Also if I try to connect to these servers using the Windows version, it works fine. All settings should be the same since we are hosting these entries on a Devolutions Server. I switched the version to V3 and V4 which gave me the same error and V2 gave me a "Not Connected" error. Any assistance would be greatly appreciated. As always I look forward to working with you and your amazing support team.


Thanks,

Devin Walker

Clock3 yrs

Hi Devin,

Benoit is on holiday. I'll be checking this issue with you.

Could you send me (via private message) another log of your RDP session after reproducing the issue?

One other thing, Benoit mentioned the RDP Engine option under the General tab. Is it possible that your sessions do not use the same RDP engine? Maybe you've set a particular version to those older sessions and the recently added one use the default one.

Best regards,

Xavier Fortin

signaturesignature

Clock3 yrs

Hi Xavier,

I've sent you the requested logs via PM. Please let me know if you need anything else.


Thanks,

Devin

Clock3 yrs

Hi Devin,

Out of curiosity, could you try the other RDP Engines? The default one should be V4. Could you try V3 and V2 and tell me if you get the same issue?

Best regards,

Xavier Fortin

signaturesignature

Clock3 yrs

Hi again,

Are you still connecting through RD Gateway? If so, do you use different sets of credentials for your RD Gateway and the machine you try to connect to? For both the RDP host name and the RD Gateway Server name do you use the machine names or ip addresses? If you use IP Addresses could you try with the names only?

Best regards,

Xavier Fortin

signaturesignature

Clock3 yrs

Hi Xavier,

As mentioned, I've attempted this with every RDP version. I am using a gateway and the credentials match that of the servers I'm connecting to 90% of the time but in both scenarios the error is still generated. I was using IP addresses but I altered one to use the hostname and that still produced the same results.


Thanks,

Devin Walker

Clock3 yrs

You've mentioned that the issue only occurs on recently added server. Could you recreate one of the functioning session and set only the minimal options required for it to connect (Host name, credentials, etc.) and try it? If it doesn't work could you export this session and the functioning one (remove any sensitive information, like passwords) and send it to me via private message?

If older previously added sessions work but not the most recent ones, I can only suppose that it has something to do with the sessions config.

Best regards,

Xavier Fortin

signaturesignature

Clock3 yrs

Hi Xavier,

I'm going to PM you both the original, working RDM file and the non-working file. Please let me know if you require any additional information.


Thanks,

Devin Walker

Clock3 yrs

Hello Xavier,

Did you get my PM? Has there been any update on this?


Thanks,

Devin Walker

Clock3 yrs

Hi Devin,

I am back from vacation and Xavier is now on vacation and I don't know when he will read your message.
I will try to get your message from him but in the mean time if you could send me the PM you sent him I would be able to help you a little bit faster.

Apologize for the inconvenience

Benoît Sansregret

signaturesignature

Clock3 yrs

Hi Devin,

I finally got your message from Xavier. Unfortunately, the two files are exactly the same. The only difference is the stamp line which is updated every time you update the entry.

The ID line should be different if you are sending me 2 different entry.

Could you try to re-export them?

Best regards,

Benoît Sansregret

signaturesignature

Clock3 yrs

Hey Guys,

I hate to revive an old thread but the issue seems to have gotten worse after a Devolutions Server upgrade from 2.x to the latest version. I'm also running the latest version of RDM. None of the computers will connect me anymore. Please find error in the log below. I never quite got around to exporting those users that you asked for but I'm happy to if still needed.


Thanks,

Devin Walker

[10/25/2016 8:15:32 PM]INFO RDP - OnConnected:131081 / Failed to connect to the host. Check your credentials and try again (131081).
[10/25/2016 8:15:32 PM]ERROR SILENT Failed to connect to the host. Check your credentials and try again (131081).

Clock3 yrs

Hi Devin,

Unfortunately, the only thing your log is saying is that for some reason our RDP component wasn't able to authentify your user.
To rule out any relation between your DVLS upgrade and your issue could you try to connect to a server using quick connect (the lightning button at the top of the main window). If that doesn't work, it means that the DVLS upgrade has no link to your issue.

I will also need the RDP logs of a session that fails to connect. See the instruction here: How to enable and send RDP Logs

Best regards,

Benoît Sansregret

signaturesignature

Clock3 yrs

Hello!

The quick connect did not work, however I had to way to insert a gateway server, which is required. I've pulled the the logs as requested and it seems to be failing to auth with our gateway server. I used Microsoft Remote Desktop to access our gateway server and I logged in successfully using the same credentials that RDM is using.

[17:23:14:346] [9139:b0970000] [INFO][com.freerdp.client.mac] -[MRDPIPCClient initLoggingWithFilter:filePath:fileName:] 117 - Log initialized headless
[17:23:14:346] [9139:b0970000] [DEBUG][com.freerdp.client.mac] -[MRDPIPCClient configureInternal] 90 - configureInternal
[17:23:14:372] [9139:b0af6000] [INFO][com.freerdp.client.common.cmdline] freerdp_client_load_static_channel_addin 2492 - loading channel rdpdr
[17:23:14:372] [9139:b0af6000] [INFO][com.freerdp.client.common.cmdline] freerdp_client_load_static_channel_addin 2492 - loading channel rdpsnd
[17:23:14:372] [9139:b0af6000] [DEBUG][com.freerdp.channels.cliprdr.client] cliprdr_VirtualChannelEntry 1365 - VirtualChannelEntry
[17:23:14:372] [9139:b0af6000] [INFO][com.freerdp.client.common.cmdline] freerdp_client_load_static_channel_addin 2492 - loading channel cliprdr
[17:23:14:372] [9139:b0af6000] [DEBUG][com.freerdp.channels.drdynvc.client] drdynvc_VirtualChannelEntry 1626 - VirtualChannelEntry
[17:23:14:372] [9139:b0af6000] [INFO][com.freerdp.client.common.cmdline] freerdp_client_load_static_channel_addin 2492 - loading channel drdynvc
[17:23:14:372] [9139:b0af6000] [DEBUG][com.freerdp.core.nego] nego_set_negotiation_enabled 1193 - Enabling security layer negotiation: TRUE
[17:23:14:372] [9139:b0af6000] [DEBUG][com.freerdp.core.nego] nego_set_restricted_admin_mode_required 1205 - Enabling restricted admin mode: FALSE
[17:23:14:372] [9139:b0af6000] [DEBUG][com.freerdp.core.nego] nego_enable_rdp 1227 - Enabling RDP security: TRUE
[17:23:14:372] [9139:b0af6000] [DEBUG][com.freerdp.core.nego] nego_enable_tls 1239 - Enabling TLS security: TRUE
[17:23:14:372] [9139:b0af6000] [DEBUG][com.freerdp.core.nego] nego_enable_nla 1251 - Enabling NLA security: TRUE
[17:23:14:372] [9139:b0af6000] [DEBUG][com.freerdp.core.nego] nego_enable_ext 1263 - Enabling NLA extended security: FALSE
[17:23:14:372] [9139:b0af6000] [DEBUG][com.freerdp.core.nego] nego_connect 154 - state: NEGO_STATE_NLA
[17:23:14:372] [9139:b0af6000] [DEBUG][com.freerdp.core.nego] nego_attempt_nla 422 - Attempting NLA security
[17:23:14:606] [9139:b0af6000] [DEBUG][com.freerdp.client.mac] -[MRDPIPCClient validateX509Certificate:] 551 - validateX509Certificate
[17:23:14:665] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rdg] rdg_process_out_channel_response 355 - Out Channel authorization required
[17:23:14:739] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rpc] rpc_virtual_connection_transition_to_state 700 - VIRTUAL_CONNECTION_STATE_INITIAL
[17:23:14:883] [9139:b0af6000] [DEBUG][com.freerdp.client.mac] -[MRDPIPCClient validateX509Certificate:] 551 - validateX509Certificate
[17:23:14:884] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rpc] rpc_in_channel_transition_to_state 420 - CLIENT_IN_CHANNEL_STATE_CONNECTED
[17:23:14:885] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rpc] rpc_in_channel_transition_to_state 420 - CLIENT_IN_CHANNEL_STATE_SECURITY
[17:23:14:040] [9139:b0af6000] [DEBUG][com.freerdp.client.mac] -[MRDPIPCClient validateX509Certificate:] 551 - validateX509Certificate
[17:23:14:042] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rpc] rpc_out_channel_transition_to_state 566 - CLIENT_OUT_CHANNEL_STATE_CONNECTED
[17:23:14:042] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rpc] rpc_out_channel_transition_to_state 566 - CLIENT_OUT_CHANNEL_STATE_SECURITY
[17:23:14:042] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rpc] rpc_in_channel_transition_to_state 420 - CLIENT_IN_CHANNEL_STATE_NEGOTIATED
[17:23:14:043] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rts] rts_send_CONN_B1_pdu 503 - Sending CONN/B1 RTS PDU
[17:23:14:043] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rpc] rpc_in_channel_transition_to_state 420 - CLIENT_IN_CHANNEL_STATE_OPENED
[17:23:14:094] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rpc] rpc_out_channel_transition_to_state 566 - CLIENT_OUT_CHANNEL_STATE_NEGOTIATED
[17:23:14:094] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rts] rts_send_CONN_A1_pdu 447 - Sending CONN/A1 RTS PDU
[17:23:14:094] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rpc] rpc_out_channel_transition_to_state 566 - CLIENT_OUT_CHANNEL_STATE_OPENED
[17:23:14:094] [9139:b0af6000] [DEBUG][com.freerdp.core.gateway.rpc] rpc_virtual_connection_transition_to_state 700 - VIRTUAL_CONNECTION_STATE_OUT_CHANNEL_WAIT
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.gateway.rpc] rpc_client_default_out_channel_recv 550 - error! Status Code: 401
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.gateway.http] http_response_print 609 - HTTP/1.1 401 Unauthorized
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.gateway.http] http_response_print 609 - Content-Type: text/plain
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.gateway.http] http_response_print 609 - Server: Microsoft-IIS/8.5
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.gateway.http] http_response_print 609 - WWW-Authenticate: Basic realm="** I edited the gateway server name out **"
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.gateway.http] http_response_print 609 - WWW-Authenticate: Negotiate
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.gateway.http] http_response_print 609 - WWW-Authenticate: NTLM
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.gateway.http] http_response_print 609 - X-Powered-By: ASP.NET
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.gateway.http] http_response_print 609 - Date: Wed, 26 Oct 2016 22:23:14 GMT
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.gateway.http] http_response_print 609 - Content-Length: 13
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core] freerdp_set_last_error 698 - freerdp_set_last_error ERRCONNECT_AUTHENTICATION_FAILED [0x20009]
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.gateway.tsg] tsg_connect 1760 - tsg_check failure
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.nego] nego_connect 160 - Protocol Security Negotiation Failure
[17:23:14:147] [9139:b0af6000] [ERROR][com.freerdp.core.connection] rdp_client_connect 276 - Error: protocol security negotiation or connection failure
[17:23:14:147] [9139:b0af6000] [DEBUG][com.freerdp.client.mac] -[MRDPIPCClient viewDidConnect:] 401 - viewDidConnect
[17:23:15:657] [9139:a50c11c0] [DEBUG][com.freerdp.client.mac] __39-[MRDPClient invalidatePasteboardTimer]_block_invoke 133 - timer stop
[17:23:15:657] [9139:b0970000] [DEBUG][com.freerdp.client.mac] -[MRDPClient releaseResources] 113 - Failed to unmap shared memory object: Invalid argument (22)

Clock3 yrs

Hi Devin,

Your log tells me that for some reason your RDP Gateway is refusing your Mac access.
The most obvious reason would be invalid credentials feeded to the Gateway server.
Could you make sure the gateway credentials are correct by first making a session that connects directly to the Gateway server?
If that work, configure the Gateway server by typing the username, domain and password directly inside RDP Entry.
2016+10+27+09+47+11
This is the most direct way to configure it.
Don't check the Use my RD Gateway credentials for my remote computer.

Tell me what you find.

Benoît Sansregret

signaturesignature

2016-10-27_09-47-11.png
Clock3 yrs

Hello,

Thank you for your response. I was able to connect directly to the gateway server using those credentials and Microsoft's RDP Client. I have yet to attempt this using RDM. I will give this a shot when I get to the office. As for storing the password locally, I've attempted that as well. In addition, I had one of my colleagues who owns a Mac attempt to replicate this issue and he had the same issue with the Gateway server rejecting his credentials. I will update you again when I have some additional information.


Thanks,

Devin Walker

Clock3 yrs

Hello,

I was unable to make a successful connection to the gateway server. I took the liberty of obtaining the RDP logs for that server as well, which I'll PM you since they are lengthy. I seem to get a flood of the following error:

[14:17:34:335] [1830:b066a000] [ERROR][com.freerdp.core] freerdp_tcp_connect 1172 - unable to set TCP_NODELAY

Followed by:

[14:17:34:336] [1830:b066a000] [ERROR][com.freerdp.core.transport] transport_write 734 - BIO_should_retry returned a system error 22: Invalid argument
[14:17:34:336] [1830:b066a000] [ERROR][com.freerdp.core.nego] nego_connect 160 - Protocol Security Negotiation Failure
[14:17:34:336] [1830:b066a000] [ERROR][com.freerdp.core] freerdp_set_last_error 698 - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x2000C]
[14:17:34:336] [1830:b066a000] [ERROR][com.freerdp.core.connection] rdp_client_connect 276 - Error: protocol security negotiation or connection failure

I hope this helps, it's really work inhibiting since I can't login to any server. Again this affects all Mac computers running RDM, but PC's work fine. Additionally, I can use Microsoft Remote Desktop and login successfully to the gateway.


Thanks,

Devin Walker

Clock3 yrs

Thank you Devin, I'll investigate the issue and come back to you.

Benoît Sansregret

signaturesignature

Clock3 yrs