Server Version#: 1.25.9.5721
I have Plex running on a Synology Arm based Server and I recently added a mini-PC running Windows to have better performance transcoding. The Windows server reports as an Indirect connection, but the Synology does not. How can I configure my system to avoid an indirect connection?
This is usually based on a bad remote access setup. If the other server is located in the same network and has no issue, this implies the issue will likely be in your own router or home network configuration.
This guide is a good start to dig into what’s causing remote access issues:
Each Plex servers has Static IPs.
Port forwarding rules for each at the router.
I used the canyouseeme.org. It works for the Synology Server (port 32400) but when I try the Windows Plex (port 24230) - I get an error…
Error: I could not see your service on 71.244.164.17 on port ( 24230 )
Reason: No route to host
I port forward rule is clearly in the FIOS Router.
I will continue reading more but I am confused why it cannot see each port equally.
Could be as simple as the ISP blocking that particular port… or some typo in the port forward configuration.
Share a screenshot?
Sometimes Windows feels the need to re-classify its network connection as “public”. Which causes the firewall to close all ports.
I’d verify that.
I would have posted earlier but I did not see how to do so - it was too easy.
and the Windows machine
C:\WINDOWS\system32>ipconfig
Windows IP Configuration
Ethernet adapter Ethernet 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : myfiosgateway.com
Link-local IPv6 Address . . . . . : fe80::f96d:772f:3b2c:7b0d%8
IPv4 Address. . . . . . . . . . . : 192.168.1.195
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
I will check that but would it affect the canyouseeme.org port test of the border router?
Canyouseeme is pinging the destination port.
If the destination computer of the port forwarding has closed all its ports, the test will fail.
Even if the gateway (i.e. your router) has a working port forwarding established.
The Windows machine had the internal port set as private.
should I set it as public instead?
No. “Private” is very much what you want.
You should double check that your router’s user interface isn’t swapping the input fields of internal and external port numbers.
It wouldn’t be the first time.
thought so.
Oddly, each time I check the ethernet configuration in the settings, it is listed as DHCP, so I set it as manual and next time I check, it is DHCP again (at least the setting is listing DHCP - perhaps as a default setting if selected?). Windows seems stubborn. The address has not changed though.
I did swap the port numbers in the interface and it would not let me set it because that port number was already assigned to the Synology Plex machine.
I am using the Gigabit FIOS Router
I used cmd line netsh to assign port as static and the Settings now show as Manual. I do not think that was the problem.
I think I conquered the problem.
the key was that setting the IP as manual through the settings app did not stick because I was not an Admin. running cmd as admin and using the netsh cmd fixed that. It seems that plex changed the port for the router so once I updated the port forwarding rules, the redirect problem was fixed. canyouseeme.org now works and sees the port!
thanks to all for the suggestions. This should have been more apparent to me sooner but I am a novice @ networking…
ps - does Settings in Windows run with Admin privileges? If it does not and changing network settings to manual are ignored, what’s the point?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
