Placeshifter Test Cannot Find Router?

[PeteCress]

The locator server connected to the IP address registered for this Locator ID, but could not access the Placeshifter server's port.

Make sure the port is not blocked on your router/firewall and is forwarded to your SageTV server computer.

In the configuration wiz, it says

Configure port forwarding to your local SageTV server.  Server TCP Port: 31099, IP Address: 5.169.189.11
Router: Manually forward TCP Port 31099 to IP 5.169.189.11

Does anybody know what is with the 5.169.189.11?

I suspect that's a player in my problem.

Tried forwarding to that address, no luck. Tried frowarding from the address to the SageTV PC's address, no luck.

FWIW, my router's running Tomato. I've had an HD200 working remotely in the past, but it was definately before going to v7. I can't recall if I was running Tomato at the time.

??

[PeteCress]

Originally Posted by PeteCress

[CODE]Does anybody know what is with 5.169.189.11? I suspect that's a player in my problem.

This is just to bump the thread. I'm getting desperate....

A fuller rendition of SageTV's ref to 5.169.189.11 is:
In order for a Placeshifter Client to connect to this SageTV Server via the internet, you will need to configure your router/firewall to open TCP port 31099 and forward it to this computer's local IP address of '5.169.189.11'. Screen snap: http://tinyurl.com/4y3flye

But my home LAN is 10.0.0-based and my SageTV box's local IP address is 10.0.0.10.

I've tried setting the destination to both 10.0.0.10 as in http://tinyurl.com/3t9hsdo and 5.169.189.11 as in http://tinyurl.com/3g5o4qd.

But no luck either way.

