I hope there must be some resolution to this. I have the exact reverse of what is commonly the problem. Our small business office recently moved to a new building in a new city. We have a Mac mini running NeXT Cloud. I set things up with our new router (behind ADSL) port forwarding as we need, etc. From outside our network, HTTP, HTTPS, sync services all work well. From INSIDE the lan, nothing works and I can’t even Ping the address. We use dynu dns for hostname resolution, but the IP address behaves the exact same way, so this must be something to do with the router.
Oddly, I am able to access all services using the local IP of the server while within the network. This probably helps point to the solution I am missing. Is there some setting local to the server's network settings that I need to change? Putting the server inside the DMZ and outside the DMZ leads to odd results. Server local address inside the DMZ, nothing works LAN, everything works WAN. Server local address not in the DMZ, everything works WAN, HTTPS to the external IP address works within the LAN, HTTPS to the external IP address works within the LAN, but neither SSH nor NeXTcloud work to the external IP address within the LAN. I find this to be very odd. What would selectively block services like this?
I ran myself ragged doing a systematic and redundant pass through all the settings, adjusting usual suspects like firewalls, and nothing I have tried works.
Any thoughts on how to solve?