PDA

View Full Version : MVP stops at CONNECTING TO MEDIA BOOT SERVER


ckron
12-20-2005, 07:44 PM
i was very excited to try the native MVP support. i have been running an early version of SageTV2 and one of Matt's ealier MVP clients for some time now. i have been afraid to update to update anything because it was all working quite well. A few days ago I took the plunge and upgraded SageTV. I have yet to see my MVP connect to the server. It boots up saying it is contacting the DHCP server and the moves on to contacting the media boot server. this is when the MVP starts cycling between the two messages and never goes any further. The following is the list of what I have tried so far:

1. Clean install of SageTV
2. Connected MVP to same switch as SageTV server
3. Installed SageTV on another PC to act as server
4. Disable checksum offload
5. numerous reboots throughout the process
6. Tried latest client from Matt and it works OK. I had some trouble getting it to connect but it did and worked fine once it did.

stanger89
12-20-2005, 08:02 PM
From what little I know, if you never get to (or past) the "Loading Application" screen, then the MVP is unable to find the SageTV server.

The first thing to check, is that you have the extender server enabled in Detailed Setup (right under the normal Server option).

ke6guj
12-20-2005, 08:16 PM
It sounds like maybe your firewall is blocking the MVP from contacting the Sage server.

Temporarly disable your windows firewall, and if it connects then, you know what the problem is. In the FAQ, there is a list of ports that need to be open for the MVP to connect.

ckron
12-21-2005, 05:07 PM
From what little I know, if you never get to (or past) the "Loading Application" screen, then the MVP is unable to find the SageTV server.

The first thing to check, is that you have the extender server enabled in Detailed Setup (right under the normal Server option).


I double and triple checked it several times. It was definitely enabled.

ckron
12-21-2005, 05:07 PM
It sounds like maybe your firewall is blocking the MVP from contacting the Sage server.

Temporarly disable your windows firewall, and if it connects then, you know what the problem is. In the FAQ, there is a list of ports that need to be open for the MVP to connect.


I am running XP SP1 with no firewall enabled.

jquinlan
12-22-2005, 06:34 AM
If you have not, stop and restart the SAGE service, the MVP servers are integrated into it now.

_Demo_
12-22-2005, 09:16 AM
Do you have a dhcp server on your network?

_Demo_

ckron
12-22-2005, 10:09 AM
If you have not, stop and restart the SAGE service, the MVP servers are integrated into it now.


I have stopped and started the service several times and rebooted the PC several times with no change in behaviour.

ckron
12-22-2005, 10:12 AM
Do you have a dhcp server on your network?

_Demo_

Yes I do and I am sure the MVP is getting an address. I have been running Matt's client for many months with little problem.

_Demo_
12-22-2005, 11:33 AM
Could you see which version it says you have under the mvp?

Thanks

_Demo_

ckron
12-22-2005, 03:33 PM
Could you see which version it says you have under the mvp?

Thanks

_Demo_

Rev D3A

ckron
12-23-2005, 07:02 AM
Here is what I got in my log:


Fri 12/23 8:23:03.804 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:23:16.582 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:104989221 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:23:16.583 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:23:25.603 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:104989221 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:23:25.604 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:23:33.808 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:23:35.584 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:617999553 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:23:35.584 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:23:44.604 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:617999553 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:23:44.605 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:23:54.586 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1131012511 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:23:54.587 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:03.810 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:24:05.375 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1131012511 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:05.376 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:13.211 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1131012511 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:13.212 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:26.591 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1995037509 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:26.592 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:33.813 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:24:35.612 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1995037509 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:35.613 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:45.594 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1786912291 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:45.595 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:54.615 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1786912291 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:54.616 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:03.816 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:25:04.597 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1273898630 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:04.598 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:13.618 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1273898630 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:13.619 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:23.600 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-760883644 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:23.600 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:32.620 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-760883644 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:32.621 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:33.819 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:25:42.602 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-247869990 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:42.603 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:44.084 Ministry is waiting for 180 sec
Fri 12/23 8:25:51.623 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-247869990 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:51.624 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:03.822 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:26:04.606 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:346147053 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:04.606 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:13.626 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:346147053 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:13.627 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:23.608 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:859162599 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:23.609 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:32.629 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:859162599 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:32.630 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:33.824 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:26:42.611 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1372175686 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:42.612 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:51.632 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1372175686 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:51.633 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:27:01.614 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1885192048 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:27:01.615 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:27:03.827 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:27:10.635 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1885192048 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:27:10.636 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:27:20.617 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1896762503 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:27:20.617 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:27:29.638 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1896762503 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:27:29.638 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:27:33.830 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:27:44.620 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1248744005 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:27:44.621 Couldn't match client 00:50:c2:24:5f:ff


My MVP stops at contacting media boot server

kpsmith
12-23-2005, 07:38 AM
For what its worth I'm having the same issue. I'll be sure to post if I can figure out why its happening.

ckron
12-23-2005, 08:11 AM
For what its worth I'm having the same issue. I'll be sure to post if I can figure out why its happening.


It is always nice to know you are not alone. Sorry you are having this issue. Have you turned on Debugger logging so you can see if you get the same error I do?


I noticed you live in Albany, NY. My brother lives out your way and I live in Rochester.

_Demo_
12-23-2005, 09:28 AM
It seems your device MAC address isn't a mvp one.
Could you try to add
miniserver/gateway=ip of your gateway
miniserver/clients=MVP/00:50:C2:24:5F:FF/ip of mvp