Found an MS knowledgebase document (http://support.microsoft.com/kb/315236) whose gist seems tb that port forwarding won't happen under XP unless the registry says it's OK.

I don't remember having to do this before, when the HD200's were working remotely. OTOH, the sys has been rebuilt on a new box since then (the old one having been WSH....)

Found my registry apparently didn't... did the deed to make is supposedly OK, but still no change.

Tried turning off Windows' Firewall with each of the address options, but no change.

[tmiranda]

Pete,

I can't see your screen shots (blocked for me) but in general you should check the following:

- Turn off the firewall on the PC running the Sage. No need to mess with any registry settings at all. I think this is true only if you are using the Windows machine as the router, which you are not.

- Make sure in the Sage settings you have enabled the placeshifter support and have defined a user.

- Go into your router config and set ports 31099 and 31100 (I think you need both, but I'm going from memory) to be forwarded to the IP address of your Sage server. It doesn't matter if you're using a 192.168. or a 10. network.

- You probably want to make sure your router is setup to give your Sage server a static IP address so things don't break when the server gets a new IP.

[PeteCress]

Originally Posted by PeteCress

A fuller rendition of SageTV's ref to 5.169.189.11 is:
In order for a Placeshifter Client to connect to this SageTV Server via the internet, you will need to configure your router/firewall to open TCP port 31099 and forward it to this computer's local IP address of '5.169.189.11'. Screen snap: http://tinyurl.com/4y3flye

But my home LAN is 10.0.0-based and my SageTV box's local IP address is 10.0.0.10.

I found the origin of 5.169.189.11. It was something called "Leaf Networks Adapter". Found it in the myComputer | Manage | Device List, disabled the device, and now SageTV is picking up the correct IP addr of itself (10.0.0.10).

Also, just for CYA, I disabled "Ethernet adapter VirtualBox Host-Only Network", so there should not be anything left to confuse SageTV.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

c:\>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 10.0.0.10
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.0.0.1

Ethernet adapter Local Area Connection 2:

        Media State . . . . . . . . . . . : Media disconnected

Ethernet adapter Leaf Networks Adapter:
        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 5.169.189.11
        Subnet Mask . . . . . . . . . . . : 255.0.0.0
        Default Gateway . . . . . . . . . :

Ethernet adapter VirtualBox Host-Only Network:
        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 192.168.56.1
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :

c:\>

Where Leaf Networks came from is another issue which I have not resolved.

But, even with the offending device disabled, results are the same - No-Go.

[GKusnick]

Originally Posted by tmiranda

- Go into your router config and set ports 31099 and 31100 (I think you need both, but I'm going from memory) to be forwarded to the IP address of your Sage server.

Mine works with just 31099. But I do have it set to forward both TCP and UDP traffic on that port.

[PeteCress]

Originally Posted by GKusnick

Mine works with just 31099. But I do have it set to forward both TCP and UDP traffic on that port.

I changed from TCP to "Both", but no change.

My gut says it's something really basic/stupid that I am doing/not doing.... something so obvious that it's not even considered.

OTOH, I really did have it working sometime last year....

[tmiranda]

Originally Posted by PeteCress

I changed from TCP to "Both", but no change.

My gut says it's something really basic/stupid that I am doing/not doing.... something so obvious that it's not even considered.

OTOH, I really did have it working sometime last year....

If the firewall is off on your server and the router is setup correctly, it is possible that your ISP is blocking those ports.

[PeteCress]

Originally Posted by tmiranda

If the firewall is off on your server and the router is setup correctly, it is possible that your ISP is blocking those ports.

I was thinking that from early on, but didn't want to go there bc it seemed to violate the idea of the simplest explanation being the most likely....

I have been testing an IP camera at http://paoli.viewnetcam.com:50001/ (which resolves to my router's IP:50001, used by the camera itself) and at http://petecress.dyndns.org:8080/ (which also resolves to my router's IP, only port 8080 used by a middleman app for streaming).

Both links work from a remote site - so it would seem that those ports, at least, are not being blocked by Verizon. I've tried a couple of other ports for Sage, but nothing outside of the 31000-32000 range.

Can't think of anything else to do, so maybe I'll set the camera middleman's port to 31099 to see what happens.

[PeteCress]

Originally Posted by PeteCress

One thing I notice in the error dialog, however, is "The locator server connected to the IP address registered...."
Seems like the next logical step is to somehow determine/confirm what IP address is "registered" for my Locator ID. If that were wrong, it would explain everything quite neatly.

BINGO!!!!! Bing-F-ing-GO!!!!!!!.

After reading the thread at http://forums.sagetv.com/forums/showthread.php?t=52464, I

• Stopped the SageTV service
• Edited SageTV.Properties, deleting all 4 of the "locator/" lines, viz:

  locator/enable_registration=true
  locator/id=D179-21E3-1D25-CCB4
  locator/system_id_base=-780590621
  locator/update_interval=1800000

• Re-started SageTV service, and stepped through PlaceShifter setup
• Observed that all was well....and that the props file now contained

  locator/enable_registration=true
  locator/id=xxxx-xxxx-xxxx-xxxx
  locator/system_id_base=1436138477
  locator/update_interval=1800000

My uninformed guess: somewhere, somebody has a table that relates LocatorID to IP Address and the entry in that table for Yours Truly got wacked.

Whew!!!!!

[tmiranda]

Glad you got it working. Your locator ID changed, that might have been the problem.

If I were you I'd edit the post and remove the locator ID, unless you want to share your server with a few friends.

Tom

[PeteCress]

Originally Posted by tmiranda

If I were you I'd edit the post and remove the locator ID, unless you want to share your server with a few friends.

Good catch. Thanks!

[PeteCress]

Originally Posted by PeteCress

One additional puzzler I noticed during the abovementioned exercise: Sage's "Configure Placeshifter Internet Connection" screen says to forward to IP 5.174.98.8. No mention of the SageTV server PC's actual local IP addr of 10.0.0.10.

Got it.

The mysterious "5.174.98.8" was the IP addr of the (virtual?) "Leaf Networks Adapter" set up many moons ago by my NAS box's remote connection feature ("ReadyNAS").

Somehow SageTV had latched on to it as the Good-Right-And-Holy path to the Sage Server.

Per another thread on the subject, I opened Control Panel | Network Connections | Advanced | Advanced Settings | Connections and pushed the Leaf Networks Adapter to the bottom of the list, leaving "Local Area Connection" (which is my real NIC) at the top of the list.

Problem went away just like magic...

With the benefit of 20-20 hindsight, it seems clear that I let myself get led astray by the unrelated Ping issue.... and I should have latched on to the goofy address right away.