okay, here's a head scratcher.

Got a sub domain that points to a static IP (my static IP). It can access and work externally from any device via IP:8040 and (subdomain):8040

For whatever reason, it will not resolve internally on my ScreenConnect server. Local/internal IP:8040 is the only way it works.

I have correct port forwarding rules set in the router to the SC Server/Host (which also has a static IP behind the NAT)
The router port forwarding is working, as I can access the SC host externally.

Seems to be something on this Windows 7 pro box that's running the SC host that is stopping everything other than it's internal static IP:8040

(tried Win 7firewall off, different DNS's, still failing)

Could the router being preventing the outgoing requests to a DNS and back to itself again?

The problem is no support invitations can be sent because the link generated is my internal/local IP:8040. Competely useless.

Any light on the mystery would be greatly appreciated.

Thank you.

Edited by user Monday, May 1, 2017 3:28:59 PM(UTC)  | Reason: Not specified

Yes, either your router does not support NAT Loopback or that feature is turned off. NAT Loopback is required if you want to be able to use the public facing address from computers internally.