Switching to UNC Paths

[mayamaniac]

I'm revisitng this thread again due to another problem.

Today, after a server reboot, the MVP couldn't connect again. I went and checked the connection order, and the Loopback adapter was last on the list, which is where its suppose to be. So I went to SageTV's system information screen, and it shows the correct IP, and not the Loopback IP. So I had no clue what the problem is this time. So I enabled SageTV debug log, and here lies the problem:

Thu 8/17 2:28:32.576 SageTVServer was instantiated.
Thu 8/17 2:28:32.577 SageTVMiniDiscoveryServer was instantiated.
Thu 8/17 2:28:32.577 SageTVDiscoveryServer was instantiated.
Thu 8/17 2:28:32.578 addr: /127.0.0.1
Thu 8/17 2:28:32.578 EPG needs an update in 0 minutes
Thu 8/17 2:28:32.580 addr: /192.168.1.101
Thu 8/17 2:28:32.580 Miniserver running on 192.168.99.100

First of all, the server LAN IP is 192.168.1.101, and the loopback fake IP is 192.168.99.100. Now why is the SageTV miniserver running on the loopback fake IP? It doesn't make sense when loopback is dead last on the connection order.

Any ideas... anyone? For now, I'm disabling the loopback adapter so that my MVP can connect again.

I might just do what BobPhoenix suggested earlier on this thread and get a UPS for the router and not have to worry about it.

[hemicuda]

Shortly after I got my first UPS I found it prudent to have all the LAN/WAN hardware plugged into it as well. At least that way the network will be up as long as the server is on. YMMV.

[ToxMox]

Mayamaniac. Try setting the IP of the looopback to 127.0.0.1

[BobPhoenix]

Originally Posted by ToxMox

Mayamaniac. Try setting the IP of the looopback to 127.0.0.1

WinXP wouldn't let me. It complained that 127.0.0.1 was restricted to the loop back adapter - which I thought was strange since that is what I was adjusting. So I disabled the loop back adapter again. This problem (Miniclient on wrong adapter) is a SageTV MVP client problem I think. Why would it insist on using that one even when the Loop Back adapter is put last in the list.

BobP.

[hemicuda]

XP is a funny critter when it comes to 127.0.0.1. I use port forwarding via SSH when I'm away from home and had to use 127.0.0.2:[port] for things to work out right. XP pitched a fit when i tried to use 127.0.0.1. No idea if the loopback everyone is discussing will work w/ that since I know nothing about it.

[stevech]

Isn't 127.xxx.xxx.xxx an IETF coordinated and reserved address for local loopback?

Meaning no service should use that unless the connection WANTS to do a loopback on the same PC or device.

[mayamaniac]

For those using the loopback adapter solution, I just wanna update this thread that in SageTV v6 there's a fix for the problem where it assigns the loopback IP to the miniserver instead of the correct server IP. As a result, the MVP extender would fail to connect. You can change the property setting to force it to use the correct IP. Just edit these two lines in the sage.properties file, add correct IP and gateway of your server settings:

miniserver/forced_server_ip=
miniserver/gateway=

[BobPhoenix]

Originally Posted by mayamaniac

For those using the loopback adapter solution, I just wanna update this thread that in SageTV v6 there's a fix for the problem where it assigns the loopback IP to the miniserver instead of the correct server IP. As a result, the MVP extender would fail to connect. You can change the property setting to force it to use the correct IP. Just edit these two lines in the sage.properties file, add correct IP and gateway of your server settings:

miniserver/forced_server_ip=
miniserver/gateway=

Thank you. Will try that tonight.