Hostnames not working on mac osx Remotedesktopmanager

Resolved

Hostnames not working on mac osx Remotedesktopmanager

avatar

RDM: 2024.1.8.6
MACOS 14.4.1

When using rdm for a connection like ssh and the defined hostname is not an ip but a FQDN the connection fails.
The Log shows connecting to (any). It looks as if the hostname is not resolved before trying to connect.
It's not my mac
Opening a normal terminal and using nslookup returns the correct ip.

Can someone recreate the issue. Entering an IP instead of a hostname works perfectly.
I use a hostname because i am using dyndns. The hostname is public und therefore it is not a local dns problem.

Can someone recreate or fix that?

All Comments (3)

avatar

Hi,

I have opened a ticket to investigate the issue you reported.
To assist us in this investigation, could you please provide us with the log files?

Best regards,

Gabriel Dufresne

avatar

Connection Log File in this message:
The SSH-Connection's log file only shows the following on verbosity 4:
---------- Log Start
[5/12/2024 12:42:44PM] Devolutions Protocols version: 2024.2.9.1 macOS
[5/12/2024 12:42:44PM] Terminal font: Menlo [Menlo, fixed=True]
[5/12/2024 12:42:44PM] Starting SSH, verbose level: 4
[5/12/2024 12:42:44PM] Setting up connection
[5/12/2024 12:42:44PM] Connecting to port: 1030 (IP any)
-------------- Log End

I assume it cannot resolve the hostname and is therefore not connecting.
The hostname I entered is publicly resolvable and not a local entry.
nslookup is working against 1.1.1.1.

Furthermore the same problem occurs on Windows with Remotedesktopmanager.
Is there a known bug with resolving hostnames altogether when they are not part of the local dns server but public?

Furthermore the connection works with the same private key and hostname in my terminal.
So it really only affects remotedesktopmanager.
If i resolve the hostname manually in my terminal and enter the ip directly in the connection configuration the connection is established successfully.
As the IP is dynamic I would really appreciate resolving hostnames working again.

Do you need further logs or information?

Regards


avatar

Hi,

I've been looking into your issue, but I was not able to reproduce it. The "(IP any)" in the terminal is normal. Here's how my ssh shell connection setup with a hostname looks, can you compare it with yours and let me know if you have something different that could affect the connection ?


When I use this connection, it connects without any issue to the ip the domain is linked to.


I suspect you may have entered the wrong port, because if I enter the wrong port, I get a log similar to yours:



Please, verify that you entered the correct port ( in your log it says 1030 ). If you did, then let me know the settings of the entry you use to connect to the ssh that you modified so we can reproduce the issue. Feel free to also try creating a new ssh shell entry with only your host, port and credentials to see if that works and let us know the results.

An other thing that could help us is to have the error message. Usually, when a ssh connection fails, it will show a message such as "Operation timed out" or "Host not found". Let us know if you get any message like that



Best regards,


Maxim Buisson

Screenshot 2024-05-13 at 1.18.11 PM.png

Screenshot 2024-05-13 at 1.03.24 PM.png

Screenshot 2024-05-13 at 1.03.04 PM.png

Screenshot 2024-05-13 at 1.02.10 PM.png