1) your MVP is never sending a request for the receive the dongle
2) or, you have a firewall that is blocking requests to port 16869
3) or, you have a routing issue which is stopping the MVP request from making it to your PC
If you dont manage to work it out from those possibilities, as a next step I could get you to log the MVP startup using Ethereal. Let me know if you want to go down that path, and I'll try to describe what you need to do.
I know there have been several folks that have this problem. Sub most of us have dropped back to 96.x which we had to do or else no MVP. And the wife would not tolerate that. Sorry I can't provide logs for this 97.x problem ... but it is there, and it is real.
There is a lot of people still using the MVP successfully on v0.97.9. I dont think this problem is widespread - otherwise I'd be hearing a lot more about it. That said, there are certainly some people having a problems booting their MVPs though, and I'm trying to work out why.
I asked for information here, and so far have only had two people provide this info, so not much to go on so far, but I am working through it.
I think there are several. I'll have to dig back and see but if memory serves me correclty upwards of a dozen. I can try to run 97.9 on my test PC and have the MVP try to work off it it when the wife is not using the other one. I'll keep you posted.
When I said "Sub most of us have dropped back to 96.x which we had to do or else no MVP" I was talking about us that have the problem, not users without the problem.
the fault I seem to have is random disconnections sometimes after very short periods or sometimes the mvp will play for many hours.
In this particular case I was playing music using musiclibrary2 plugin and had been for about 6 hours when the disconnection happened,
My gbpvr server is also the family PC, the dhcp server is a linux firewall.
There does not seem to be any correlation between activity on the gbpvr server and the failures, it just appears to disconnect for no obvious reason. There is nothing in the event logs with a similar date stamp.
I am running 97.9 but a patch version you issued a few days ago, it reports its assembly version as 1.0.2351.33091, you issued it to try and correct the time taken to load the tv guide at startup.
I was previously running 96.12 which was very stable
Let me know if you want me to increase logging level