Networking help please.

[chlywly 1]

Hey guys, I'm going nuts trying to get Emby to connect to my PC server. 

PC (server) is on 192.168.2.190
Nvidia Shield (client) is on 192.168.1.38

All ports are open, WAN is routed. I have no issue with any other device. I can ping the Shielf from my PC.

However, Emby keep saying "Error connecting to server" using either the WAN or Internal IP. Driving me insane.

[Abobader 3464]

Hello chlywly,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Carlo 4561]

17 hours ago, chlywly said:

PC (server) is on 192.168.2.190
Nvidia Shield (client) is on 192.168.1.38

Hi,
Unless that's a typo the server is on 192.168.2 while the Shield is on 192.168.1 network.  
Assuming these are using a netmask of 255.255.255.0 they won't be able to talk to each other without a static route entry added to your router.

[Luke 42078]

@chlywlycan you please comment on that? Was that your issue?

[chlywly 1]

Hey guys, appreciate the questions.

To be more clear I have WAN static routes setup already (that use my modems IP assigns).

For instance on my 192.168.1.1 Router -> 

192.168.2.1

255.255.255.0

10.88.111.X

My PC (with the Emby server) is 192.168.2.119

And i'm trying to connect it it off my Nvidia Sheild on 192.168.1.32

And I simply cannot, even though I can ping it from my PC.

[rbjtech 5284]

If you can ping the shield from your pc - then you have a route from the 192.168.1.x network to/from 192.168.2.x network - BUT this may be the gateway (router) accepting icmp and allowing it through the firewall.   

You will need to allow port tcp 8096 from 192.168.1.x as a SOURCE (network) and 192.168.2.190 as a destination.   It will then route the traffic.

Alternatively, just put the client and server on the same network - then there will be no need for any routing or gateway dependencies...

[chlywly 1]

1 hour ago, rbjtech said:

If you can ping the shield from your pc - then you have a route from the 192.168.1.x network to/from 192.168.2.x network - BUT this may be the gateway (router) accepting icmp and allowing it through the firewall.   

You will need to allow port tcp 8096 from 192.168.1.x as a SOURCE (network) and 192.168.2.190 as a destination.   It will then route the traffic.

Alternatively, just put the client and server on the same network - then there will be no need for any routing or gateway dependencies...

I spent 2 hours trying to do just that to no avail and did not understand it, even the gateway said that the port 8096 was forwarded... I was keeping these off my PC/Quest network for a reason; I wanted a stable Gigabit connection just for those 2 devices, and another stable Gigabit for other peripherals. 

Edited October 28, 2024 by chlywly

[JackBowman 35]

You need to be on the same class IP address range (192.168.1.x) as the Nvidia or create a secondary IP on your PC for the (192.168.1.x) address range

Edited October 28, 2024 by JackBowman

[chlywly 1]

5 minutes ago, JackBowman said:

You need to be on the same class IP address range (192.168.1.x) as the Nvidia or create a secondary IP on your PC for the (192.168.1.x) address range

Sorry but I don't believe that is accurate.

[pwhodges 2012]

Have you specified in Emby's network page the other subnets which are considered local?

Paul

[chlywly 1]

3 minutes ago, pwhodges said:

Have you specified in Emby's network page the other subnets which are considered local?

Paul

I have indeed.

[JackBowman 35]

9 minutes ago, chlywly said:

Sorry but I don't believe that is accurate.

What I told you is the two easiest ways to accomplish this if both PC and Nvidia Shield are local. You of course want to match the router IP to make internet access simple as well. Why do you require different class c addresses?

Edited October 28, 2024 by JackBowman

[chlywly 1]

2 minutes ago, JackBowman said:

What I told you is the two easiest ways to accomplish this if both PC and Nvidia Shield are local. You of course want to match the router IP to make internet access simple as well. Why do you require different subnets? 

I already mentioned it above. Being on the same subnet would indeed solve this, but would break my network in other ways. That is not why I posted this thread.

[JackBowman 35]

Creating a secondary IP on the PC that matches the  Nvidia Shield should not break anything. My assumption is that your PC is Windows.

Edited October 28, 2024 by JackBowman

[chlywly 1]

2 minutes ago, JackBowman said:

Creating a secondary IP on the PC that matches the  Nvidia Shield should not break anything. My assumption is that your PC is Windows.

Perhaps I misunderstood, how would creating a secondary IP help and how would I go about that?

[JackBowman 35]

6 minutes ago, chlywly said:

Perhaps I misunderstood, how would creating a secondary IP help and how would I go about that?

What version of Windows are you running on the PC?

[chlywly 1]

3 minutes ago, JackBowman said:

What version of Windows are you running on the PC?

11

[JackBowman 35]

Here you go... 

 

[chlywly 1]

1 minute ago, JackBowman said:

Here you go... 

 

Thanks, Ill try this out and report back.

[JuJuJurassic 49]

