Yup, this was my fault... I missed the very last CommunityName instance, at the bottom of the headend file. This won't matter for an existing setup because you'll still have the entry from the older slice (which is why when I tested everything seemed fine), but for a new setup it will. I've fixed it now, but any new users (within the last 24 hours) that are having this issue will probably need to do a clear/delete all then rerun guided setup(I didn't increment the slice, just fixed the error and reposted, and if the slice is already there the Tivo won't know that the one on the server has a correction). Again, anyone who had it running prior to 18 Aug need not worry, it's only the headend that went up on 18 Aug that was missing the last Community string and previous installs will have it already.