F5F Stay Refreshed Power Users Networks network routing

network routing

network routing

Pages (2): 1 2 Next
J
JONNTHENOOB
Member
194
08-03-2016, 11:51 PM
#1
Hello everyone,

Apologies ahead of time for the lengthy explanation. I’m trying to clarify the problem thoroughly. My Plex server is linked to the router through a wireless connection. I also have another PC and a NAS connected via network power adapters that feed into another network adapter, which then goes to the router. Because these adapters are on separate switches or fuses, the speed caps at around 50 Mbps—which is frustrating when streaming 4K from Plex since it pulls media from the NAS.

Since the NAS and server are nearby, I connected them with a gigabit switch and shared the wireless link from the server to the switch, which then went to the network port. Everything seemed fine until I moved both devices onto a subnetwork created by Windows. Now all my devices fall into the 192.168.1.xxx range, while the NAS and PC are on a different subnet (192.168.137.xxx). This means I can’t reach the NAS using a MAC address or an Android device—only through the server.

I attempted to set up a route using CMD with:
Route 192.168.137.0 mask 255.255.255.0 192.168.1.153 (using 153 as the destination IP)
But after that, both the NAS and PC lost internet access.

Is there a solution? Should I try creating a route again, or should I move the NAS and PC to share the same subnet as the rest of the network? Thanks for any advice! This has been really confusing over the past two days.
J
JONNTHENOOB
08-03-2016, 11:51 PM #1

Hello everyone,

Apologies ahead of time for the lengthy explanation. I’m trying to clarify the problem thoroughly. My Plex server is linked to the router through a wireless connection. I also have another PC and a NAS connected via network power adapters that feed into another network adapter, which then goes to the router. Because these adapters are on separate switches or fuses, the speed caps at around 50 Mbps—which is frustrating when streaming 4K from Plex since it pulls media from the NAS.

Since the NAS and server are nearby, I connected them with a gigabit switch and shared the wireless link from the server to the switch, which then went to the network port. Everything seemed fine until I moved both devices onto a subnetwork created by Windows. Now all my devices fall into the 192.168.1.xxx range, while the NAS and PC are on a different subnet (192.168.137.xxx). This means I can’t reach the NAS using a MAC address or an Android device—only through the server.

I attempted to set up a route using CMD with:
Route 192.168.137.0 mask 255.255.255.0 192.168.1.153 (using 153 as the destination IP)
But after that, both the NAS and PC lost internet access.

Is there a solution? Should I try creating a route again, or should I move the NAS and PC to share the same subnet as the rest of the network? Thanks for any advice! This has been really confusing over the past two days.

M
MicMineHD
Member
206
08-04-2016, 12:38 AM
#2
Your NAS needs two IP addresses: one from the power adapter (192.168.1.X) and another from the box-to-box line. ... Or was the power adapter unplugged and internet shared directly from the Plex server to the NAS?
M
MicMineHD
08-04-2016, 12:38 AM #2

Your NAS needs two IP addresses: one from the power adapter (192.168.1.X) and another from the box-to-box line. ... Or was the power adapter unplugged and internet shared directly from the Plex server to the NAS?

M
MNKYTOES
Junior Member
1
08-08-2016, 04:30 AM
#3
Here’s a revised version of your message:

Make sure to include the network—currently referred to as WAN for your PC and Plex server—at the link provided: https://support.plex.tv/articles/200430283-network/. However, that setup seems a bit outdated...
M
MNKYTOES
08-08-2016, 04:30 AM #3

Here’s a revised version of your message:

Make sure to include the network—currently referred to as WAN for your PC and Plex server—at the link provided: https://support.plex.tv/articles/200430283-network/. However, that setup seems a bit outdated...

P
PlayForCC
Member
217
08-14-2016, 03:50 PM
#4
I removed it from the power adapter, sorry I didn't mention that earlier.
P
PlayForCC
08-14-2016, 03:50 PM #4

I removed it from the power adapter, sorry I didn't mention that earlier.

W
WillyRoQuint
Junior Member
4
08-16-2016, 04:14 PM
#5
So, sending data to a second device via a third one is... tough. The simplest fix would be to install another Wi-Fi router, install tomato or another firmware, and use it as a wireless bridge for the devices you need. (Or simply connect a Wi-Fi adapter to your NAS.)
W
WillyRoQuint
08-16-2016, 04:14 PM #5

So, sending data to a second device via a third one is... tough. The simplest fix would be to install another Wi-Fi router, install tomato or another firmware, and use it as a wireless bridge for the devices you need. (Or simply connect a Wi-Fi adapter to your NAS.)

