When I try to browse to the server I check the "Status" of both interfaces. The external interface does see an increase in it's incoming packet count. The internal interface shows NO increase in it's outgoing packet count. i.e. It appears the ISA server isn't forwarding the request so I doubt it's an access issue on the IIS box.

I set up a destination set to the internal IIS server using both the NetBIOS name (using the browse button to select the server) and its' IP address. Neither one works. Reading other posts on this site I also tried disabling packet filtering and alert monitoring and that didn't help either.

This system was set up as 'firewall only'.

I noticed on Proxy 2 that you can specify a domain user account to use for anonymous access but ISA doesn't seem to have a similar specification. (I noticed this because I was wondering if it was a domain access issue ???)

I don't know what else to try. If anyone knows what else I can try, PLEASE HELP!

I was able to get it to work by setting the destination set to "All Destinations" in the Web Publishing Rule.

Why wouldn't it work if I selected a destination set where the IIS server is specifically identified as the destination ?

When configuring your destination sets, you need to specify the FQDN that will resolve to the external interface of your ISA Server. For example, if you create a destination set for www.mywebsite.com, the DNS entry on the public DNS Server should resolve that name to the IP address of your external interface.

Then you use the destination set in your Web Publishing rule, but telling the rule to use that destination set and to forward requests for that destination to the IP address of your internal server.

HTH<
Tom

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