V5 Broke my MVP

[PGPfan]

Not true John Colburn,

I'm using the XP firewall and an MVP with Sage just fine!

The Hauppauge manual likely means that the 'Hauppauge software' will not work with the XP firewall. I guarantee you they don't do testing of their product with Sage, since they offer NO (software) support if not used with their software.

-PGPfan

[MeInMaui]

My MVP just quit working last night with these same symptoms (sageTV splash screen flashes once and then the screen stays black) I tried using the new mvp.bin and also tried deleting the contents of the clients folder. The splash screen behavior would just flash repeatedly in some instances and the duty cycle of the flashing changed with the alternate mvp.bin. Unfortunately nothing I tried would allow the mvp to boot into the sage UI. Has there been any progress on this issue? I do have a rotating daily backup of my sageTV folder going back 7 days, so I'll try restoring to the last time I knew it worked to see if that helps. I would appreciate any suggestions. Thanks.

Aloha,
Mike

[BobPhoenix]

Originally Posted by MeInMaui

My MVP just quit working last night with these same symptoms (sageTV splash screen flashes once and then the screen stays black) I tried using the new mvp.bin and also tried deleting the contents of the clients folder. The splash screen behavior would just flash repeatedly in some instances and the duty cycle of the flashing changed with the alternate mvp.bin. Unfortunately nothing I tried would allow the mvp to boot into the sage UI. Has there been any progress on this issue? I do have a rotating daily backup of my sageTV folder going back 7 days, so I'll try restoring to the last time I knew it worked to see if that helps. I would appreciate any suggestions. Thanks.

Aloha,
Mike

Have you unpluged/repluged the power cord to the MVP? Have you shutdown/restarted your SageTV Server? That's what usually fixes the black screen for me. I guess you must have since you tried the new MVP.Bin. So nothing further to suggest.

[MeInMaui]

Originally Posted by BobPhoenix

Have you unpluged/repluged the power cord to the MVP? Have you shutdown/restarted your SageTV Server? That's what usually fixes the black screen for me. I guess you must have since you tried the new MVP.Bin. So nothing further to suggest.

Yup, I did all that. I did, in the end, finally fix the problem by restoring my most recent known-good backup of the sageTV directory (2-days old). After that everything is working fine again. I'm guessing that something must have gotten corrupted. Man, I'm glad I instituted daily automatic backups a while back! Thanks for the suggestion.

Aloha,
Mike

[John.Kelly]

Originally Posted by John Colburn

No matter how many ports were opened, the Hauppague MVP could not find the Sage server.

Hauppague MVP manual states MVP will not work with XP firewall. Make your network vulnerable to anyone and it works.

Otherwisw, forget the MVP.

For many, the real problem is that there is an undocumented port that has to be opened for the XP firewall. The documentatioin I am referring to is the Sage TV Version 5 Manual, pages 217 & 218. An easy way to establish that your MVP connection is an XP firewall problem is to simply turn off the XP firewall and see what happens. If, all of a sudden, they work, your problem is the firewall and the information below should be of help!

Already an exception in the XP Firewall after installing SageTV version 5:

SageTV
C:\Program Files\SageTV\SageTV\SageTV.exe

From Pages 217 & 218 of the SageTV 5.0 User's Guide:

SageTV Communication Port 1 - TCP 42024
SageTV Communication Port 2 - TCP 7818
SageTV Discovery Port - TCP 8270
SageTV Discovery Port - UDP 31100
SageTV EPG Server - TCP 7760
SageTV Media Extender Booting Port 1 - UDP 16867
SageTV Media Extender Booting Port 2 - UDP 16869
SageTV MVP Port - TCP 31099

Port I added to get this running:

SageTV undocumented Port - 16881 UDP

[Opus4]

BTW: The port 16881 is listed in the forum's FAQ and the list has been updated in the v6 manual. Any other port listing issues, please let us know.

- ANdy

[stevech]

If your LAN is connected to the Internet via a NATing router, then why run XP Firewall? (one reason, I suppose, is kids' PCs and their tendency to get viruses).

[roxy99]

Originally Posted by stevech

If your LAN is connected to the Internet via a NATing router, then why run XP Firewall? (one reason, I suppose, is kids' PCs and their tendency to get viruses).

I disabled XP firewall when I got my NAT router. Never had a problem. I don't even have antivirus on the Sage server.

[stevech]

Originally Posted by roxy99

I disabled XP firewall when I got my NAT router. Never had a problem. I don't even have antivirus on the Sage server.

But do you have teenagers using PCs on your LAN?

[roxy99]

Originally Posted by stevech

But do you have teenagers using PCs on your LAN?

No. Nor Peer-to-Peer, Kazaa, Limewire or any of the sh&t. I like to keep my system squeeky clean

You have a point. Anyway, openning the port like Andy said would work, assuming its XP firewall causing the problem.

[stevech]

Originally Posted by roxy99

No. Nor Peer-to-Peer, Kazaa, Limewire or any of the sh&t. I like to keep my system squeeky clean

You have a point. Anyway, openning the port like Andy said would work, assuming its XP firewall causing the problem.

I have a NATing router like most everyone, and I have a 24/7 PC with a web server (not Microsoft's IIS), and Sage. Neither have been wacked by the Internet due to the router, over several years.

WIndows firewall is for folks that don't have a router or have nasty untrustworthy PCs on their LAN, or who don't encrypt their WLAN.