Discussion Locked

IIS 4.0/Websense Authentication/ Website

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have IIS 4.0 running with MS Proxy 2.0 SP1. I have WebSense Filtering instaleld onthe same machine as well. I have Also Websense Reporter installed on another machine. In order for the WebSense server to show actual domain user information, I must disable Anonymous Access to the default website on TCP port 80. That means that people on the internet cannot access my default website from the internet, but internal users can. Should I move the Proxy clients to port 8080 instead of the default port 80 so I don't have to have authentication for my normal website?

3 replies

by alex

Call my silly, but when you disable anonymous access, that disables it for the PROXY server not individual services. Unless I am wrong changing ports will not accomplish anything if you can't re-enable anon access. And since with Websense you cannot, I think you are up the creek without a paddle. I would say run your webserver on another machine or do away with websense and filter domains manually with proxyserver. If I am wrong about the way proxy authentication works please let me know.

by daniel.quick

Instead of running the server on another machine, I setup a second site and binded the Default website to the internal card and the other website to the external NIC. I put to alieas IP address on the two NICS in the proxy and I used DNS to point web-server to point to port 80 on the internal card 192.168.1.200 to point to alias IP address 192.168.1.201 and binded the second site. The incoming traffic by default is intercepted by 192.168.4.2, the external nics IP.

This discussion is closed to new replies.