I was waiting until 2.14 to post this, hoping the update would help. In just the past few weeks I've moved to a permanent client/server model with NPVR.
I'm having a re-occurring, random problem with my HD-PVRs arranged in a client/server setup. Often, I start LiveTV and it works great. When I stop LiveTV and attempt to restart it, I'll get the "please wait..." dialog and it'll just sit there and time out.
If I go and visit the server, I'll see the HD-PVR it attempted to use has it's "bling" lights on. It is as if the "stop" livetv command from the previous viewing on the client isn't stopping the HD-PVR, which then fails to start up the next time.
NPVR still thinks that HD-PVR is in use for LiveTV. The only way to reset it is to exit out of NPVR on the server, power cycle that HD-PVR, and startup NPVR again.
I have two HDPVRs connected, I've swapped them around to make sure one isn't behaving badly (one is actually brand new). It has randomly happened with both.
I've made sure firewalls are off on both client and server as well as used the actual statically assigned IP address server address on the client instead of relying on DNS.
Server and client are hardwired on a GIG switch (not a router, a real switch.)
Any advice would be most appreciated.
I'm having a re-occurring, random problem with my HD-PVRs arranged in a client/server setup. Often, I start LiveTV and it works great. When I stop LiveTV and attempt to restart it, I'll get the "please wait..." dialog and it'll just sit there and time out.
If I go and visit the server, I'll see the HD-PVR it attempted to use has it's "bling" lights on. It is as if the "stop" livetv command from the previous viewing on the client isn't stopping the HD-PVR, which then fails to start up the next time.
NPVR still thinks that HD-PVR is in use for LiveTV. The only way to reset it is to exit out of NPVR on the server, power cycle that HD-PVR, and startup NPVR again.
I have two HDPVRs connected, I've swapped them around to make sure one isn't behaving badly (one is actually brand new). It has randomly happened with both.
I've made sure firewalls are off on both client and server as well as used the actual statically assigned IP address server address on the client instead of relying on DNS.
Server and client are hardwired on a GIG switch (not a router, a real switch.)
Any advice would be most appreciated.