VNC - Unable to connect to server

Hello,

Thank you for contacting us on that matter!

In case it could give us some additional information about the nature of the error you encountered, I would like to verify if you have any logs under Help > Application Logs tied to this error.

Best regards,

Hey thanks for your answer :)

I have this error log, only when trying with UltraVNC :

System.Runtime.InteropServices.COMException (0x80020009): You are not connected to any server.
at Interop.ULTRAVNCAXLib.IUltraVncAxObj.Disconnect()
at AxInterop.UltraVncAx.UVNCaxHost.FlushConnection()

Nothing reported with FreeVNC.

So I tried with a new Debian 11 VM for testing purposes and I have no difficulties accessing it with FreeVNC.
It looks like it is indeed a story of proposals and/or compatibility since I try to access on quite old AIX & Linux Redhat server.

How can I configure RDM to be more flexible ?

Thanks,
Marius

Hello,

Thank you for your response!

For the time being, we recommend to try the External display mode, which allows RDM to launch actual VNC sessions using the designated application. This mode is generally more reliable and offers more VNC applications.

Regarding the issue you are experiencing with Embedded VNC sessions, I will open an engineering ticket so our VNC specialist can investigate this issue.

Best regards,

Hello mcouvratd

I'm trying to reproduce the issue here; can you let me know the specific Redhat version and VNC server/version combination that's not working? (For VNC server, I mean tight, tiger, etc etc).

Thanks and kind regards

Hey ! Sorry for the delay, I wasn't at home.

The servers I'm trying to connect are usually Redhat Linux (release between 5 & 7) and AIX (5.X 6.X & 7.X).
And the vnc server running on those are mostly XVNC server.

Does it help ?
I'll be glad to help if needed, thanks,

Marius

Hi Marius

Thanks for getting back to me. I'm going to try and get a lab environment together to evaluate this on my side.

In the meantime, something that would be helpful is this:

• In Options > Types > Others > Other, please check the box "Enable Logging for ARD and VNC"
• You'll need to provide a path to a log file, including a file name (for example, "C:\users\rmarkiewicz\desktop\RDM-VNC-Log.log")
• Apply the changes and then relaunch Remote Desktop Manager

Now, you can retry a problematic connection (ensuring that you are using freevnc - the "VNC Application" on the connection settings should be "FreeVNC"). After it fails the log file should be written to the path you specified earlier and you can send that to me either by PM (click my username then the "envelope" icon) or to rmarkiewicz [at] devolutions.net.

Please let me know if something is not clear.

Thanks and kind regards,

Hey !

It's all clear, I've just done it, here is the only line that output when I try a connexion :

[08:57:28:463] [2924:00002f4c] [ERROR][freevnc.client] - connect failure: 10061

All configuration are set to default, I've just had input the password on the Settings tab.

Let me know if I can do anything else,

Marius

Hello Marius

Just to be sure - you did configure the custom port in the connection as well? (You mentioned using a custom port in the OP).

Error 10061 is "No connection could be made because the target machine actively refused it"; it normally indicates a problem connecting to the specified port (usually by firewall). However you did mention that you're able to connect using the standalone UltraVNC client. So I just want to check that your port configuration is good.

On my side, I'm continuing to investigate the problem.

Thanks and kind regards,

Yes sure ! I'm bluring the fields for paranoiac reasons but I've set the custom port in the frame below :

Hello again Marius

Thanks for the confirmation.

I've set up an initial test environment here with CentOS 7 and x11rdp 0.9.13, but I can't reproduce the problem.

You said that it works with the standalone UltraVNC viewer - what version of UltraVNC do you have? The embedded UltraVNC application is just UltraVNC viewer 1.3.6 wrapped up inside an ActiveX control, so it should fundamentally work in the same way.

When you tested with Debian 11, did you use a non-standard port?

Is there any other configuration we're not seeing? Are you traversing a proxy / VPN / ssh tunnel? Or it's direct connections?

Thanks and kind regards,

Hi ! I think I've figured out what's going on and I'm so confused.

When using UltraVNC as a standalone or some others, I'm connecting to my client using as a host something like [IP]:95, which is as an exemple what we could use as our custom port. I assumed the port used was undoubtedly 95, but it was in fact 5995.
The difference between UltraVNC as a standalone and in your software is that the standalone converts by himself [IP]:95 into [IP]:5995

I had no idea on which port I was connecting to until now.

I'm truly sorry for this mess :)
And I'm glad we figured out.

Marius

EDIT in case it wasn't clear, FreeVNC works perfectly when well used

Hello Marius

No trouble at all and thanks a lot for closing the loop on this.

Please don't hesitate to comment on the forum with questions or comments about the VNC integration.

Thanks and kind regards,