Not sure if this has any bearing on this previous issue I had but I had to do a LOT of messing around to get PMS up and running properly on my new build. Unfortunately I didn't keep any of the trace logs but I'll describe the issue as best as I can.
Ok, so prior to today I had no idea what "install as a service" actually meant. Everytime I tried I got an error and didn't bother pursuing the issue. This all changed when I built my new system which is a bit of a horse. Prior to today I would just add PMS to the Startup folder, and leave it to it. Doing this didn't work as something goes wrong with the java when loading. I'm not sure if it's because of the loading being SO fast that it causes an issue, but it's definitely java related as theres about 10 lines of error code telling me so. A "restart" of the server seen everything running perfectly. No matter what settings I changed I would get exactly the same issue, on reboot the ole java issue would raise its head.... restart server = problem solved.
This is ok as long as the PC is running but if the Wife turned it on and wanted to do anything it would be a pain taking her through it all as my mediaserver has no monitor or interface, I solely use remote desktop to manage it.
Soooooo, I turned my attention to the "install as a service". Run as administrator had the service installed, changing the Java directory in the config had it running properly and then configuring the firewall had it running sweet.
Since then the only issue I had was the ole AVI stutter/audio delay issue. I just changed that to forced transcode so hopefully THAT issue is now resolved.
Anyway, and sorry for taking so long to get to the point I just wanted to give a little background, I was thinking that perhaps the issue with the 0.0.0.0 IP was down to people using the start menu to run PMS rather than the install service option? It certainly doesn't work with my current system