We help IT Professionals succeed at work.

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

mbath20110
mbath20110 asked
on
542 Views
Last Modified: 2013-11-16

Zero expertise with my WatchGuard firewall other than being the onsite monkey while the WatchGuard tech walked me thru installing it and setting it up.

Ok Ok. Maybe not giving myself enough credit.  I DO know how to get into Policy Mgr. and do the basics.

To my question.  Running Outlook Webaccess on my Exchange 2003 server.  If I or my users want to chech their webmail they go: 65.154.98.141\EXCHANGE (where EXCHANGE in the actual DNS name of my Exchange server).

But let's say I want to play and I have IIS running on another server, say, APPLICATIONS.

How do I configure my Firewall so I can go 65.154.98.141\APPLICATIONS and see any test websites that I'm running on APPLICATIONS.

I'm using NAT on the firewall to translate the external IP to the internal IP of EXCHANGE but it seems that it will only let me do one; in other words I can't add a second NAT for APPLICATIONS.

Any thoughts???
Comment
Watch Question

Commented:
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...

Author

Commented:

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.
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.