No matter the scenario, my Plex clients ALWAYS list my Plex server as “Remote”. I even have a desktop hard wired into the same router as my server and clients (Plex Web via multiple browsers, Plex Media Player, Windows App) still say the server is “Remote”. Server and clients are signed into plex.tv with my Plex Pass account.
Is this normal? Or should it in fact say “Local” (or some other verbiage)?
I posted as a sanity check. Since you responded with questions, I am guessing that NO, this isn’t normal.
All wired connections Gigabit via Cat6.
Verizon FIOS ONT ==> Asus Router == > Plex Server (Same results Windows & Synology NAS)
{Verizon FIOS ONT ==> Asus Router} == > Hard Wired Desktop PC Client
{(Verizon FIOS ONT ==> Asus Router} == >Mobile Device (iOS, Androd, Laptop - apps & browsers) via WiFi Clients
All clients say server is Remote. Server and clients signed into same plex pass account.
Verizon FIOS ONT is the device Verizon (my ISP) installs in (or on) your home to convert the FIOS fiber connection to Cat6. This is my internet connection (as opposed to a cable modem), which connects to the WAN port on my ASUS Router.
Actually, I have another idea:
It may be that you are using an IP range in your home network that is not reserved for private networks.
In this case, all Plex clients will always say ‘remote.’
Compare your local IP addresses with this list:
If they don’t appear there, then this is your issue.
@OttoKerner, yes, my home network was not in the correct range. I’m really at a loss for words for this because it has been set this way for much longer than I will now admit, range suggested by a IT Network Professional. I’m pretty sure this is the only time it has been a problem. It has now been corrected and PMS now says “Nearby” across all clients.
Thank you for taking the time to help with this. An even bigger thank you for using your brain instead of sticking to the script. Too many “help desk” type people/services just stick to the script. (And others that chime in just to get their post count higher.) It would have been easy for you to send me down the DNS Rebind rat hole again (long story, and I had everything else suggested already in place) but you used your brain and realized there was another scenario, and you nailed it.