Two Ethernet Adapters?

[PeteCress]

Trying to set up Client for remote access, but am stuck.

My WHS/SageTV box has two Ethernet adapters:

• One on the mobo, which is connected to the Internet
• Another as a card, which is connected to an old router that has my two HD HomeRuns plugged in to it.

Problem seems to be that Sage's setup recognizes the card instead of the mobo adapter.

I pulled the NIC, rebooted, and now Setup seems tb recoginzing the mobo adapter.

But Test Placeshifter Connection is throwing:

"...The locator server connected to the IP address registered for this Locator ID, but could not access the Placeshifter server's port. Make sure theis port is not blocked on your router/firewall and it is forwarded to your SageTV server computer."

Am I correct in assuming that "the Placeshifter server's port" is 31099?

BTW, when I re-install the NIC, Setup goes back to thinking that's the adapter to use.

Should I cave in and re-config my server so that Internet comes in on that NIC and my HD Homeruns/local router are connected to the mobo's adapter?

Anybody been here?

[GKusnick]

You can change NIC priorities via Control Panel > Network Connections > Advanced > Advanced Settings. Try putting the one that serves your general-purpose LAN first in priority order.

Have you tried connecting Placeshifter from inside your LAN, using the server's LAN IP instead of the Locator ID? Get that working first, then try remoting through the Internet.

[Taddeusz]

I also have two NIC's in my server. I ran into a similar issue when I first installed two NIC's. You say your one NIC is connected to the internet. Does it go through a router at all?

Probably what you need to do is set the following options in your properties file:

miniserver/forced_server_ip=your internet NIC IP
miniserver/gateway=Whatever the gateway address is for your internet NIC, usually a router.

[PeteCress]

Originally Posted by GKusnick

You can change NIC priorities via Control Panel > Network Connections > Advanced > Advanced Settings.

Thanks! This is going to save me quite a few man hours once I get it doped out.

I think I've managed to change the order bc here's how ipconfig /all looks now: (i.e. the adapters are coming up in the reverse of the order they were... and I verified the MAC addresses to confirm that the mobo device is really the first one.)

I stopped, then re-started the SageTV service, but no change.

Doesn't *seem* like I should have to restart the server.... but I guess that is next.

Or am I missing something else?

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : sage
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit
Physical Address. . . . . . . . . : 00-23-54-79-39-A8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.108
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 71.242.0.12
71.250.0.12
Lease Obtained. . . . . . . . . . : Tuesday, September 29, 2009 1:41:31 PM
Lease Expires . . . . . . . . . . : Wednesday, September 30, 2009 1:41:31 PM

Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8169 Gigabit Ethernet Adapter #3
Physical Address. . . . . . . . . : 00-A1-B0-80-32-84
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Tuesday, September 29, 2009 1:43:44 PM
Lease Expires . . . . . . . . . . : Thursday, October 01, 2009 1:43:44 PM

[Taddeusz]

BTW, I have to ask how your network is set up and how your Placeshifter clients and/or media extenders access the SageTV server from within your house. Depending on how you have your network setup those settings may screw up your internal SageTV network because the same settings are used for both "internal" and "remote" clients.

A diagram would be helpful.

[PeteCress]

Originally Posted by Taddeusz

BTW, I have to ask how your network is set up and how your Placeshifter clients and/or media extenders access the SageTV server from within your house. Depending on how you have your network setup those settings may screw up your internal SageTV network because the same settings are used for both "internal" and "remote" clients.

A diagram would be helpful.

Here's a diagram: http://tinyurl.com/y8mwzc3

I have heard of the distinction between "internal" and "remote" clients, but do not have a clue beyond knowing the words.

[Taddeusz]

Originally Posted by PeteCress

Here's a diagram: http://tinyurl.com/yazqonq

I have heard of the distinction between "internal" and "remote" clients, but do not have a clue beyond knowing the words.

Ok, those changes shouldn't affect things then. I was concerned you were doing something janky like using your SageTV server as a router.

[Fuzzy]

another option is to simply bridge the connections. This will still keep directed traffic on the correct interface, but will allow broadcasts across both. Really simplifies setup, since your dual card machine will really only be one IP on the network.

[PeteCress]

Originally Posted by Fuzzy

another option is to simply bridge the connections. This will still keep directed traffic on the correct interface, but will allow broadcasts across both. Really simplifies setup, since your dual card machine will really only be one IP on the network.

The reason I added the separate NIC/Router for the two HD HomeRuns - instead of just plugging them into the main router - was to keep their traffic off of the main LAN.

Sounds like the bridge would put their traffic back on the main LAN.

Do I understand that part correctly?

[Fuzzy]

No, it would not be duplicated on the other half of the lan, unless a packets destination is on the other half of the lan. Wired ethernet is not like wireless, where a fixed bandwidth is shared among all traffic. The switch's job is to route traffic to just the port it's destined for, utilizing just the lines needed... this is what makes a switch different than a hub. A network bridge works effectively the same way. The advnatage being thatsince it's on the same subnet, broadcasting still functions, so network discovery and such still works correctly.

[Beefcake550]

You could also try this:

That old router which has the HDHRs hooked up....turn off it's DHCP server and plug in the 2 HDHRs and computer NIC to the LAN ports. Then, assign a 169. IP address to the computer NIC for the HDHRs (or don't assign anything and it'll just take longer to boot).

You'll have to power down the HDHRs and disable/enable copmuter NIC and reboot the "router".

This will cause the HDHR software to assign addresses to the HDHRs and communicate to them over the NIC you intend. The 169 address should/will tell/show Sage that it is not connected to anything and it should then use the other NIC and life should be good.

This is how I have mine setup and it's been working great for a year now.