![]() |
|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
![]() |
|
Thread Tools | Search this Thread | Display Modes |
#41
|
||||
|
||||
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: Quote:
![]() ![]() ![]() 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.
__________________
Mayamaniac - SageTV 7.1.9 Server. Win7 32bit in VMWare Fusion. HDHR (FiOS Coax). HDHR Prime 3 Tuners (FiOS Cable Card). Gemstone theme. - SageTV HD300 - HDMI 1080p Samsung 75" LED. Last edited by mayamaniac; 08-17-2006 at 03:53 AM. |
#42
|
||||
|
||||
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.
__________________
Server: MS Win7 SP1; FX8350 (H2O cooled); 8GB RAM; Hauppauge HVR-7164 (OTA); HVR-885 (OTA); SageTV 9.1.5.x; 12+TB Sage Storage Clients: HD300 x2; HD200 x2; Placeshifter Service: EPB Fiber (1Gb); OTA (we "cut the cord"); Netflix, Hulu, etc. |
#43
|
||||
|
||||
Mayamaniac. Try setting the IP of the looopback to 127.0.0.1
|
#44
|
|||
|
|||
Quote:
BobP. |
#45
|
||||
|
||||
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.
__________________
Server: MS Win7 SP1; FX8350 (H2O cooled); 8GB RAM; Hauppauge HVR-7164 (OTA); HVR-885 (OTA); SageTV 9.1.5.x; 12+TB Sage Storage Clients: HD300 x2; HD200 x2; Placeshifter Service: EPB Fiber (1Gb); OTA (we "cut the cord"); Netflix, Hulu, etc. |
#46
|
|||
|
|||
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. |
#47
|
||||
|
||||
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=
__________________
Mayamaniac - SageTV 7.1.9 Server. Win7 32bit in VMWare Fusion. HDHR (FiOS Coax). HDHR Prime 3 Tuners (FiOS Cable Card). Gemstone theme. - SageTV HD300 - HDMI 1080p Samsung 75" LED. Last edited by mayamaniac; 10-16-2006 at 03:38 AM. |
#48
|
|||
|
|||
Quote:
|
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|