• 0 Posts
  • 1.15K Comments
Joined 1 year ago
cake
Cake day: January 2nd, 2025

help-circle

  • RustDesk is a great option too for just Remote Access. Though I find it’s performance a bit slow, and with VPN I can use any tool I need same as on the LAN (my workflow is unchanged).

    I do use RustDesk for the adhoc situations (friend needs help/new machine, etc). It’s faster to setup for ad-hoc support vs adding a Tailscale client.


  • You’ll need port forwarding to expose RDP yo the internet

    No. Do NOT do this. RDP isn’t designed for the internet, it’s a security hole, even more so in a small business where they aren’t going to use advanced security (2FA, certs, etc).

    Remote access should always be over a secure connection, such as a VPN.

    Never port-forward RDP - you’re just begging to get owned.



  • It sounds like what you really need is a mesh VPN not really KVM.

    Install Tailscale on all the machines and you’re set.

    Alternatively Hamachi.

    Edit: You could also install Tailscale on a single dedicated device on your destination network (such as a Raspberry Pi or mini PC) and configure it as a Tailscale router. This would enable you to access any IP-based device on the network without that device having Tailscale installed on it.

    With any of this you could access machines just like on the local network, using VNC or RDP.




  • Others have mentioned power - you may want to do some math on drive cost vs power consumption. There’ll be a drive size point that is worth the cost because you’ll use fewer drives which consume less power than more drives.

    Having built a number of systems, I’m a LOT more conscious of power draw today for things that will run 24/7. Like my ancient NAS draws about 15 watts at idle with 5 drives (It will spin down drives).

    More drives will always mean more power, so maybe fewer but larger drives makes sense. You may pay more up front, but monthly power costs never go away.

    Also, I’ve built a 10 drive n NAS like this (because I had the drives and the case, mono and ram). It can produce a lot if heat while doing anything, and it was a significant power hog - like 200w when running. And it really didn’t idle very well (I’ve run it with UnRaid, TruNAS and Proxmox).


  • And while more drives means more failure opportunity, it also means when a failed drive is replaced, it’s likely of a different manufacture period.

    I have a 5-drive NAS that I’ve been upgrading single drives every 6 months. This has the benefit of slowly increasing capacity while also ensuring drives are of different ages so less likely to fail simultaneously. (Now I’m waiting for prices to come back down, dammit).









  • Yea, that’s a challenging part for sure, one that I still deal with.

    It can be done, but you need to configure the sync jobs “just so”. Send only from the phone, don’t sync deletions, etc.

    In the past I’ve setup a master folder on my phone and used subfolders for “upload only” Syncthing shares. Then wherever I put a file on my phone it gets synced to the appropriate folder on my server.




  • Its really to compensate for the lack of framers.

    Five years ago the average age of a framer was 55.

    This is what happens when you don’t have a new generation of people trained to do something - constructors have no choice but to use automation.

    I’m not blaming anyone - its just an observation of pressures. Framing’s a tough job.

    There will be massive outlays for the systems, they’ll probably be leased or you’ll have companies that specialise in managing the system, and as a GC you’ll contract them to implement the design.