Recent content by hhspiny

Yes. No need for connect anywhere.

changing to zerotier virtual port network interface made it work in public wifi

Actually, spoke too soon. last time I tested in home. laptop -> cell phone -> internet -> home router -> remotly server. turn on zerotier, can connect. today in public library laptop -> library wifi -> internet -> home router -> remotely server turn on zerotier, does not connect...

This seems to have been fixed in the new releases. not sure which release. it works over zerotier now. I did not touch network IF setting.

I connect back to home router via VPN. either direct VPN via SSPT or with zerotier. I can ping the remotly host, can remote desktop. so the network works fine The host status shows green in client. For SSPT connection, remotly client can not establish direct connection, falls back to...

One other thing I have observed. after in-place upgrading, it often takes a couple of login/logout from hyper-v terminal to admin account, before the boot services starts up and allows access to windows login screen.

This is a niche use case. just to report, not asking for a fix, but hopefully in the future. use win srv 2022 in a hyper-v virtual machine (with GPU enabled). install remotly in admin account only, not in any user account. connect only via PC_Name/administrator instance. everything works...

to update. have been running remotely host inside hyper-v VM (client Win 2022 Srv) with virtual GPU enabled for the last month and it went smoothly.

a potential bug in 1.34 -- if an unauthorized client is connected and waiting for authorization, no other client can make connection.

It would be even better if a specific device(s) within an account is designated as the authorizing device, and shows a notification. or the authorization function can be centralized on the web portal. i.e. batch authorization for multiple hosts. if you have a group of hosts, and want to add...

I would vote for extending the inbound connection list to allow adding to authorized list. mobile phone works, but you need to be around. what if you need to authorize for someone else, and you don't want to do it right then, but rather to take care of it later, and in batch.

Right now, the authorized device is added only via the dialog box that pops up. this creates two problems 1. the dialog box disappears after a while 2. run in booter mode (i.e. no remotly instance in user account), the dialog box does not pop up at all. Suggestions, list the devices that have...

will test quickhost then once I can download the 1.34 version. maybe that also solves the occasional blank-screen.

Follow-up on remotly_boot.exe. with the 1.34 pre-release, which seems to behave the same as 1.33.1 Note, this is in windows 11 (not VM), installed with admin account, start with windows. but do NOT start remotely client in normal user account (i.e. normal user account still uses the admin...

to allow for controlling android device remotely.