Here is my specs…
4 Sep 04 2016 12:56:40 54.229.22.127 46336 192.168.1.10 32400 Deny tcp src outside:54.229.22.127/46336 dst inside:192.168.1.10/32400 by access-group “outside_in” [0x4cc7a6a3, 0x0]
I watched my firewall and noticed this traffic. It shows the Plex.tv site, 55.229.22.127 attempting to connect to my PMS over port 46336. not sure why they hit my front end on port 46336 and ask for port 32400 on my PMS?
There is ‘control protocol’ and streaming protocol .
If that was a reply to an already open socket, that makes perfect sense as that’s part of the outbound-originated ‘control protocol’. Your server’s status, your account, etc, all that goes through that port and syncs with Plex.tv
If you think “Web server”, each has a control port and a service port. 32400 is the ‘web facing’ port. the other port (46336 in this case because it’s random) is that control port.
I fixed it. It appears that Plex previously connected to my PMS using only port 32400. Now they come in over different ports and I have to forward the traffic to port 32400 on my 5520.
so your port forwarding wasn’t as you thought?
on the LAN, PMS listens to port 32400, independent of what it may tell plex.tv to contact it at. That’s what UPnP / manual port forwarding handles (port redirection)
The odd thing is that it was working fine until the upgrade. I am not really sure what changed. I had to change the source port/range to default (1-65535) and destination port/range to 32400. Now when I login to Plex.tv and launch the application, it can see my server just fine.
DSM upgrades are sneaky. If there was even a hint of ‘E-Z Internet’ usage (if you tried it some time in the past), it could easily have latched on to that and done its thing.
Either way, glad you’re working
So now it is broken again. I am able to get to the servers web page from outside of my network, but when I try to login it says the server can’t be found.
