Port...Forwarding/Mapping/Starboard????

Hello to All –



I’m a newbie on the Admin side of IT, so please bear with me.



The problem: 2 servers, 2 web apps, both need to be served to Internet. The website hosted on Primary server works fine, can be accessed on LAN and WAN. The ASP app on SQL server cannot be accessed from either LAN or WAN.



The Configs:



Primary server: Win SBS 2003, IIS 6.0, MS Exchange.

· Serves company web

· Serves Exchange for Outlook and web-based.

· IIS Default Web Site set to Internal IP, Port 80, host header (mycompany.com).



SQL server: Win 2000, IIS 5.0, MSDE

· Serves ASP app

· IIS Default Web Site set to Internal IP, Port 81, host header (myapp)



Netgear FVS318 firewall/router:

· HTTP opened on port 80 on Primary server IP.

· Custom service (myapp) opened on port 81 on SQL server IP.



According to software tech support, the ASP app should forward port 81 to port 80 (???) so that the following URL should open the app. http://www.mycompany.com:81/myapp/default.asp



But….this doesn’t work. Can someone point (no pun intended) me in the right direction with this?



Thanks!!!

Only if you explain what "doesn't work" means to you.

Sorry about that Doug. The link didn't open the ASP page. However....

I finally managed to get the link work.....Sort of!

The ASP page opens for everyone outside of the LAN. When a user types in http://www.mycompany.com:81, the page is displayed properly to those on the WAN. Internal users receive a "Page Not Found" error.

I think this is an issue with DNS. Does anyone have any comments about this type of situation??