I’m totally confused then. My connection is fiber. Remote access has worked fine until about a week ago following a command to plex via Alexa going sideways.
My router connect via a wired connection, and the plex server is a wired connection to the router. Direct link may have a satellite connection, but i think it is for Television services.
From what I can see from your screenshots and logs everything is ok.
Since you are using Plex Server on a Windows machine, check the Win10 firewall. Your remote connections will get to your server with public address, if you enablex Plex with a private firewall profile your connections will pass through the Dlink wifi router but will be blocked on the Windows server.
Try to connect externaly to your server. You can check if external packets are getting to your server with a sniffer, like Wireshark, or can check on the command prompt with
netstat -an | findstr 32400
On the left column you’ll have your IP address, on the right incoming connections. You are expected to see your external IP trying to connect to your server.
You can check your firewall rules on the comando promt with
netsh advfirewall firewall show rule name=all dir=in
look for the entry with local port 32400.
Remote IP must be “any” for your connections work.
Thank you very much!
I’m not sure what this means:
I tried it after trying to my ip address:28658 which got a took too long to respond.
I don’t see what appears to be an external ip address from my phone.
It means that you have no external IP coming to your server.
Left side is the machine were you gave the netstat command. The 127.0.0.0 are loopback addresses (a computer always has this interface, to “talk” itself).
The [::] is the IPv6 loopback interface.
I assume that you are using the Plex interface on the machine itself, since on the right side (“outside” connections) you have ports talking to :32400.
The 192.168.0.195:32400 indicates that this other machine is another Plex server that you are trying to reach from your local machine.
Your connections are being blocked (or not reaching) the WAN interface of your D-link router.
I have a simmilar model, looking on the manual I found a DMZ setup. Look your’s model manual and look for DMZ, try to enable it and see if you have success on your connections.
No rules with port 32400 on your Windows firewall?
Not that I could tell. Thanks for that second command.
It produced a long result, and I don’t think I saw 32400 in their any where.
Is that command only for the windows firewall. I use eset internet security, but I tried uninstalling that and still couldn’t get remote access to work.
I’ve tried ‘pausing’ the firewall, and no luck.
This was working with the same firewall and router, and so on, until I had a problem when I told alexa to play a video on my firestick. Then remote access went bye bye and I’ve had no luck restoring it.
Yes, this command is for the windows firewall.
So, if disabling the firewall makes no effect, try the DMZ approach.
I think that the Alexa and firestick problem was a coincidence. I assume that your Alexa, Plex and Firestick are all on the same network.
By the way, you router it has a 2.4GHz and 5GHz WiFi combo? How did you set it? The advanced mode, with separate WLANs for each frequency or the simple mode, one WLAN and the router giving the access as it sees fit for the client?
I think the latter, but I’m not sure actually. Would this make them be on separate subnets, effectively? If I just drop the port forward, and let upnp handle things, it works sporadically.
Check this setting. With separate WLANs some devices seems to lose connection and/or don’t “see” other devices on the network. I had problems connecting Chromecasts on my TVs, and I had to change to the simple mode.
Test the DMZ setting also.
When you say DMZ, does that mean the Plex Server and the echos would all be in the DMZ, and if so does that create significant security risks???
Isn’t the DMZ just open to any Tom, Dick or Harry to mess with devices there?
Sorry for the naive question, and thanks for your help.
If your router model is like mine, the DMZ has an option to select one IP address to be on DMZ. It is a temporary setting.
You need to narrow down where the problem is happening.
If you want to be really safe, you can get some computer, connect it to the WAN port of the router, give it a fixed IP address (10.0.0.1 netmask 255.255.255.252) and change the setup of your router to static IP addres and use 10.0.0.2 netmask 255.255.255.252
You can leave the everything on the DMZ. Then you can redirect any port that you want and test it from the PC using the 10.0.0.2 address as target.
Is your Plex connection wired or wireless?
The windows plex server is attached by cable to the my dlink router.
The echo clients of particular concern are on wifi.
Other clients such as my phone, at least when on the house wifi have no problem accessing content from the plex server, just the echos.
I’m not sure, but I think alexa contacts the plex server from a webaddress external to my small network. Alexa can’t seem to do anything unless the internet is avaiable.
Turns out it was firewall issue. I don’t use the windows firewall, and finally figured out the rules I need for my firewall to stop interfering with Plex remote access.
Nonetheless, think you for your help.
Nice that you solved the problem! 
Alexa does not work without internet connection. The voice commands are sent to the Amazon cloud…
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
