Pls review logs - Random MVP restarts/Failed to Locate GUI Server

[ramalias1]

That is better since it is how I expect mvpmc and GBPVR to work together. For whatever reason the heartbeat (same problem as above example) is lost and in this case the server and not the client kills the connection.

OrakelJos has put a lot of effort into looking at a related problem at http://forums.nextpvr.com/showthread.php?t=39714 and you might want to check on his findings.

Martin

Ok. I'll check it out. Thanks.

I tried few things today. Installed an older version og GB-PVR...reinstalled drivers for the WINTV-PVR150...updated firmware on the router...changed settings on router and all proved unsuccesful.

My computer is not that powerful anymore and my router is a 10/100 Linksys. Do you think the problem could be computer/router related? The comptuter is a Pentium 4 2.8Mhz. with 1GB of RAM.

[mvallevand]

I doubt the problems is related to the verison of GBPVR, the PVR 150 drivers, or the power of the computer. The MVP has terrible networking capabilities which I why I suggested you check out what OrakelJos is doing. I don't have a solution that will prevent this missing heartbeat.

Martin

[HarryH3]

Your computer is fine. Mine is even slower than yours, yet it supports 3 tuners and 2 MVP's without a problem. Data to the MVP's traverses 2 10/100 switches on it's way between the computer and the MVP's.

Perhaps the switch in your router is getting flaky? Most home routers don't "route" data inside the home. They typically just have a built-in 4-port switch to handle moving data within the home. They only route/filter data that moves between the home (LAN) ports and the outside world (WAN) port.

Also make absolutely certain that the PC firewalls are configured correctly. More than a few of us have been burned when a Windows Update re-enabled the Windows Firewall after it had previously been set to "Off". :eek:

[mvallevand]

HarryH3 I don't think it is firewall, this problem looks similar to the lost remote problem that others have reported (it is nice to see a Hauppauge log with the same symptom). The only difference is that GBPVR is actually forcing the client off which is unusual.

Martin