![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
2·
4 months agoI use it with WAC on my home server and it’s good enough for anything I need to do. Easy to create VMs using that UI, PS not even needed.
I use it with WAC on my home server and it’s good enough for anything I need to do. Easy to create VMs using that UI, PS not even needed.
Last time I did this domain accounts needed to include their domain/upn to logon, so there won’t be any account confusion. However if they were accessing the nas from a domain joined machine, it would use Kerberos anyway so shouldn’t be getting prompted to logon. Obviously that is only for SMB shares, other connection types didn’t use Kerberos.
For real, at the minimum use a virtual machine.
It depends where you want the complexity.
Since ssh is a layer4 tunnel if you don’t run a proxy on your home box, you’ll need a new network connection for each service, if you are fine with that, I would set it up only on the VPS. This means if the tunnel goes down, you should at least get 502 error rather than a timeout or connection refused.
Alternatively you could forward 80, 443 to a proxy service on the home server. That would require two ports for the ssh.
You can drop it to a single ssh connection by having a proxy on both and just have the VPS proxy Http and https to the same port on the home server.