problem connecting to remote machine

Hi Darko,

Are you using the hostname or IP address to connect to the machines, or are you using the Wayk Den ID?

You can enable the logs on the client following the instructions here: https://helpwayk.devolutions.net/index.html?kb_logs.htm

Best regards,

I use Wayk Den ID.
Finally I succeed in connecting via wayk now after enabling wayk now/wayk service incoming and UDP outgoing traffic.
But I can't connect to server when in unattended mode.
I will delay further testing for some time and try again latter in month or two.

Thank you for help.

Hi Darko,

Thank you for testing Wayk Now and sorry that it didn't work out of the box the first time. I would like to let you know that we are currently working on a solution to simplify authorizing Wayk Now traffic through restricted network environments. However, it should be available in a month or two. The current Wayk Now peer-to-peer connection is UDP based and functions like the WebRTC standard. This is good for many reasons (NAT traversal) but it is not easy to allow in a firewall because the inbound UDP ports change every time. Our work in progress solution that we would like to offer is a TCP relay that would require allowing a single outbound TCP port in the firewall. Let me know if this is the kind of solution that would better fit your needs as opposed to the current solution (UDP, random inbound ports).

You can also help by telling me more about your network environment and the type of firewall you are using. Is it the built-in Windows firewall, or something else? Ideally, by the time you evaluate our solution again, we should have fixed the current issues you encountered.


Best regards,

sorry for delay.
It is great to hear you are working on improving unattended support.
Yes allowing only one outgoing port would be much better, like TV.
Many networks don't even filter/block outgoing connections so remote access would work without any problems.

My situation depend on client environment.

Hi,

It's been some time since the last post, but in the meantime we managed to produce a working prototype where a Wayk Now peer-to-peer connection was performed entirely using two outgoing TCP connections to a custom TCP relay server we built. Performance is actually quite good, so this option looks very viable for restricted network environments. We now need to make it possible to properly negotiate this option as an alternative to the UDP-based protocol and perform complete integration and testing, but my guess is we should be able to make it available soon after the holidays. I will likely ask you to try it out when we have something ready to test on our side.

Best regards,

Hi


The 3.1 release is now available for download, and includes the option of using a TCP relay server.

The setting can be found under the "Connectivity" section - you need to enable "Prioritize relay servers for peer-to-peer connections". Note you only need to enable the setting on one "side" of the connection (you do not have to instruct the remote user to change anything).

I would recommend you to give this a try in your environment :)


Thank you for your patience,

wayk 3.2.1
.msi enterprise trial install on both machines.
Win10-1809 > win2012r2

I made simple next next install, set "Prioritize relay servers for peer-to-peer connections" (even on both sides) but I'm not able to connect to win2012r2 machine.

For test I also tried teamviewer next next install on win2012r2 and connection is working.

To me it looks like wayk still have problem working with machines behind firewall/NAT.

I have also noticed under "file\options\Connectivity" "wayk den user" section where I can login as wayk den user.
I even registered computer for remote access but no sucess.

Then I have tried connect to server with public IP and there was a problem until I have enabled all outgoing connection.

What outgoing port need to be enabled?
For TV it is TCP 5938

It would be nice to have something like this
https://community.teamviewer.com/t5/Knowledge-Base/Which-ports-are-used-by-TeamViewer/ta-p/4139

Hi,

The "Prioritize relay servers for peer-to-peer connections" (Devolutions Jet relay) requires TCP/8080 outgoing to be allowed on both sides. I agree that a dedicated knowledge base article on which ports are used by Wayk Now is a good idea.

When not using the TCP relay servers, the peer-to-peer connectivity makes use of STUN/TURN protocols, similar to WebRTC. In this case, UDP port 3478 is used, but the real port of the peer-to-peer connection changes every time, making it hard to allow through a firewall, unfortunately. If the firewall has options specific to STUN/TURN traffic (it's a standard, a lot of routers and firewall recognize this type of traffic) then you can try enabling it this way.

You can also send us the logs so we can tell where the connection failed (https://helpwayk.devolutions.net/index.html?kb_logs.htm).

Best regards,

8080 was a missing link.

It is working now :)

I can continue playing with wayk and unattended access.