Boot problems in 0.97.7

[timelapse]

I have been using GBPVR succesfully since august last year with MVP. I have two NICs on my machine; one NIC (192.123.1.1) is dedicated to MVP. TFTPD32 serves as DHCP server and GBPVR is BOOTP server (supplying the dongle to MVP).

Since upgrading to 0.97.7 (from 0.96.x) I have a problem getting MVP to boot. I am using dongle.bin and here is what happens (reproduceable):

1) I start by resetting MVP (removing and re-inserting the powercord).
2) I turn the computer on.
3) MVP gets to the second/third bar on the boot screen.

After some time (say 15 minuttes):
4) I kill GBPVR.exe using task manager.
5) I reset MVP.

Then MVP can boot.

Using Ethereal I lean that MVP (192.123.1.2) tries to communicate on the wrong NIC/network:

"Broadcast ARP Who has 192.168.1.100? Tell 192.123.1.2"

MVP should communicate with 192.123.1.1 which is in the other end its network cable.

Attached is a snippet from GBPVR.exe.log (showing GBPVR is aware of both my NICs).

Anybody got any ideas :confused:

[martint123]

Interesting, Since the upgrade, I seem to have more than my usual MVP connection problems, once connected it seems fine, but needs a few reboots to get there. I'm using my router to serve DHCP.
I'm not saying my problem is the same as yours and I haven't spent enough time to diagnose anything but I have multiple IP addresses due to VMware. I can't do anything at the moment, but tomorrow will kill off their processes and see if it improves.

16/05/2006 18:08:13.421 INFO [8] MVP Streaming thread starting
16/05/2006 18:08:13.437 INFO [12] BOOTPWorkerThread() Hostname: wazock
16/05/2006 18:08:13.437 INFO [12] BOOTPWorkerThread IP Address 192.168.1.5
16/05/2006 18:08:13.437 INFO [12] BOOTPWorkerThread IP Address 192.168.70.1
16/05/2006 18:08:13.437 INFO [12] BOOTPWorkerThread IP Address 192.168.152.1
16/05/2006 18:08:13.687 INFO [10] ServiceLocatorThread() Hostname: wazock
16/05/2006 18:08:13.687 INFO [10] IP Address 192.168.1.5
16/05/2006 18:08:13.687 INFO [10] IP Address 192.168.70.1
16/05/2006 18:08:13.687 INFO [10] IP Address 192.168.152.1
16/05/2006 18:08:13.734 INFO [7] MVP Control thread Listening on port: 5906

[DeepBlueC]

check your config.xml file adn verify the mac address of your mvp is correct.

You also may want to try the new dongle ftp://ftp.hauppauge.com/Support/MediaMVP...24110b.zip

[martint123]

Attached a pair of gbpve.exe.log files. One from a "working 99% of the time" on v0.96.12 and one from a rarely working, but ok once connected, v0.97.7.

Next is to see if the multiple IP's has anything to do with it.

[onestar]

I don't know the software you are using, but why not just setup the dhcp server to tell the mvp to get dongle.bin from the tftp server you have, then let it boot after that.

I found in 0.96 the MVP was always stuck at bar 3. But with a independent DHCP/TFTP server serving the dongle, it boots no problem

[timelapse]

check your config.xml file adn verify the mac address of your mvp is correct.

The MAC address is correct.

You also may want to try the new dongle ftp://ftp.hauppauge.com/Support/MediaMVP...24110b.zip

I tried the suggested dongle, but the problem seems to be with the BOOTP process: No dongle is ever sent to the MVP.

[timelapse]

This software base router you're using must have a feature for forwarding ports.

No, not to my knowledge. I am using TFTPD32 to act as a DHCP server only on the NIC that is directly connected to the MVP.

I use a free program called ccports.exe doesn't have to be installed. Run MVP again and ccports gives you live report of what's happening on your network. There was a way to forward ports two of them to MVP and tell the router which port to what IP it should use. You might have to do the same.

I have been using af sniffer (Ethereal) for this. The two networks are not in any way connected (e.g. bridged) and the network connected to the MVP has no other hardware attached (no router).

Again I don't use this method anymore nor do I use your software that requires you to run two NICs and load balance them. Which Server OS are you running?

I am running Windows XP without doing anything fancy between the two NICs. One of them is simply connected directly to the MVP (network 192.123.1.0) and the other to my home lan (192.168.1.0). The two networks are totally indendent.

Funny thing is this setup worked great in the previous version of GBPVR. I suspect the problems are related to the changed boot process.

[timelapse]

I don't know the software you are using, but why not just setup the dhcp server to tell the mvp to get dongle.bin from the tftp server you have, then let it boot after that.

I found in 0.96 the MVP was always stuck at bar 3. But with a independent DHCP/TFTP server serving the dongle, it boots no problem

Well, I had this setup earlier, but decided to let GBPVR serve the dongle so I could easily switch between gbmvp.bin and dongle.bin from within config.

But for now I followed your suggestion and let TFTPD32 act as a BOOTP server on the NIC connected directly to MVP. And my problems are gone! For this reason I suspect that something in the changed boot process within GBPVR is causing my troubles.

Thank you all.

[onestar]

Well, I had this setup earlier, but decided to let GBPVR serve the dongle so I could easily switch between gbmvp.bin and dongle.bin from within config.

But for now I followed your suggestion and let TFTPD32 act as a BOOTP server on the NIC connected directly to MVP. And my problems are gone! For this reason I suspect that something in the changed boot process within GBPVR is causing my troubles.

Thank you all.

I've used the dhcp/tftp server from weird solutions, and in that I can by MAC address very simply assign a different profile - read different dongle - its how I got to see the new dongle in action