One issue that may make it even more difficult to troubleshoot is that Microsoft no longer supports WHS 2011 and hasn’t since April 2016. Not sure how many updates they send out now that impact WHS2011 but it’d be difficult to duplicate the issues with a sundown product.
Have you considered moving up to a current version or another more current server?
Agreed, this one of those stupid issues that you do not know where to start looking for the cause. Now you mention that WHS is not supported anymore and they removed SMB support from Windows, it looks like a “perfect storm”.
Maybe it is time for more drastic measures.
Moving to another server, yes I was/am thinking about it. The hardware of the servers, I am running 3 of them, is also coming into age now. Only issue is the involved cost, we are talking about large amounts of data.
To test, I could swap the OS of one of the servers from WHS 2011 to Win 10 Pro and see if that solves it. Will take some time though…
Not sure what constitutes a “large amount of data” but there are some pretty low cost NAS devices now that work great with Infuse. I run a WD MyCloud and it works great. You can add an additional hard drive off the USB port on that and have a pretty substantial amount of storage.
Not a windows person but the Microsoft Server 2016 seems to fit the bill and has been recommended as a go to for those upgrading from MHS 2011.
Also having issues with this. I thought it was something to do with Infuse no longer waking the NAS. If I restart the ATV then it works. If I access the drive with my laptop or Sonos it wakes and Infuse works. I’m using a Synology Play 214 with Wake On Lan activated.
Maybe run Linux on your hardware? I have CentOS 7 running on hardware that is 10+ years old. Installed PMS and configured SMB and I havent had any probs with connecting to shares since I installed the OS about a year ago (even after running updates).
I disabled Atmos and it resolved the issue. To be honest, the only reason I installed infuse was to use my Plex with my Atmos on the Apple TV. Is this an issue that will be fixed in an update? Or is it more of a core issue with the Apple TV so infuse won’t be able to stream Atmos using Plex?
Wired or WiFi connection for the ATV? If WiFi maybe try a temporary Cat 5E or 6 cable. If wired try a new cable? I just got bit a few months ago with an “almost bad” Ethernet cable. Changed it and all stalls and lost connections disappeared.
I have a 4K Apple TV connected to a synology server connecting through SMB over ethernet. Infuse has always worked really well for me. Then I upgraded to the Apple tvOS 12 beta. Right after doing so I get the error loading content message. Never happened before the beta.