I remember you've once said that Web proxy service is not actually needed for Web server publishing. I would want to disable it not allowing my Web Proxy & sNAT clients to get much from this life.

Only firewall clients should benefit from using Internet. Now I have a couple sites published like this:

1. As far as I have only one real IP, I have to distinguish sites by host header names.

2. I created a Destination set in ISA Server and assigned a real name to it, i.e: home.realname.ru

3. Using IIS MMC Snap-in I configured site to reply as following: using port 80 and INTERNAL Win2000 domain name and host as host header; and using port 8081 and no host header name.

4. I created Web Publishing Rule that redirects all requests to my Destination (home.realname.ru) to internal IIS (192.168.0.10:8081), sending original host header.

However, this configuration works ONLY IF WEB PROXY IS RUNNING. But for me, I wanna get rid of this stupid service.

My question is: how to publish internal Web on a server which is SecureNAT client?

Thank you very much in advance,
-Vsevolod,
MCSE,MCT

If you use Web Publishing Rules, you must have the Web Proxy service enabled.

When you publish via Server Publishing rules, you'll need to make a Protocol Definition for inbound HTTP TCP Port 80 and use that in the Server Publishing Rule.

Now, a good question is whether your Host Headers will still work. I haven't tested out that configuration yet. I would suspect that they would still work since the request is forwarded to the internal server which having the web proxy service add itself as the source of the request to the internal web server.

However, I could be wrong

Note that you can still have the internal web server be a SecureNAT client.

HTH,
Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/

Get it Here!