in your Sage.properties file. Note that you must be running the 4.1.4 beta for that to work.

_Demo_

ckron
12-23-2005, 09:50 AM
What is that supposed to do?

ckron
12-23-2005, 10:19 AM
It seems your device MAC address isn't a mvp one.
Could you try to add
miniserver/gateway=ip of your gateway
miniserver/clients=MVP/00:50:C2:24:5F:FF/ip of mvp

in your Sage.properties file. Note that you must be running the 4.1.4 beta for that to work.

_Demo_

The MVP now gets to Starting Application and hangs there. The log follows:




ri 12/23 12:10:21.443 Seeker awoken
Fri 12/23 12:10:21.444 MARK 1 currRecord=null enc=Hauppauge WinTV PVR PCI II Capture #2 clients=[] ir=false
Fri 12/23 12:10:21.452 Seeker in AUTOMATIC mode nextRecord=A[42542,41996,"Cyberchase",12005@1223.17:00,30] nextTTA=17378556
Fri 12/23 12:10:21.453 newRecord=null
Fri 12/23 12:10:21.453 NOTHING TO RECORD FOR NOW...
Fri 12/23 12:10:21.455 MARK 1 currRecord=null enc=Hauppauge WinTV PVR PCI II Capture clients=[] ir=false
Fri 12/23 12:10:21.456 Seeker in AUTOMATIC mode nextRecord=null nextTTA=9223372036854775807
Fri 12/23 12:10:21.461 newRecord=null
Fri 12/23 12:10:21.462 NOTHING TO RECORD FOR NOW...
Fri 12/23 12:10:21.777 Seeker clearing unwanted and partial files...
Fri 12/23 12:10:21.779 Seeker waiting for 284 mins.
Fri 12/23 12:10:37.588 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 12:11:02.308 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:106070732 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 12:11:02.309 Matched request to client 0
Fri 12/23 12:11:02.310 servername 192.168.0.124
Fri 12/23 12:11:02.442 Reading mvp.bin in mode octet
Fri 12/23 12:11:02.443 Opening file
Fri 12/23 12:11:07.592 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 12:11:11.612 At last block
Fri 12/23 12:11:37.596 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 12:12:07.598 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 12:12:37.601 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 12:13:07.604 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 12:13:12.790 Ministry is waiting for 180 sec
Fri 12/23 12:13:37.607 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 12:14:07.610 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 12:14:37.613 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 12:15:07.615 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 12:15:21.808 Seeker awoken
Fri 12/23 12:15:21.813 MARK 1 currRecord=null enc=Hauppauge WinTV PVR PCI II Capture #2 clients=[] ir=false
Fri 12/23 12:15:21.815 Seeker in AUTOMATIC mode nextRecord=A[42542,41996,"Cyberchase",12005@1223.17:00,30] nextTTA=17078187
Fri 12/23 12:15:21.816 newRecord=null
Fri 12/23 12:15:21.817 NOTHING TO RECORD FOR NOW...
Fri 12/23 12:15:21.817 MARK 1 currRecord=null enc=Hauppauge WinTV PVR PCI II Capture clients=[] ir=false

_Demo_
12-23-2005, 11:27 AM
You should try to find out why your mvp mac address is modified, that will probably resolve the other problem as well.

_Demo_

ckron
12-23-2005, 11:55 AM
You should try to find out why your mvp mac address is modified, that will probably resolve the other problem as well.

_Demo_


why do you believe it is modified?

kpsmith
12-23-2005, 11:59 AM
Turns out my issue was related to the firewall settings. So I think I'm set... Sorry I couldn't help a fellow NY'er out. Sounds like you may be getting closer at least.

_Demo_
12-23-2005, 01:35 PM
MVP mac address should start with 00:0D:FE which is assigned to Hauppauge.

_Demo_

ckron
12-23-2005, 03:15 PM
MVP mac address should start with 00:0D:FE which is assigned to Hauppauge.

_Demo_

00:50:C2:24:5F:FF matches up with the MAC address of the server:
00:50:2c:0a:30:8e

The server only has one NIC in it. The only other thing under network connections is this goofy internet gateway thing I have never seen before. I believe the NIC is some sort of VIA chip.

gplasky
12-23-2005, 05:19 PM
Double check the underside of your MVP. There should be a sticker on it with the MAC address of your MVP. See how that compares.

Gerry

ckron
12-23-2005, 05:49 PM
I did already. It is definitely different

mayamaniac
12-23-2005, 06:00 PM
my D-Link router shows the MAC addresses and IP assigned to them for every device connected to the router. So check your router page and find out the IP assigned to whatever MAC address that's correct on the MVP, then turn the MVP on and see if your server can ping it (command prompt, type: ping [MVP IP address]). If that works, then maybe insert that IP into the mvp properties, wherever that is, somone posted earlier.

And lastly, dumb questions, but you uninstalled the hauppauge software right?

ckron
12-23-2005, 06:15 PM
my D-Link router shows the MAC addresses and IP assigned to them for every device connected to the router. So check your router page and find out the IP assigned to whatever MAC address that's correct on the MVP, then turn the MVP on and see if your server can ping it (command prompt, type: ping [MVP IP address]). If that works, then maybe insert that IP into the mvp properties, wherever that is, somone posted earlier.

And lastly, dumb questions, but you uninstalled the hauppauge software right?

I never installed that lousy Hauppauge software.

The funny thing is, my router is not showing the MAC from the MVP. Keep in mind that my router is not my DHCP server. One of my other servers is my DHCP server.