Search results

Hmm. Maybe this problem is related with these Virtual adapters. Is it possible to disable them for test an leave only one physical?

Maybe there is more than one and Remotly is not using the one it should.

One more question. How many network adapters do you see in ipconfig /all

We will try to sort this out as soon as possible. If it works for them it must work for us.

BTW soon you will be able to install your own relay server so that direct connection and connect anywhere will work with almost identical latency. This will solve all problems.

I'm also sometimes connecting using mobile network. But in this case direct connection works from time to time (i think it depends on the BTS i'm currently using, if it does not block p2p it works). So i'm also having a similar test case. I will now need to check with VPN.

Are you connecting from 2 different networks? Port forwarding has no sense in the same network. We will figure it out. But it must work as I use it everyday. My setup is as follows: HOME: 1 Router with firewall connected (cable docsis). On this router I have port forwarded 42015 to my Android...

They work on Android, I use it at home. I need to set a port on Android and then port forward it on my router to connect to our lab. Without setting this port (in this case I use the default 42015) I cannot connect. So it must work. Setting this in local network should not matter. It is intended...

I will forward these issues to our QA team for them to replicate.

In LAN the direct connection should always work without any problems. I have never had any problem with direct connection in LAN. Is there a problem when you set the same ports on Android and PC server?

Hmmm.. that is very strange. We will need to reproduce this in our labs using Tailscale. There are no limitations on our side.

You can use Wireshark to check the RDP connection what ports are used and then set the same Inbound/Outbound ports in Remotly server and also Outbound port in Android app.

Does the connection work using Connect Anywhere? Maybe you need to set fixed P2P ports for direct connection? It should work (I think some users connect using VPN). If RDP works then the problem is 99% related with ports.

We will add this together with the upcoming Remotly HUD. We will add a "stats" button that will show all useful information.

Thank you vamp! We will check it out. But it will be much more difficult on our side as we do not use WebRTC on the Remotly server. We need to implement a wrapper (it will work in parallel with our own protocol whenever someone is connecting from the web browser). So for native clients like PC...

Wow! Thank you for this amazing workaround. I'm sure this will help other users with the same problem! I'm going to test is myself today. Thanks vamp!

By the way we have found a solution to this problem but it only works on AMD. We run a Hyper-V virtual machine in GPU sharing mode. Then we connect to this VM using Remotly when the monitor is turned off. Complex :/

I found this "Monitor RM HDMI Phantom Display Silver". It costs 3USD and after pluging into any of the hdmi ports that is not occupied should work like a charm (by making the DisplayPort run normally even after turning off the monitor attached to it).

Thank you vamp! It will be integrated in v1.12.0 update. Please do check the screen blanking thread as we want to improve this as much as possible before going into additional drivers.

Hmmm. This driver is used when running hyper-v virtual machine. I will need to double check it. "The "turning always on" method is not working on me, because if not use remotly it also turn on and it disturb my family." I don't quite understand. Does the blank not work for you? Or the problem...