Can't get past the "Contacting Servers" message

[LehighBri]

I recently bought and installed a MediaMVP but I am unable to get past the Contacting Servers message. The steps I performed to install were (note that I installed on my 10/100 wired network using a Linksys WRT54G router):

1. Registered the Media Extender license key on the SageTV 6.1.9 server
2. Enabled the Media extender and placeshifter server in the Detailed Setup
3. Restarted server PC
4. Turned off my firewall to completely rule it out
5. Plugged in the power to the MediaMVP and turned it on
6. The MediaMVP found my server and I click OK to choose it
7. The "Contacting Servers" message appears on the MediaMVP and stays on for at least 15 minutes before I give up and turn it off.

Any ideas on how to get this working so that I can get to the Sage interface on my MediaMVP? I ran a quick debug during the steps above and the sagetv_0.txt debug file shows the following when I search for 'mvp':

Sun 6/10 21:46:05.021 Seeker has finished the library import scan.
Sun 6/10 21:46:08.016 Ministry is starting
Sun 6/10 21:46:08.017 Ministry is waiting for 180 sec
Sun 6/10 21:46:36.666 Received mvp packet
Sun 6/10 21:46:36.878 Sending mvp reply
Sun 6/10 21:46:45.548 Received mvp packet
Sun 6/10 21:46:45.753 Sending mvp reply
Sun 6/10 21:47:12.491 Received mvp packet
Sun 6/10 21:47:12.705 Sending mvp reply
Sun 6/10 21:47:18.973 Received mvp packet
Sun 6/10 21:47:19.190 Sending mvp reply

[mdnttoker]

Try running a Wireshark packet capture and see what IP addresses are being assigned and used...

[LehighBri]

Originally Posted by mdnttoker

Try running a Wireshark packet capture and see what IP addresses are being assigned and used...

My server has always had a static address of 192.168.1.111 and my hauppauge is pulling dynamic IP from my DHCP on my linksys router. The latest IP for the MediaMVP I noticed it is 192.168.1.103. Should I be looking for anything in particular from the Wireshark output?

If I search for 192.168.1.103 in Wireshark, I noticed the following:

Source: 192.168.1.103
-WCCP protocol: Unknown WCCP message (1)[Malformed packet]

Source: Hauppaug_08:d2:dc
-ARP protocol: 192.168.1.103 is at 00:0d:fe:08:d2:dc
-ARP protocol: who has 192.168.1.1? Tell 192.168.1.103

[mdnttoker]

Well, you should see the MVP request an IP, request the boot image from the server via tftp, see a ton of udp traffic while the image is loaded ,and then at some point it should transition to tcp/ip traffic for regular display.

Is all this happening? Are the IP's correct in each transaction (source / destination)?

[LehighBri]

Originally Posted by mdnttoker

Well, you should see the MVP request an IP, request the boot image from the server via tftp, see a ton of udp traffic while the image is loaded ,and then at some point it should transition to tcp/ip traffic for regular display.

Is all this happening? Are the IP's correct in each transaction (source / destination)?

The IPs look to be correct, but per the SageTV log file, I do not see any tftp activity. Also, I tried to telnet to the IP of the MediaMVP but was not able to do so. Is there a reason why I cannot telnet to it or a reason why the tftp is not initiating? Do I have to upgrade the firmware in the MediaMVP somehow?

[tmiranda]

Do you have the wireless MVP? Assuming you do try this:
- Unplug the MVP and wait about 30 seconds.
- Plug the unit back in and press the "OK" button when prompted to enter setup.
- Go to the network setting and see what is in there. You should select wired as the preferred network.
- If you have wireless encryption enabled, select the wireless connection, turn off the encryption and then switch back to the wired connection. Don't ask me why wireless encryption makes any difference when you are running in wired mode but somehow it does.....

I've spent hours fiddling with the wireless MVP and sometimes just changing a setting and saving the config will make a difference. Wierd.

Also, what is the topology of your network?

[LehighBri]

Originally Posted by tmiranda

Do you have the wireless MVP? Assuming you do try this:
- Unplug the MVP and wait about 30 seconds.
- Plug the unit back in and press the "OK" button when prompted to enter setup.
- Go to the network setting and see what is in there. You should select wired as the preferred network.
- If you have wireless encryption enabled, select the wireless connection, turn off the encryption and then switch back to the wired connection. Don't ask me why wireless encryption makes any difference when you are running in wired mode but somehow it does.....

I have the wired MediaMVP. Nonetheless, I tried these steps but still no luck.

Originally Posted by tmiranda

Also, what is the topology of your network?

I have a Linksys WRT54G router connected via 100mb ethernet to my server PC (192.168.1.111 static IP) and also to my MediaMVP (192.168.1.121 static IP). I am able to ping my MediaMVP and get a response, but I cannot telnet.

Ping results:
Pinging 192.168.1.121 with 32 bytes of data:

Reply from 192.168.1.121: bytes=32 time=19ms TTL=64
Reply from 192.168.1.121: bytes=32 time=1ms TTL=64
Reply from 192.168.1.121: bytes=32 time=19ms TTL=64
Reply from 192.168.1.121: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 19ms, Average = 10ms

Telnet results:
Connecting To 192.168.1.121...Could not open connection to the host, on port 23: Connect failed

[LehighBri]

I finally fixed it! It turns out the MediaMVP was trying to connect to a 2nd network card on my server I solely use for my HDHomeRun card. I noticed the post below which did the trick:

http://forums.freytechnologies.com/f...age.properties

In a nutshell, I updated the sage.properties file:
miniserver/forced_server_ip=192.168.1.111 (IP of server's network card which connects to my router)

[mdnttoker]

Originally Posted by LehighBri

I finally fixed it! It turns out the MediaMVP was trying to connect to a 2nd network card on my server I solely use for my HDHomeRun card. I noticed the post below which did the trick:

http://forums.freytechnologies.com/f...age.properties

In a nutshell, I updated the sage.properties file:
miniserver/forced_server_ip=192.168.1.111 (IP of server's network card which connects to my router)

Yeah, that's where I was going with the network cap's.

If this was the problem, you should have seen the MVP trying to connect to the wrong NIC IP in the Wireshark log's.

Glad you got it fixed!

-Dan

[bbig119]

Originally Posted by LehighBri

I finally fixed it! It turns out the MediaMVP was trying to connect to a 2nd network card on my server I solely use for my HDHomeRun card. I noticed the post below which did the trick:

http://forums.freytechnologies.com/f...age.properties

In a nutshell, I updated the sage.properties file:
miniserver/forced_server_ip=192.168.1.111 (IP of server's network card which connects to my router)

Son of a bi#$%ch, I've been fuddling around with this problem for ages, but the symptoms have presented themselves more strangely. I had an old linksys and like you, a HDHomerun connected to a second NIC on the sage server. Sometimes I could get my MVP to connect, but it was like magic. I would go back and forth starting/stopping the hauppauge and sage servers and eventually some combination allowed it to work-- until I lost power or mucked with the connections on the router. I recently upgraded to a buffalo whr-g125 and haven't been able to produce the magic needed to get my mvp working. I read and reread the instructions in the sage manual thinking I was missing some incredibly obvious setting since they make it sound effortless to set the thing up. There seems to be very little chatter about this problem in the forums-- fortunately and luckily I found this post and it appears to have worked like a charm. Either that or the magic just happened to work when I put in that miniserver setting in the properties file.

Thanks!!!