Server Version#: Version 1.23.4.4712
Player Version#: Version 4.57.4
I have been tearing out my hair trying to figure out why my server had issues keeping the remote access connected after I received the newest G3100 router.
Ive used plex for several years now and this issue litterally began after i upgraded fios routers.
I decided to just search around and it seemed that a lot fo people ran into the same issues I had, but never came to any solution. Ive tried many things to get this to work, and I finally believe i have stabilized my remote access.
After mad sciencing my router so much, I decided to reset to default and then I found these fixes, that I believe has fixed my issues.
First, I used this information exactly. Here is the original post if you wish to see Verizon G3100 Router - #19 by jdini76_gmail_com
basically he set his port forwarding for 32400 to both TCP and UDP, instead of just TCP. In his original post, he has a picture example. Out of every port forwarding direction Ive used, this is the only one that has worked so far, so just try it before you knock it.
You select port forwarding from the firewall settings and then ypou select the IP you want to use. Select custom ports, protocol to both, source ports to any, set destination to 32400, forward to 32400 as always. Add and apply.
Secondly, after scouring the verizon fourms, I found this, which i copied exactly, and now i have no remote access issues. Here is the post to the original topic Solved: configuring network for Plex media server - Verizon Fios Community
" Re: configuring network for Plex media server
Ok, that other poster’s post helps if you had a third party (own RJ-45 WAN port router) and want to keep FIOS TV working.
Since you do not, moving along.
You need to setup a Static IP on/for the computer that you want to host on and then forward to it.
There appears to be two ways of doing that, but I am not sure of that.
I am sure of one way of doing it, so I will tell you how to do that it that way.
#1 In the router go to Advanced → IP Address Distribution
#2 Make sure the DHCP Range does not occuy the whole subnet.
#3 If the DHCP Range occupies the while subnet, select for Network(Home/Office) the edit button under action that looks like a pencil/pen and then make the DHCP Range smaller.
For example if the router’s LAN IP is 192.168.1.1 and the DHCP Range is 192.168.1.2-192.168.1.254, then you could make the Starting IP Address 192.168.1.100 (which would make the DHCP Range 192.168.1.100-192.168.1.254)
#4 Then on your computer that you want to host on/forward to, you make it’s manual Static IP outside of the DHCP Range.
For example with the router at 192.168.1.1 and the DHCP Range 192.168.1.100-192.168.1.254, outside of the DHCP Range would be 192.168.1.6
Full Settings outside of the DHCP Range for example would be:
IP Address: 192.168.1.6
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
(At least one DNS Server required, but typically two) ex 4.4.4.3 and 4.4.4.4
//
The second way of setting a Static IP, appears to be go to Advanced → IP Address Distribution → Connection List . Then from the list, that looks like this UI
http://screenshots.portforward.com/routers/Verizon/FiOS-G1100/DHCP_Connections.htm
Select the Edit icon under Action ."
This is assuming youve already set an static pi through your pc directly.
Control panel → Network and Internet → Network connections. Right click you connection and select properties, then highlight IPV4 and select properties, then set your static IP. For my fix, I used 8.8.8.8 (preferred) and 4.4.4.3 (alternate) as my DNS stuff.
My server has been stable to the last several hours and I havent had anymore issues. Hopefully this helps anyone who found theselves in the same boat.
