What version of Windows 10?

Where I work, there was a complaint about Windows 10 1803 breaking Samba and people being unable to attach to Linux shares. You can find reports of this by Googling. I am running Amahi 11 with Windows 10 v.1903 - no problems here.

I had the same issues with the Amahi 11 Express install. The minimal CD install instructions will work.

Also, +1 for Rufus

I posted the bug report here:
bug 2397

No action on it, but I have found that I can connect to my server using OpenVPN and then Amahi Anywhere works when I'm remote. However, you do have to set up OpenVPN to make that work. It's not too tough, though.

https://wiki.amahi.org/index.php/OpenVPN

System 4.13.9-300.fc27.x86_64 ,x86_64 Platform 11.0.1-1 Core 11.0.0-1 I'm also having problems with Amahi Anywhere when connecting remote from an iPhone. On LAN, everything is fine and OpenVPN is working as well. I see no errors in amahi-anywhere.log. This is what it shows for today, and where it wo...

FYI - figured out the log file question I had. Replace "cat var/log/messages" with "journalctl". Things seem to be running well.

Okay, I completed the upgrade to 10 and it appears to be working. I had a lot of things to work through, but I finally got there. I just sent out the updated certificates to my users and they'll let me know if this was really a successful upgrade. A couple of things... I didn't see easyrsa included ...

This problem is back. I had a power outage here on 9/2 which caused my modem to cycle and a new IP addresses to be assigned. After this happened, I got messages from OpenVPN clients that they could no longer connect to the server using OpenVPN. Investigating it on my end, I see that the IP address t...

This one is resolved. Apparently it was an issue with a switch to SSL for Dynamic DNS and Amahi 8. It was resolved on the Amahi side and I am now back to connecting properly via OpenVPN - it is finding the proper IP address. Thanks for the great support!

The offending line in the OpenVPN client log is: TCP/UDP: Preserving recently used remote address: [AF_INET]123.123.456.456:1194 The problem is my router's external IP address has changed and so this preserved remote address is wrong. Why and where is this address preserved? I'm not seeing a way to ...

Okay, I verified that this is exactly the problem. Modifying the config file to use the current modem IP address, instead of the Dynamic DNS, results in a successful VPN connection. Looks like this one is in your court!

Thanks for the help!