FWIW, after getting Amahi installed and the shares built the way I wanted, I updated my ubuntu server completely. Still working well.

Sparky's 4th law of debugging: when the issue is insoluble and everything is set up correctly, the problem is a typo.

I set the share to the incorrect location, so though the dlna server was pointing where I wanted it to be, the share was not where it was supposed to be. That should help . . .

I think I have all of that set correctly. network_interface=eth0 friendly_name=Forge Media Server I checked the permissions after doing sudo chown xyz:users -Rv [share root] and I have not found any that are not set correctly. Additionally, I put force group = users force user = xyz in the "ext...

I have exactly the issue described in the initial post. I have a setup very similar to the one described in the first post: media_dir=A,/var/hda/files/Music media_dir=V,/var/hda/files/Movies media_dir=V,/var/hda/files/Homevideo media_dir=P,/var/hda/files/Pictures Specifically I have a films and a ho...

Sorry I'm not familiar with where Amahi DHCP or networking issues would be logged.

One tip that is not part of the official Amahi recommendations but that I believe in: if you are using greyhole storage pooling, move your landing zones to someplace that is NOT your root partition. Once you get your hda running smoothly and configured the way you want it to be, you might think abou...

I'll offer some simple things to check here. No intent to insult anybody's intelligence but this is what I'd look at first with the issues you describe. As for BlackSmith.yourhda.com (in my case) not being accessible to the outside world, ensure that port 80 is forwarded by your home router to the l...

That is the same place. My setup currenty points toward the shares on the Amahi setup page. That location happens to be the landing zone as well. When you check "use storage pool," greyhole then makes the share location a landing zone. [ Post made via iPhone ] http://forums.amahi.org/image...

The reason I mention the landing zones is that the location that BigFoot wrote DLNA should not be set to use /mnt/samba/share. The default /var/hda/files/share works fine. When accessing files remotely, there is no need to access them via the /mnt/samba/share. That is intended for manipulation of fi...

I appreciate you taking the time to help. I hear you about a partition being out of space, but there are NO partitions out of space on my server, as seen here: xyz@ForgeServer:~$ df -h Filesystem Size Used Avail Use% Mounted on /dev/sda6 9.7G 3.1G 6.1G 34% / udev 236M 12K 236M 1% /dev tmpfs 98M 1.4M...