Anthony Pidden's community posts

We could manage a remote session, but it might have to be an assisted view-only session unless we have an agreement in-place, due to the nature of the data we hold and the access this system provides.

We are UK based (GMT+0).

I'm sorry, I'm not sure what you mean? There is only a field for a port, not a address to listen on.

Do you think that IPv4 and IPv6 ports are somehow different?
It's not like IPv6 ports are with letters while IPv4 ports are with numbers...

Please do as originally stated and pass this on to someone who is familiar with networking.

Pauline wrote:

Hello Anthony,

Thank you for your patience and apologies for the delay.

Could you please send us a screenshot of your Server's Port Manager window?

Looking forward to your reply.

As requested. I've included all dialogs available, up to and including the edit port window. I also took the liberty of including the IP-filter window for completeness.

Has there been any response from the developers?

It has been over a month so-far with no reply 😢

Has there been any response from the developers?

Thanks, Pauline. I have followed the instructions to the letter.
The RU host/viewer settings are irrelevant if the RU server isn't listening on an IPv6 interface.

I can tell my RU hosts and RU viewers to use IPv6 for the RU server until the cows come home, but it won't work if the RU server isn't listening and accepting connections via IPv6.

I've provided all of the information above to prove this case and I have read and followed all the guidance and previous posts.

As expected, trying to connect either the RU host or RU viewer to the RU server using IPv6 fails because the RU server is only listening on IPv4 interfaces.

I'm pretty sure RU server in it's current form doesn't support IPv6; either that or I am missing some setting to enable it.

netstat

shows pretty clearly it is only listening on IPv4 interfaces (

0.0.0.0:5655

), IPv6 port scan confirms this.

I thought perhaps because the server obtained its IPv6 address via DHCP that RU server was ignoring it, but even with manually configured IPv6 settings it does not listen on

[::]:5655

(which would be what it would show if it was listening on IPv6)

In case I am missing something, it would be great if someone can confirm what extra steps need to be taken to enable IPv6 support in RU server.

This is how services listening on all IPv6 interfaces in Windows would appear:


This is how the RU server is listening, which is IPv4 only. For it to listen on IPv6 as well it would show an additional entry:


As can be seen using an IPv6 scanner, the port is open but there is no application listening:


This was taken using the current latest version of RU server (3.3.5.0)

Hey Pauline,

No AV on the server.
Viewer has been used on machines with Kaspersky AV and also a machine with just Windows Defender (i.e. nothing), same results.
Host machines both with KAV and without exhibit the problem as described.

I think that pretty much rules out AV.

Aside from the firewall appliance in front of the RU server, no software firewalls are used.

I'll see if I can get some logs from the ru-server and viewer.

Using viewer 7.1.2.0, host 7.1.2.0 and ru-server 3.2.1.0

ru-server is hosted in a DC, viewer and host are on different business-grade connections

My problem is as follows:

• Host shows as online
  
• Attempt to connect (any action, doesn't matter)
  
• Instantly get 'Unable to connect. Attempts left: ' dialog. Host now shows as offline
  
• When dialog times out after 5 attempts, host will show as online again after a short interval
  

Here is a short screen-cap demonstrating the issue:


A temporary solution appears to be to restart the ru-server, but this doesn't always last very long. The issue varies in how frequently it presents.

I suspect something happens with the firewall in front of the ru-server that the ru-server/hosts don't recover from or the lack of IPv6 on the ru-server (most of the hosts are dual-stack with IPv6 connectivity but the ru-server is not currently configured with an IPv6 address)

This is quite problematic for us as not all operators have access to restart the ru-server (not to mention it is very frustrating when it does it multiple times in longer support sessions).

Any help greatly received.

Ticket 3744 opened.

Host logs just show 'Internet-ID ErrorCode <> 0' with 'Error code: 1' 150 seconds after 'Internet-ID: Connection established' after which it attempts to reconnect, rinse, repeat.