Placeshifter listening on wrong IP address

[trini0]

I'm trying to figure out why my new setup isn't working (HD100/Placeshifter clients unable to connect to the server).
I noticed this in the server settings. (see screenshot)

I have 2 NICs in the server.
Primary NIC: 192.168.20.11 <-- This serves the local network my clients are on
Secondary NIC: 192.168.200.11

When using the placeshifter client, if I specify the server to connect to, it connects without any problems. If I tell it to connect using the locator ID, it fails.

For the life of me, I cannot find a way for me to change this.
Anyone has any ideas where I can specify the IP address?
Thanks

[trini0]

Nevermind...

1. I swapped the IP addresses between the NICs.
2. I put the HD100 in the same network as the server, so it doesn't cross over the routers, and it connected successfully. (I'll have to investigate this)

Now I'm enjoying TV again...

[Taddeusz]

Change this setting in your server's properties file to the IP address of the network your HD100 and Placeshifter are supposed to be connecting from:

miniserver/forced_server_ip=

[trini0]

Thanks. I'll have to keep that in mind...

[GKusnick]

Originally Posted by trini0

When using the placeshifter client, if I specify the server to connect to, it connects without any problems. If I tell it to connect using the locator ID, it fails.

Sounds like your router is forwarding to the wrong IP then. Using the Locator ID is like connecting from the Internet; it translates to your WAN IP and comes in through your router instead of connecting directly via LAN.

[trini0]

Maybe. But if so why is the HD100 also affected.
What I think is going on, is that the routers aren't forwarding/relaying the udp auto-discover broadcast message from the placeshifter/HD100 to the server.
If you're familiar with it, its the same thing with DHCP broadcast messages. They cannot jump networks without help of a dhcp relay on routers.
I have to investigate if I can set this up in my routers.

[Taddeusz]

Do you have multiple network cards in your server?

[trini0]

Yes. Not sure what you're thinking, but I've had 2 NICs in the server for the longest time, and it worked fine.
The only that that has changed, is that the server is now in a different network than the clients

[Taddeusz]

Originally Posted by trini0

Yes. Not sure what you're thinking, but I've had 2 NICs in the server for the longest time, and it worked fine.
The only that that has changed, is that the server is now in a different network than the clients

Then you need to use that setting I suggested.

[GKusnick]

More than one net card, and more than one router? Maybe a diagram would be in order.

[trini0]

Ok. I'll try to have one put together later today.
Thanks

[trini0]

I've included a quick drawing of the network as it stands relating to my sagetv install.
In this configuration, neither the placeshifter client or the HD100 client can "discover" the sagetv server.
If I move these clients to the same network as the server (192.168.20.xxx), they work fine.
I believe my root issue is the udp broadcast from the clients not crossing over to the other network
Thanks

[GKusnick]

It seems to me you may have a couple of different issues going on here.

1. Server broadcasting autodiscovery packets on the wrong NIC. Do you actually have any evidence for this, e.g. Wireshark traces that show packets going out the wrong port? Or was this an inference from the fact that the clients aren't receiving them? If they're actually going out the wrong NIC, you should be able to correct that either with the property Taddeusz mentioned or by adjusting NIC priorities in Control Panel > Network Connections > Advanced > Advanced Settings.

2. Routers not forwarding autodiscovery packets to all subnets. I'm not sure what you can do about this. Maybe there's some setting to control this in your router config, but I seem to remember reading somewhere that autodiscovery is intentionally limited to the same subnet.

3. Locator ID not working. Again, this seems like a port forwarding issue on your router(s).

All of that said, I have to wonder why your home network is so complex, with four different subnets. What is all that complexity buying you? Wouldn't it be simpler to go with just one router located at your firewall/WAN connection?

[trini0]

Originally Posted by GKusnick

It seems to me you may have a couple of different issues going on here.

1. Server broadcasting autodiscovery packets on the wrong NIC. Do you actually have any evidence for this, e.g. Wireshark traces that show packets going out the wrong port? Or was this an inference from the fact that the clients aren't receiving them? If they're actually going out the wrong NIC, you should be able to correct that either with the property Taddeusz mentioned or by adjusting NIC priorities in Control Panel > Network Connections > Advanced > Advanced Settings.

I haven't sniffed the line as yet, so as of now I was speculating, using what I saw in the SageTV settings.
I'll also try what Taddeusz suggested.

Originally Posted by GKusnick

2. Routers not forwarding autodiscovery packets to all subnets. I'm not sure what you can do about this. Maybe there's some setting to control this in your router config, but I seem to remember reading somewhere that autodiscovery is intentionally limited to the same subnet.

I briefly looked over the documentation for the routers I'm using.
Not sure as yet, but I'm still investigating...

Originally Posted by GKusnick

3. Locator ID not working. Again, this seems like a port forwarding issue on your router(s).

All of that said, I have to wonder why your home network is so complex, with four different subnets. What is all that complexity buying you? Wouldn't it be simpler to go with just one router located at your firewall/WAN connection?

Actually my home network is more than what I described. I have another network for other servers.
My network, is more of a lab for me. Yes its more complex than the average "home" network, but it is what it is at the moment. I have to pay for the complexity.

But for now, my HD100 is working, so I'm ok for now, but I'll keep investigating to see if I can have the setup running the way I would like it.

[Taddeusz]

What subnet mask are you using? I assume one that makes both address ranges possible.

But, I believe the properties setting will fix your problem. The issue with having more than one network adapter in your SageTV server is that the extender/placeshifter server can only be accessible from a single network address. Using this setting allows you to specify which network address to use. Otherwise it automatically picks one, which may not be the one you want.