Should TS Gateway be functional?

Hi,
Could you send me in a private email the .rdp that you use in Windows?
edited by dhervieux on 10/31/2013

FreeRDP does not support the auto detect. Perhaps it's the problem.

Like David said, the auto-detect is not supported in FreeRDP. Right now, to use a gateway, you have to specify the server details.

I've looked at this and realise the UI is not intuitive if you have created the connection with the auto-detect option on the Windows version. There needs to be a warning or something. We will work on enhancing this.

Thanks, Richard

I'm not sure I understand what you guys mean by auto-detect.

On RDM Windows, I have the LOCAL "Computer name" entered on the "General" tab and in the "Connection" tab, I have "Use these RD Gateway server settings" selected and the RD Gateway hostname is entered in "Server name".

Pretty much the same thing appears for the same connection(s) on RDM Mac but it seems to be trying to connect to the local host name without taking into account that it needs to connect to the RD Gateway first.

i'm also having problems using ts-gateway.
I'm using ms rdp for mac the new one and i'm also getting these error.

TS-Gateway is implemented and should work with the settings you have, however the support is still somewhat experimental. I will revalidate this functionality.

Thanks, Richard

Hi,
I've talked to Marc André from FreeRDP and he asked me to send him the .rdp. Export to .rdp will be available in the next beta release.

Hi,

The new beta release is out (0.9.5.0).
You can now export rdp connection to rdp files
"Check of Updates" to download the latest version

Thank you
edited by dhervieux on 11/5/2013

Hi,

As a test, can you let me know what happens if you specify the credentials for the gateway?

e.g. Under the gateway address, click 'Credentials...' and specify the gateway credentials.

Thanks, Richard

Hi,

When i specify my credentials i'm able to login.
whitout credentials i got the error.

That's the thing, for all my connections, the "Credentials..." button is disabled/greyed out. Switching back and forth between the no gateway/use gateway radio box doesn't bring it back.

I've also tried clearing the text in "Server name", choosing "Do not use RD Gateway server" and saving the connection. Then going back in it, it's still on "Do not use..." but the text is still in the field and the "Credentials..." button remains disabled regardless of the value of the radio box.

Finally, creating a new connection brings back the "Credentials..." button and specifying all the settings and credentials finally work. Problem is, I have over 30 connections like that :(

The culprit may be the database version? When I first ran the Mac version, we were still on version 8 of the Windows version. It asked me to upgrade the database to a version I don't remember and I accepted. It got me thinking that I should upgrade the Windows client to version 9. When I did, it asked me to upgrade again. I don't remember this version either but I do remember that it was above the one the Mac version upgraded to. I thought I may have broken the Mac version connectivity but it still worked. At least it seemed to..?

Is there an easy way to retrieve my current database (MSSQL) version?
edited by ekred on 11/6/2013

Ok, additional information. Adding credentials to the gateway on the Windows version brings back the "Credentials..." button on the Mac version.

In other words, if a connection has been created on Windows without specifying credentials, it keeps Mac users from being able to specify them.

Another test.

I have a folder with several connections that use the same credentials. I setup the credentials at the folder level and setup all underlying connections to use "inherited" credentials. For the gateway, I used "Use my RD Gateway credentials for remote computer", which is a bit backward as it's pretty much the opposite happening (remote computer credentials used for RD Gateway).

Everything works marvelously well on Windows but disables the "Credentials..." button on Mac as well as return a "Can't connect" error message.

Hi

Thanks for the detailed feedback on this.

First, I'm glad that by specifying credentials you are able to connect to the gateway. So that is working well.

It seems there are a few problems with the UI, particularly when dealing with connections created on the Windows client. We will work on fixing this. It's not 100% straightforward as the Mac client can not support all the same options as the Windows client.

We will give this area some attention to get this smoothed out. Obviously re-creating 30+ connections is not a good solution! :)

Thanks, Richard

Hi,

I have just released a new version (0.9.11.0) with enhanced support for configuring the gateway.

The user interface now more closely mirrors the Windows version, so connections that were created on Windows should carry their settings over more cleanly.

There are a few pieces that still won’t work, because they aren’t supported by FreeRDP. We don’t have a way of highlighting that in the UI currently, so if you use any of the following options, it is likely that they gateway connection will not work:

- Smart card authentication
- Automatically detect RD Gateway server settings

Additionally, I am aware of the following issues:

- “Open gateway only when unable to ping host” is not currently implemented
- “Bypass RD gateway server for local addresses” is not currently implemented. On Windows, this is supplied by the Microsoft API. However FreeRDP doesn’t support this option, so we will have to implement it ourselves.

I am also aware of some bugs when selecting both “Allow me to select later” and “Use my RD Gateway credentials for the remote computer”. Essentially, the authentication prompt does not currently allow you to specify the domain - we need to fix that.

Finally, the “Store password on the local computer” option obviously will not carry a password over from a Windows machine! On OS X, we store the password in the system keychain. This is implemented but support should still be classed as experimental for now.

We still have some issues to work on, but it should be much better now. Please let me know any feedback you might have.

Thanks, Richard

Yes, everything feels much better now. Thanks!

About the "Use my RD Gateway credentials for remote computer" option. On Windows, I have my credentials saved in the parent folder. The connections are setup to use inherited credentials and in the RD Gateway settings, I simply select "Use my RD Gateway credentials for remote computer" and it works fine. Will this eventually work on Mac as well? Because it currently doesn't.

Thanks!

Hi

I'm glad it's looking better! :)

The goal is to have feature parity with the Windows version, where possible. So we will work on making this behaviour the same

Thanks, Richard