MediaMVP with MVPMC hangs after some time

[HtV]

@ OrakelJos:
Just to be sure (to rule out the cable) I would test with another networkcable.

Hans

[OrakelJos]

I have to assume he wants to go back because he feels the mvpmc dongle is causing the problem and wants to run with the Hauppauge dongle. He might be right.

Martin

Martin: no, I don't assume mvpmc is the problem. I have also problems with the latest Hauppauge dongle which is supposed Vista "proof". In fact I prefer the mvpmc dongle. It is much snappier.

[OrakelJos]

@ OrakelJos:
Just to be sure (to rule out the cable) I would test with another networkcable.

Hans

Will try that, but the compete connection has been tested with a cable tester
Till november 2008 I was running W2K3 on the same server, same GBPVR configurattion, same network and same MediaMVP's without any problems. I therefore blame the problems to W2K8 (=Vista kernel) and not to the dongles or network.

[OrakelJos]

Have been very busy to reinstall the server with Windows Server 2003 R2 Standard. Installed the new GBPVR 1.3.11 and configured from scratch.
Did not apply any TCP/IP tweaks except for the number of concurrent connections which I increased from the default 10 to 50.
The server runs GBPVR, MDaemon mailserver (only for private use), some home automation and monitors my telephone, so a lightly loaded configuration. Even my raid is hardware based so does not have an impact on the processor load.
Will try out the behaviour of the dongle (mvpmc20080930) and let you know the results

[trummel]

I wouldn't bet on it being a w2k8 problem as I get the same thing with an MVP connected via a 10/100/1000 switch to an XP server. I have 3 MVP's connected the same way and have only seen it on one of them - it is the most used though. Think I'll swap a couple and see what happens.

Swapped them all around, all three lose remote control functionality.

[mvallevand]

This problem has been reported on XP. The Hauppauge dongle handles error differently, it simple crashes which often reset to the main menu so it can be masked.

Martin

[OrakelJos]

Had still a crash/freeze (with mvpmc) after going back to Server 2003. Have now returned to the default dongle from Sub, added QoS ( but not yet activated) and gave higher priority to network programs instead of the default file shares. See if this gives any positive result.
In the meantime I have also made a second cable from the gigabit switch to my livingroom as a last resort but not yet used it. First see what the above brings because I don't yet believe it is a hardware problem.
Will be continued............

[HtV]

In the meantime I have also made a second cable from the gigabit switch to my livingroom as a last resort but not yet used it.

I take it that you made the cable according to the standards, I mean: not just the colored pairs straight to the other end but mixed in the right way.

Hans

[mvallevand]

If mvpmc crashes, I'd be happy to look at the logs. If it is the remote that stops responding, emulation made is 100% active, video streaming and everything else works as expected from the client perspective, you can even send keystrokes to the tcp network layer. Where they go at that point is the mystery.

Martin

[OrakelJos]

I take it that you made the cable according to the standards, I mean: not just the colored pairs straight to the other end but mixed in the right way.

Hans

Yes, cable is made up correctly. I have a complete gigabit network in my home and I have a cable tester. Trust me, I know my stuff