I am new Plex. I have read a number of discussions from this forum and it is somewhat over my head. A little guidance would be appreciated.
Details:
OS - Windows 10
Plex - latest version - installed about 3 days ago. Lifetime license.
Currently hard wired, not using wifi, but may in the future
Network configuration:
A. Windows machine is wired to an unmanaged TP-Link 16 port switch.
B. The switch has 2 wireless routers attached to the port. I can see Plex on the downstairs firestick, so this seems to work.
C. The TP-Link switch is attached to an AT&T modem
Experience/Issue:
A. when enabling remote access, I can see there are two (private and public) IP addresses, but the results are “Remote Access is disabled”
B. In some instances, I can select manual port and it will enable remote access then quickly go to disabled
C. I can remove the port number and refresh again and I will see the two ports and it will go from enabled to disabled.
D. In some situations Plex will remain enabled for a time and then disable itself.
So the route needs to go from the computer, to the switch, to the AT&T modem to get this to work. It seems that locally it does work.
Not familiar with all of the network jargon, so keep this simple, if you can. Also if I open UPnP, is that a major security hole?
One last question. I have installed a HomeRun device for TV. Can you share out a live broadcast? I do not see that as an option, but I also do not have anyone remote to test with.
Have you configured your AT&T router/modem to allow for that kind of external port forwarding? Usually going with a manual port forward tends to be more stable/reliable – but UPnP can also work.
You might want to take a look at this guide on troubleshooting your remote access. Any findings from that will help pin down the problem you’re experiencing.
As a side note:
The remote access status indicator displaying a green icon and then switching to red doesn’t mean remote access starts ok and then fails. This is based on how Plex detects the remote access status in different steps and only turning it to “red” after finishing all the steps (and failing in the end).
UPNP is considered a risk. It seems to be an automatic protocol for devices within your network to punch a hole (port forwarding) in the router automatically. Plex will attempt to do this for itself for the one port it needs. If this fails, then you must manually do a port forward rule in the router towards the server. The reason it is a risk is that if any small virus manages to enter your network (downloaded a suspicious file) it can then punch a hole in the router automatically to allow a bigger virus payload to enter
If you change the (external) port number on the router, you must tell your Plex server this, as it reports this different port number to any client that connects. Note: Plex uses the same port on your computer no matter what, you cannot change that. But you can have a different external port on the router in order to obscure the reason for an open port on the router. Make sure you set it up correctly in the router if you do this, or just skip that if you are uncomfortable with doing it right.
Anbother thing to watch for after this would be a local Windows firewall. Make sure that it is not blocking traffic as well. I’ve heard some people having issues connecting due to a Windows firewall.
