WatchGuard Firewall - How can I point to another web server on my network.

here is one way (easiest I think...) lets just use the same IP address...

first, I am assuming that your web server is called APPLICATIONS. and your test web sites are located on APPLICATIONS as subfolders or files under "wwwroot" folder of your IIS?

on your firewall, use NAT to map the TCP port 80 or the external IP (65.154.98.141) to the internal address of your web server (APPLICATIONS). so now all HTML traffic will be directed to the APPLICATIONS machine's "wwwroot" folder (given that it is an IIS machine).

so to test, place a sample web page into the wwwroot folder and lets call it default.htm for now, then use IE and browse to http://65.154.98.141/default.htm and you should see that web page

now, I don't really know how your test sites are created or stored... but its generally created as sub folders under the wwwroot folder. So lets say that I have a test site called TESTSITE01. it would be physically located on \\APPLICATIONS\wwwroot\testsite01.

Then use IE and browse to http://65.154.98.141/testsite01/yourwebpage.htm

I hope this helps...

Thanks for respsonding RLiu,

I think you've got me on the right track but the sticking point is, I want to preserve the IP NAT to my Exchange server (so my users can keep getting OWA).

So to refine my question, if I want to leave in place, 65.154.98.141/EXCHANGE, how do I add 65.154.98.141/APPLICATIONS, which is where, as you correctly stated, my test website would be?

Or, is this even something that should (can) be done via the firewall?  Can I do some internal mapping or sharing of folders on Applications that points to Exchange?

And maybe my larger question is,  is what I'm proposing really proper network design?  Should I really be hosting websites on different machines in my network?  If I've already got IIS running on my Exchange server then that's where any and all other websites (internal or external) should be located.

Thanks again.