V
Viizion_PvPz
Senior Member
670
08-18-2016, 04:07 AM
#6
In the future, I aim to connect the server to the router and ensure all devices link to the internet through the server, with everything secured via a VPN. My current problem is that the server functions as DHCP for the connected devices, placing them on a separate network.
V
Viizion_PvPz
08-18-2016, 04:07 AM #6

In the future, I aim to connect the server to the router and ensure all devices link to the internet through the server, with everything secured via a VPN. My current problem is that the server functions as DHCP for the connected devices, placing them on a separate network.

D
DerKreiki
Member
178
08-18-2016, 10:13 AM
#7
I notice... I thought I could set up a network using the Windows system on an Ethernet port linked to the switch, connecting it to Wi-Fi on Windows. Something like directing the Ethernet link to either share the same IP range as the Wi-Fi or route its IP ranges from 192.168.137.xxx to 192.168.1.xxx.
D
DerKreiki
08-18-2016, 10:13 AM #7

I notice... I thought I could set up a network using the Windows system on an Ethernet port linked to the switch, connecting it to Wi-Fi on Windows. Something like directing the Ethernet link to either share the same IP range as the Wi-Fi or route its IP ranges from 192.168.137.xxx to 192.168.1.xxx.

C
castielqueen
Member
228
08-18-2016, 01:03 PM
#8
Consider using VLANs and having two separate networks doesn’t require linking your server to two Ethernet ports or Wi-Fi. However, it seems you’re aiming to build an edge network directly on hardware and route traffic through your Plex server.
C
castielqueen
08-18-2016, 01:03 PM #8

Consider using VLANs and having two separate networks doesn’t require linking your server to two Ethernet ports or Wi-Fi. However, it seems you’re aiming to build an edge network directly on hardware and route traffic through your Plex server.

T
Thomawaks
Junior Member
34
08-18-2016, 01:58 PM
#9
Sorry my network knowledge is a bit limited and didn't get half of what you wrote LOL But yeah all in all at this stage I need (due to logistics) to have 1 PC and NAS connected to the server via LAN and then server connected to router via Wifi. PC and NAS get internet OK and good speed, what is doing my head in is the fact that Server is on same IP range as the rest of devices 192.168.1.xxx as it should, but the PC and NAS are on a different IP range 192.168.137.xxx as windows is acting as DHCP server, is there any way to bypass this so NAS and PC get IP from router? Maybe something I can disable on Windows so when LAN connected devices to server get the IP from router via Wifi? Or at least route the ip range 192.168.137.xxx in a way that devices on ip range 192.168.1.xxx can access devices on 192.168.137.xxx I have seen this but either I did something wrong or I am not understanding how to do it... https://www.howtogeek.com/howto/windows/...ing-table/
T
Thomawaks
08-18-2016, 01:58 PM #9

Sorry my network knowledge is a bit limited and didn't get half of what you wrote LOL But yeah all in all at this stage I need (due to logistics) to have 1 PC and NAS connected to the server via LAN and then server connected to router via Wifi. PC and NAS get internet OK and good speed, what is doing my head in is the fact that Server is on same IP range as the rest of devices 192.168.1.xxx as it should, but the PC and NAS are on a different IP range 192.168.137.xxx as windows is acting as DHCP server, is there any way to bypass this so NAS and PC get IP from router? Maybe something I can disable on Windows so when LAN connected devices to server get the IP from router via Wifi? Or at least route the ip range 192.168.137.xxx in a way that devices on ip range 192.168.1.xxx can access devices on 192.168.137.xxx I have seen this but either I did something wrong or I am not understanding how to do it... https://www.howtogeek.com/howto/windows/...ing-table/

T
Taybaybay
Posting Freak
850
08-24-2016, 11:24 AM
#10
Based on the information provided, you should configure the route to direct traffic to the network router at 192.168.1.1 using the correct subnet mask. Alternatively, you can use the server's Wi-Fi IP address (192.168.1.153) if that is more convenient. Avoid pointing the route to an unused router IP unless necessary.
T
Taybaybay
08-24-2016, 11:24 AM #10

Based on the information provided, you should configure the route to direct traffic to the network router at 192.168.1.1 using the correct subnet mask. Alternatively, you can use the server's Wi-Fi IP address (192.168.1.153) if that is more convenient. Avoid pointing the route to an unused router IP unless necessary.

Pages (2): 1 2 Next