Why do you have two separate networks / subnets? I guess it's to reduce / segment the network traffic. You could cheat and set the subnets on both "networks" to 255.255.252, then both "networks" would appear to be on the same network. It would stop the traffic segregation between the networks, but could be useful as a test.

 

[chlywly 1]

1 minute ago, JuJuJurassic said:

Why do you have two separate networks / subnets? I guess it's to reduce / segment the network traffic. You could cheat and set the subnets on both "networks" to 255.255.252, then both "networks" would appear to be on the same network. It would stop the traffic segregation between the networks, but could be useful as a test.

 

Subnets are already 255.255.255.0 on both networks. My modem requires 2 separate network/peripherals to pump full Gig/up-down split on a 2Gigabit banwidth frame.

Edited October 28, 2024 by chlywly

[JuJuJurassic 49]

yes, so there are 2 separate subnets, 192.168.1.x and 192.168.2.x, by changing the subnet to 255.255.252 the traffic would be on the "same" network. if you set the subnet to 22 bits, the network range is 192.168.0.0 - 192.168.3.255, which encompasses both address ranges. Look here https://visualsubnetcalc.com/

 

 

[chlywly 1]

2 minutes ago, JuJuJurassic said:

yes, so there are 2 separate subnets, 192.168.1.x and 192.168.2.x, by changing the subnet to 255.255.252 the traffic would be on the "same" network. if you set the subnet to 22 bits, the network range is 192.168.0.0 - 192.168.3.255, which encompasses both address ranges. Look here https://visualsubnetcalc.com/

 

 

Sorry I meant both subnets are on 2 different subnet masks. Do you mean for me to try 255.255.252 and .251? What difference would that make between 192.168.2.x and 1.x

[JuJuJurassic 49]

TCPIP uses the subnet mask to work out if the network it's sending to is local or not and if it should go to the default gateway. The device does a logical AND between the IP address and the subnet. In the case of a 255.255.255.0 or /24 subnet with an IP address of 192.168.1.5

11111111.11111111.11111111.00000000 = 192.168.1.5

11000000.10101000.00000001.00000101 = 255.255.255.0

the network is

11000000.10101000.00000001.00000000 = 192.168.1.0

192.168.1.x

with the address of 192.168.2.5 and the subnet of 255.255.255.0

11111111.11111111.11111111.00000000 = 255.255.255.0

11000000.10101000.00000010.00000101 = 192.168.2.5

the network is

11000000.10101000.00000010.00000000 = 192.168.1.2.0

192.168.2.x

but with a subnet of 255.255.252 or /22

11111111.11111111.11111100.00000000 = 255.255.252 or /22

11000000.10101000.00000001.00000101= 192.168.1.5

the network is

11000000.10101000.00000000.00000000 = 192.168.0.x

with the address of 192.168.2.5 and the subnet of 255.255.252.0 or /22

11111111.11111111.11111100.00000000

11000000.10101000.00000010.00000101

the network is

11000000.10101000.00000000.00000000 = 192.168.0.x

192.168.0.x

Therefore both 192.168.1.5 and 192.168.2.5 are on the same network .

So if both devices changed their subnet to 255.255.252 or /22 they would be on the same network and able to communicate.

I hope this helps.

Edited October 28, 2024 by JuJuJurassic

[chlywly 1]

11 minutes ago, JuJuJurassic said:

TCPIP uses the subnet mask to work out if the network it's sending to is local or not and if it should go to the default gateway. The device does a logical AND between the IP address and the subnet. In the case of a 255.255.255.0 or /24 subnet with an IP address of 192.168.1.5

11111111.11111111.11111111.00000000 = 192.168.1.5

11000000.10101000.00000001.00000101 = 255.255.255.0

the network is

11000000.10101000.00000001.00000000 = 192.168.1.0

192.168.1.x

with the address of 192.168.2.5 and the subnet of 255.255.255.0

11111111.11111111.11111111.00000000 = 255.255.255.0

11000000.10101000.00000010.00000101 = 192.168.2.5

the network is

11000000.10101000.00000010.00000000 = 192.168.1.2.0

192.168.2.x

but with a subnet of 255.255.252 or /22

11111111.11111111.11111100.00000000 = 255.255.252 or /22

11000000.10101000.00000001.00000101= 192.168.1.5

the network is

11000000.10101000.00000000.00000000 = 192.168.0.x

with the address of 192.168.2.5 and the subnet of 255.255.252.0 or /22

11111111.11111111.11111100.00000000

11000000.10101000.00000010.00000101

the network is

11000000.10101000.00000000.00000000 = 192.168.0.x

192.168.0.x

Therefore both 192.168.1.5 and 192.168.2.5 are on the same network .

So if both devices changed their subnet to 255.255.252 or /22 they would be on the same network and able to communicate.

I hope this helps.

Thanks I think I understand, where as Im on 255.255.255.0 I should change subnet mask on both routers to 252.0 (will try)