From: houston, texas, usa
Thanks for the reply, figures I'd have an odd problem. I'll fill-in some info:
I'm using a web publishing rule to publish the site. Also, I'm using IIS, and since I'll be hosting a friend's site, I'm setting IIS up to use Host Headers. I've also created one web site without a host header defined so that, in "theory", if a browser doesn't send the host header, the surfer will get a message to upgrade his/her browser.
In the web publish rule, I've configured it to foward the original header, so that I don't have to define a whole bunch of aliases on my internal DNS.
Here, you can connect to my site to test this. If you go to "www.carsandfish.com" you should see my page. If you then go to "carsandfish.com" you'll see the error page about incompatible browsers. This error page comes up because ISA is forwarding the web request to IIS, but with the header "carsandfish.com" which IIS is not configured for, so it displays the default web site (my error page). Hopefully everything is making sense :-)
My thinking is that with the destination set defined for "www.xxx.xxx" ISA should drop "xxx.xxx" and display a 403 Forbidden, similar to when you try to connect to my site with just an IP address (184.108.40.206)
Thanks again for you help,