My ISP Modem also has a DHCP wifi which happens to sit near my kitchen, but I never use it, I am using my AirPort Extreme for all my devices and I have set it up to DHCP mode because I prefer IP (10.xx.xx.xx instead of 192.xx.xx.xx) (hence facing double NAT)
So long story short, I have noticed that (AirPort Extreme) wifi speeds are terribly slow in the kitchen and Plex really struggles in there.
Now when I connect to this ISP modem wifi, it is not able to detect Plex locally, it shows as remote connection.
Is there some network settings in Plex that I can do to bypass this and make Plex locally available on the ISP Modem (after all ISP modem and AirPort Extreme are connected via ethernet)
Double NAT will always give you a world of trouble, in many situations.
Did you know you can configure your AirPort Extreme to operate as a basic access point? It won’t do any NAT or DHCP in this mode and will eliminate your double NAT problem. Worth reading up on and giving it a try, imho.
How is your machine running Plex Media Server connected to the network, out of curiosity? Is it connected to the 10.0.0.0/8 network on your AirPort Extreme or the 192.168.0.0/16 on your ISP’s equipment?
(Also, it’s not 192.xx.xx.xx, it’s 192.168.xxx.xxx. That’s your class B RFC1918 subnet. As @JasonNalley alluded to: there’s really nothing to choose between the three networks (there’s 172.16.0.0/12, too) as they all do the same job, just with different sizes of IP address space)