MVP cannot get IP with 4.1.6

[spence]

Well after a long weekend and much playing with network snapshots I found in my particular setup that my MVP was being also grabed by not only SageTV but also Hauppauge's code!!!

In my test setup I had a fresh, clean XP profesional install with NOTHING ELSE except I installed Hauppauge's code (beta) to test the MVP was working but then I did an uninstal via the start, all programs route of Hauppauge own code configuration and didn't remove it by windows (their code also, but...)

Well to make a long story short their was STILL active code running in the background with me thinking that it was all gone!

Did a search of MVP*.* and found 3 files!!! One was an .exe and once I did a compleate deleate and also deleted ALL the Hauppauge MVP registrys - LOVE AND BEHOLD REBOOT AND SageTV 4.1.6 was alive and fully working!

FYI: The .exe was running but I didn't give it a second thought because it was under the system area when I did talke a look at active running code...

Hope this helps

Spence

[mayamaniac]

MVP stopped working for me also after upgrading to SageTV 4.16.

I'm using 192.168.1.xxx DHCP IP Range, 255.255.255.0 subnet, and 192.168.1.1 as gateway, D-Link 614+ Router. Always used these settings and they worked in 4.15. I have not changed anything. I tried entering the MVP client info manually in sage.prop but still not working. Here's what I entered:

miniserver/automvp=true
miniserver/clients=MVP/00:0D:FE:00:4C:78/192.168.1.108
miniserver/gateway=192.168.1.1

I disabled my firewall just to rule out that as a problem but still can't figure this one out. I hate to downgrade to 4.15 because I want to see the MVP speed improvments in 4.16.

Any ideas?

[MrApollinax]

Originally Posted by walts81

Well 2 full days at this and still no working MVP. I can't run ethereal because the MVP is connected via a wireless bridge and according to ethereal's website a capture over 802.11 is very limited. I have no firewalls setup. My network is 192.168.1.x. The MVP gets an IP (I can see it on my router's clients table). Sage can see it because it shows up in the log but for some reason times out on the tftp. And like I said before... the MVP was working perfectly before upgrading to 4.1.6. This is driving me nuts!

- Josh

I don't know why i didn't see this post before, sorry. If you run ethereal on your SageTV computer you should still be able to catch all your server-side communication. That disclaimer is for captures over wireless NIC cards in the computer. The capture engine is a driver-level app and they haven't tested it thouroughly with the wireless chipsets as of yet.

[mayamaniac]

Very bizarre, I just downgraded to 4.15, and its still not working. What the heck did 4.16 do to the MVP? Now its not working at all, it just get stuck at the "Contacting MediaMVP BootServer" screen.

[sagetvkid]

Originally Posted by mayamaniac

Very bizarre, I just downgraded to 4.15, and its still not working. What the heck did 4.16 do to the MVP? Now its not working at all, it just get stuck at the "Contacting MediaMVP BootServer" screen.

...this was happening to me also...I usually leave my server on hibernation..I rebooted my router and my system..still no go...It was until I actually shut down my system for a few minutes and turned it back...bam!! The MVP made the connection...Just sharing what worked for me

[walts81]

Well, I had it working great with the official 4.1.3 release. I upgraded to 4.1.6 and the MVP was hosed. I did a complete re-format and re-install of XP and the MVP still won't work. It won't even work with the Hauppauge software. It just always hangs at the "Loading Application" screen. It's getting an IP. But for some reason won't finish the upload process. I think Sage killed it.

- Josh

[mayamaniac]

Mystery solved.

MVP is working now. Last night I went to troubleshoot the problem once more. I opened SageTV and went into system info, and I noticed that the server IP says 192.168.0.1. I know that is NOT the IP of the server computer. Then it dawned on me that I have a USB ethernet adapter connected to the server and using Windows ICS (internet connection sharing) which defaults to 192.168.0.1. Now why is SageTV picking this IP up instead of the IP on the main NIC? I have no idea, but I unlugged the USB ethernet adapter and rebooted SageTV and it uses the correct IP now, and the MVP loads and connects no problem, even in 4.16.

Divx/Xvid transcoding works pretty well. I noticed audio sync problem only once, and stop and play again fixes it. Still more room for improvements but this is a great start. I think I'll get another MVP now, if they are in stock (saw some posts about MVPs out of stock everywhere).