No - it doesn't apply with your setup. It might only have applied if you were running a s/w firewall on the host server itself. Router-based firewalls don't (normally) process traffic on what is considered the internal network - only between the internal and external networks. Oh well, I thought I'd suggest it anyway.
I turned off my anti-virus last night to see if that was possibly interfering, but the problem still persisted...
I played around with Beyond TV and the open source plug-in that works with the MediaMVP and while Beyond TV is very impressive, the plug-in is just a replacement of the Hauppauge Media Server interface (or so it appears). So it doesn't carry over all that same functionality to the MediaMVP as GB-PVR does...
-Charles
[SIZE="1"]NextPVR v2.3.4 on XP Home SP2 Rig: Dual Core P4 2.8GHz, 3GB Ram + 230GB HD Media: WinTV PVR-150/MCE (2) + Media MVP 1000 (1) vD3A Tools/Plug-ins:Weather, ComSkip, NEWA[/SIZE]
Okay. I seem to have found a solution to my problem!!!
It seems that changing my host computer's NIC (Broadcom 440x) setting for "Speed & Duplex" from "Auto" to "100 Mb Full" does the trick!
I'm not sure I understand why that would be... but it seems to be even more stable now with the wireless adapter than it did when I had it wired so this probably was a problem all along but was only made worse by the wireless connection.
Now I'm looking forward to the next GB-PVR release which should work even better with a MSDE backend!
-Charles
[SIZE="1"]NextPVR v2.3.4 on XP Home SP2 Rig: Dual Core P4 2.8GHz, 3GB Ram + 230GB HD Media: WinTV PVR-150/MCE (2) + Media MVP 1000 (1) vD3A Tools/Plug-ins:Weather, ComSkip, NEWA[/SIZE]
[b Wrote:Quote[/b] (cginzel @ Dec. 31 2004,09:53)]It seems that changing my host computer's NIC (Broadcom 440x) setting for "Speed & Duplex" from "Auto" to "100 Mb Full" does the trick!
I'm not sure I understand why that would be...
Under normal circumstances, the hardware at both ends of an ethernet connection would be set to Auto and would effectively negotiate speed and duplex modes. There are occassions, however, when the two ends 'misunderstand' each other and they end up running in different modes. As long as they both use the same speed, you will get communication but if one is running as full duplex (can send and receive simultaneously) and the other as half duplex (one or the other at any given time), you would normally see a great deal of packet loss etc.
With a 'real-time' application such as streaming video (or even audio), timing is obviously critical but with all the packet loss going on, the jumbled communication will effectively breakdown.
Just think of a television interviewer talking to somebody via a satellite link where there is a several second delay - if the two don't observe a half-duplex approach then the conversation becomes unintelligible.
I've read in other forums that supposedly the MediaMVP runs at half-duplex, but when I set my host NIC to "100 MB Half" it would still cut out, but at full-duplex is works without a hitch!
I suppose it could have something to do with the fact that I have a wireless adapter and router between the host PC and the MediaMVP.
-Charles
[SIZE="1"]NextPVR v2.3.4 on XP Home SP2 Rig: Dual Core P4 2.8GHz, 3GB Ram + 230GB HD Media: WinTV PVR-150/MCE (2) + Media MVP 1000 (1) vD3A Tools/Plug-ins:Weather, ComSkip, NEWA[/SIZE]
These settings are for physical and not logical connections.
The fact that you have several boxes (PC, router, wireless bridge, MVP) in the mix doesn't actually matter - it is the physical link between your PC and the router that is important. The Auto discovery is presumably failing (normally a bug in a NIC driver) and the router is expecting 100BT/FD but the NIC driver is using 100BT/HD.
It doesn't matter what the MVP wants as it isn't physically connected to the PC - as long as it and the wireless bridge are happy at the physical level and the PC and router are happy at a physical level then things should work fine.