I had a similar issue. I installed KDE GUI on top of the server and made it the default display so I could do things directly from the box. I needed to see the hostname hda so I could use Windows 10 to remote desktop to the Linux box hda. I could use Putty and connect with no problem but I wanted to see things like CPU usage, temperatures, and network traffic in a GUI as clients connected to the hda.
Easiest way was to disable the firewall
systemstl disable firewalld
I modified my /etc/sysconfig/network-scripts/ifcfg-eno1 and/or ifcfg-enp1s0 to include:
DHCP_HOSTNAME = "hda" (Amahi blows it away each reboot but the Plex servers don't - see below)
add to /etc/hosts any machines I wanted to connect to
oh - did I mention I am using my router's DNS and DHCP? I gave the hda a reserved address on the router DHCP server by MAC address so it always gets the same IP address.
I edited /etc/samba/smb.conf and changed the WORKGROUP to mine (Amahi has a place to add this).
Then I had problems mapping the drives and writing to them with drag and drop (Windows 10 to Linux). I wanted a back door to move files around while not messing with the Amahi shares specifically for the clients.
I went into /etc/selinux and modified selinux.conf
If you want to keep Selinux I found this worked as well but I have a closed system so I didn't need it.
setsebool -P samba-export-all-rw=1
On the Windows 10 box I did this:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
Either reboot the Windows 10 PC or kill explorer through task manager and start it again.
To remote desktop in I added this:
yum install xrdp
systemctl enable xrdp.service
systemctl start xrdp.service
systemctl enable xrdp-sesman.service
systemctl start xrdp-sesman.service
chcon –t bin-t /usr/sbin/xrdp
chcon –t bin_t /usr/sbin/xrdp-sesman
systemctl reenable xrdp.service
systemctl start xrdp.service
systemctl status xrdp.service
I was then able to browse the hda in Windows 10 clients, map drives, and right click on the hda to remote desktop in giving me the KDE GUI on the Windows 10 box. I needed more than http://hda:9090
. The hda is now in lights-out mode.
Lots of trial and error last week but I documented it - if anyone wants my full install instructions from scratch, send me a PM. There are legitimate reasons for wanting to see the hostname hda on the Windows network and the above reasons were mine so I share the results.
Bottom line is it works.
I have two boxes running hda that I swap out (both same hostname and IP address) and 4 plex servers I'm playing with trying to overload my bandwidth
In the end I find it's easier to just load Plex on top of Fedora because you have control of the files and not Amahi. I like the concept of Amahi but it's very rigid. I'll continue to use both because of different needs and just plain like tinkering with things.
And then there was the iTunes issues but that's another story. I have those instructions as well and it was successful.