plex having problems contacting internet

[nojohnny101]

so I have been pulling my hair out on this one. I recently got a new router and have tried resetting everything the same as it was (with same IP address pool, etc.)

I know I'm missing something but I have been through every network setting and router setting that to my knowledge would either affect plex or the freenas box itself.

The specs of the freenas box is below my signature.

Here is how my router is setup:

LAN
IP Address: 10.0.0.1
Subnet Mask: 255.255.0.0

DHCP Server Settings
IP Address Pool: 10.0.1.2 - 10.0.1.50
Default gateway: 10.0.0.1
Primary DNS: 8.8.8.8
Secondary DNS: 8.8.8.4

FreeNAS Settings
Hostname: axio
domain: local
IPv4 Default Gateway: 10.0.0.1

I have a static IP address of 10.0.1.31 setup for Plex and I also have a correct port forward setup that forwards 32400 internally to 32400 externally for 10.0.1.31

Plex is installed within a manually created jail following these instructions:
https://forums.freenas.org/index.ph...all-plex-in-a-freenas-9-3-jail-updated.19412/

I can ping google.com and 8.8.8.8 just fine from within FreeNAS and from within the plex jail.

Plex has an internal IP address of 10.0.1.31 and i can view it fine by going to http://10.0.1.31:32400/web

the jail settings for plex are as follows:
IP Address: 10.0.1.31
IPv4 Netmask: /16 (255.255.0.0)
IPv4 Default Gateway: 10.0.0.1

The problem is I can't claim the server and I had problems before of not being able to setup plex to be access remotely.

I am getting the following errors in the plex logs:

Code:

l 21, 2016 15:39:56 [0x80a2bf000] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can'$
Jul 21, 2016 15:39:56 [0x80a2bf000] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can'$
Jul 21, 2016 15:40:01 [0x80a2bf000] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can'$
Jul 21, 2016 15:40:01 [0x80a2bf000] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can'$
Jul 21, 2016 15:40:06 [0x80a2bf000] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can'$
Jul 21, 2016 15:40:06 [0x80a2bf000] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can'$
Jul 21, 2016 15:40:11 [0x80a2bf000] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can'$
Jul 21, 2016 15:40:11 [0x80a2bf000] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can'$

Anyone have any ideas? I'm at my wits end!

 

[Jailer]

Is there a reason you need 65K IP addresses on your LAN? A /24 subnet mask would be more sensible. Also you've given your Plex jail a static IP address that is within your DHCP range. You're just asking for a future IP conflict with that one.

Couple other things.
Lan Address: 10.0.0.1
DHCP range: 10.0.1.2-10.0.1.50

Are your LAN and DHCP server on different subnets or is that a typo? Did you set up a port forward for your jail?

Need some things cleared up before we can proceed to troubleshoot.

 

[nojohnny101]

Is there a reason you need 65K IP addresses on your LAN? A /24 subnet mask would be more sensible.

to be honest i didn't really understand what he subnet mask set so i just put it on that because the router wouldn't allow me to set 255.255.255.0

Also you've given your Plex jail a static IP address that is within your DHCP range. You're just asking for a future IP conflict with that one.

I was under the impression that the specificed IP pool of addresses (in my case, 10.0.0.2 - 10.0.0.50) defined the range where only IP addresses could be valid, anything IP address set outside of that would not be valid. So you're saying that statically set IP addresses are not bound by the DHCP reservations? I thought one had to set static IP addresses within the DHCP range and that just told the DHCP to not assign those static IPs when dishing IPs out.

those numbers are not typos. I have since changed it to:
LAN Address: 10.0.1.0
DHCP Range: 10.0.1.2-10.0.1.50

Port forward is setup for the jail:

thank you for your time

 

[Jailer]

to be honest i didn't really understand what he subnet mask set so i just put it on that because the router wouldn't allow me to set 255.255.255.0

What router are you using that won't allow you set the subnet mask for your LAN to /24?

Some routers will allow you to "reserve" an IP within the DHCP range. If that's a feature supported by your router then you'll be OK if you've reserved that IP in your router settings. If not you'll need to set the IP to something outside the DHCP rage or change the DHCP range to something that won't conflict with your existing static IP's. If you manually assign your jail a static IP on your FreeNAS machine your DHCP server on your router doesn't know that the IP has been taken and will eventually hand it out to a device when it requests an IP and you'll be stuck with an IP conflict to figure out.

Now that you've made those changes have you rebooted your router to see if they work?

Have you checked your port using an external port checker to see if it is in fact open?

 

[nojohnny101]

i am using a brand new Tp-Link archer c8 v1.0 with firmware 4.0 build 20160517

this is the error that i get when trying to set subnet mask 255.255.255.0 with a router IP address of 10.0.1.0

i'll look into the static IP issues within the DCHP range

I have it working now, the only thing I changed the LAN IP address from 10.0.0.1 to 10.0.1.0

still, why is it not allowing the subnet mask change?
also do i have to specify the subnet mask in the advanced settings for the plex jail?

 

[SweetAndLow]

For someone who doesn't understand networks you sure have a complicated one. It seems like you are creating 2 different subnets on your network. Just make sure all your subnet masks are 255.255.0.0

 

[nojohnny101]

ok. all the subnet masks are at 255.255.0.0

not sure why the router is shouting conflict and forcing me to use the above subnet mask. oh well. it is working now.

the subnet mask from the ISP is 255.255.248.0 that is ok correct? (I know I can't change that anyways)

thanks for everyone's time.

 

[pirateghost]

ok. all the subnet masks are at 255.255.0.0

not sure why the router is shouting conflict and forcing me to use the above subnet mask. oh well. it is working now.

the subnet mask from the ISP is 255.255.248.0 that is ok correct? (I know I can't change that anyways)

thanks for everyone's time.

Your ISP subnet doesn't have anything to do with the subnet on your local area network. You are NATTED behind your router. Everything on YOUR side of the router is up to you, everything on the WAN/ISP side is controlled by your ISP.

I see a lack of fundamental network knowledge here. I think it would be good to do some digging into understanding subnets, gateways, and basic IP addressing. That would help clarify your configuration and topology.

 

[nojohnny101]

thank you for clarifying pirateghost.

i'm already reading up on everything and filling in the gaps on things i don't know. i plan on getting a router once i get a new house (later this year) that i can use pfsense on. that should provide with a wide open playground to put the stuff i'm reading now into practical practice.

thanks. marking this as solved.

 

[gpsguy]

You should have tried 10.64.10.1 with the 255.255.255.0 subnet mask.