IIS, external access and brain overload...
We're running Server 2003 and need to allow external connections to our new digital signage system.
Here's the setup - we have a no-ip.org domain which currently has two sub-folders - /exchange which links to OWA and /portal to Engage portal.
I want to set up a third sub-folder to allow external access to an internal IP address. I've tried setting up port forwarding in the router, to send all port 90 traffic to the internal IP. IIS is then set up with a web site to direct the traffic, but when I try this off-site I get an error saying (external IP):90 is unavailable.
Is this possible in IIS, or am I banging my head against a wall for no reason?