Using Android Miniclient as Placeshifter

[NetworkGuy]

I am just wondering if anyone has tried using the Miniclient remotely instead of Placeshifter.

[KarylFStein]

Originally Posted by NetworkGuy

I am just wondering if anyone has tried using the Miniclient remotely instead of Placeshifter.

Yes, I do that quite a bit.

[NetworkGuy]

Originally Posted by KarylFStein

Yes, I do that quite a bit.

How does it find the SageTV server if it is not on your local LAN?

[KarylFStein]

Originally Posted by NetworkGuy

How does it find the SageTV server if it is not on your local LAN?

I use a dynamic DNS service, (e.g. duckdns.org is a free one). So I just enter my domain name in as the connection.

You may also use the built-in locator service. When logged in to SageTV go to Setup > Detailed Setup > Server > Placeshifter Locator ID. You may then set up your connection with that ID.

[wayner]

Or you can just enter your WAN IP address if it is pretty static, which mine is.

[NetworkGuy]

Fuzzy pointed me to a thread about getting your IP address using the SageTV Locator service.
https://forums.sagetv.com/forums/showthread.php?t=48158

[Fuzzy]

You shouldn't need to use the 'get ip address from locator service', as you should be able to use the locator id directly in the miniclient, and it will do the look up for you.

[NetworkGuy]

Originally Posted by Fuzzy

You shouldn't need to use the 'get ip address from locator service', as you should be able to use the locator id directly in the miniclient, and it will do the look up for you.

Did not know that. Thanks!

[btrcp2000]

Trying to do this as well. The only way I can get it to work is if I place the whole server in the DMZ within the router. Same goes for webserver. Plex and Playon work fine from outside.

Ports 31099, 31100, 8018, and 7818 (last 3 are desperate reaches from old posts around here) are forwarded in the router directly to the server's static IP.

Any ideas?

[videolog]

I have been trying to do this on a Mi Box and I keep getting
"Unable to connect
Host is Unresolved: "then my locator id

It's like it does not even try to connect. I am able to connect with my phone, from this same location.

Any ideas?

[Pelicanjoe]

The Locator ID has been unreliable for me. It was working until it wasn't working. Luckily, my router has a Virtual DNS built in. I used that DNS and no problems! And, you don't have to worry about keying in the long Locator ID code!

[wayner]

Originally Posted by videolog

Any ideas?

Have you tried your server's external IP address directly?

[videolog]

I haven't tried the external IP address directly. I have a dynamic address I use that works for everything I have on the server. The strange part is this all works on the phone. We are on vacation and I thought I would give the Mi Box a try. The second I try to connect it immediately comes up with the error. It doesn't even try to connect. I think it must be some setting on the Mi Box.

I will go ahead and try the ip address to see what happens.

[videolog]

Okay, the external IP works, but the dyn dns does not. Very strange.

Thanks for the idea of using that ip.

[wnjj]

Finally getting around to trying this out myself. I'm not having any luck.

My setup is the following:

1. Windows 7 server.
2. ISP is wireless via a Nanobridge M5 antenna. It's configured in router mode.
3. Additional router in my house is an old TrendNet tw100-s4w1ca.
4. The TrendNet WAN IP is set to static IP in the M5's LAN domain and that IP is also listed in the M5's DMZ.
5. I added port 31099 and my server PC's local IP to the TrendNet's "Virtual Server" settings (i.e. port forwarding). The PC's IP is in the TrendNet's LAN domain.

I have the miniclient on my Galaxy S7 phone and connect just fine on the LAN using the local server IP. So think this means port 31099 (default) is listening fine on the server. 'Netstat -a' shows it listening too.

If I use the phone from an outside network using my outside IP address it times out trying to connect. I've tried using both 4G at home or wifi off site for the phone.

One of those port scan websites shows 31099 as 'not responding' on my external IP so I assume that means trying to connect on that port isn't making it to the server through one of the routers.

My (limited) understanding of DMZ is that TCP connections addressed to my external IP address are automatically forwarded to the DMZ IP listed. That is my TrendNet router WAN IP. After that, port forwarding should pass it on again to my server on the TrendNet's LAN.

Any idea where to look next? Maybe I should try some simple FTP or web server software to see if I can "host" one of those through the routers? The TrendNet has nothing useful in terms of logging of incoming packets, forwarded or otherwise.

Worst case I can buy a newer router if that's the issue.

[KarylFStein]

Why do you have the Trendnet? Are the two LANs different subnets? On the LAN if you put in the Trendnet WAN does it connect?

[wnjj]

Originally Posted by KarylFStein

Why do you have the Trendnet? Are the two LANs different subnets? On the LAN if you put in the Trendnet WAN does it connect?

Because originally the M5 was in bridge mode so I needed my own router. Plus I need the physical ports. When my ISP changed to router mode, putting the TrendNet in the DMZ should have been equivalent. Most customers on my ISP don't ever log in to their antenna, though I do.

The M5 LAN is 10.10.1.x and the TrendNet is 192.168.0.x so there's no confusion.

I haven't tried the TrendNet WAN. That's a good suggestion. I can get to the M5 on the 10.10.1.x net (HTTP) so I should be able to direct the MiniClient to that domain.

I can also try taking the TrendNet out of the DMZ and configure it as a simple hub, leaving the M5 to do all of the routing and DHCP. The downside is I would have to port forward in the M5 and my ISP prefers a "generic" configuration.

[wnjj]

Connecting to the TrendNet WAN from my LAN works so its port forwarding seems to be OK. I'm guessing my ISP may be blocking ports.