01-27-2025, 10:01 PM
@5-pot-fan
Couple of things-
1. As Tim noted, you've configured your two players to use different DNS resolvers.
Host RPi4 is using the DNS resolver on your network router. Apparently, it caches the hostnames of devices discovered on the LAN so it can tell host RPi4 Where the host with hostname RPi5 is (Evidence: this host can mount the SMB shares from the other using the unqualified hostname). Only if the router can't handle a DNS request does it forward it to an upstream server (your ISP's or whatever you configured your router to use).
Host RPi5 is directly using the Google DNS server(s) out in InternetLand, which has no idea what the unqualified hostname "RPi4" should resolve to.
Proposed solution: change the DNS resolver on RPi5 to your network router: 192.168.75.250
2. That scan function in Remote NAS Source actually uses mDNS-related rather than DNS-related tooling to discover shares on the LAN. If it returns "RPi4/WGreen" as a path, try editing the path manually to add the mDNS .local pseudo-domain, e.g., "RPi4.local/WDGreen". This likely will make my item 1 moot.
Regards,
Kent
PS - the router my ISP provided does not has a local DNS resolver. I have to use mDNS addressing for pretty much everything on my LAN. The router also does not allow me to change its default primary and secondary DNS server addresses. Neither is the norm for most residential routers.
Couple of things-
1. As Tim noted, you've configured your two players to use different DNS resolvers.
Host RPi4 is using the DNS resolver on your network router. Apparently, it caches the hostnames of devices discovered on the LAN so it can tell host RPi4 Where the host with hostname RPi5 is (Evidence: this host can mount the SMB shares from the other using the unqualified hostname). Only if the router can't handle a DNS request does it forward it to an upstream server (your ISP's or whatever you configured your router to use).
Host RPi5 is directly using the Google DNS server(s) out in InternetLand, which has no idea what the unqualified hostname "RPi4" should resolve to.
Proposed solution: change the DNS resolver on RPi5 to your network router: 192.168.75.250
2. That scan function in Remote NAS Source actually uses mDNS-related rather than DNS-related tooling to discover shares on the LAN. If it returns "RPi4/WGreen" as a path, try editing the path manually to add the mDNS .local pseudo-domain, e.g., "RPi4.local/WDGreen". This likely will make my item 1 moot.
Regards,
Kent
PS - the router my ISP provided does not has a local DNS resolver. I have to use mDNS addressing for pretty much everything on my LAN. The router also does not allow me to change its default primary and secondary DNS server addresses. Neither is the norm for most residential routers.
