How do I change ISA 2006 Web Proxy Port 8080 to Port 80
Currently, we have about 400 PC that are "proxy" to a Windows 2000 server that also has Microsoft ISA 2000 and Surf Control Internet Security software installed. These 400 PC are "proxy" to the ISA 2000 and Surf Control server through the port 80.
Now, we upgrade the server to Windows 2003 with ISA 2006 and Websense software. I cannot get the ISA 2006 to work with the Web proxy port 80. It will work for port 8080 but I hope that I don't have to change "all 400 PC" to use port 8080.
I tried to change the ISA 2006 HTTP port 8080 of the "Web Proxy" in the "Networks" to port 80 but it did not work.
Would someone please tell me how to configure the ISA 2006 to accept the HTTP port 80 as default.
Any help is highly appreciated.
Teng- SpostatoGreg LindsayMSFTmercoledì 24 giugno 2009 20.28not a NAP related question (From:Network Access Protection)
Tutte le risposte
- Do you have IIS installed on the same box?
If you do change that to a different port i.e. 8080
Then go back to ISA and configure it to use port 80- Proposto come rispostaTh3_0ne venerdì 12 giugno 2009 15.54
- Yes, I did installed IIS on the same box. I followed your instructions by changing the Default IIS Web to port 8080 and the ISA Networks (Intenal) to port 8080 but it still did not work.
Am I need to do something else?
Thanks,
Teng - I'm not sure if it's configured the same for 2006, but using Forefront, I go to Web Access Policy, then it has 'Web Proxy: Enabled (Port:8080)' as a hyperlink,
If I click on that hyperlink, I can enable HTTP or HTTPs proxying on specific ports...
However, you mention needing to change 400 PCs.. why don't you just deploy your configuration change via Group policy, or just use WPAD ? 1. I assume you still have IIS running on Port 8080 on the internal NIC IP . Check whether it is working to connect to you site on port 8080.
This will make sure your website is not using port 80 still.
2. In ISA, do you have auto discovery turned on? If so , by default it will use port 80 and can conflict with your web proxy port
3. Do you have any web publishing rule created in your ISA that use a Web listener to listen on port 80 on the internal NIC as well?
Bala Natarajan [MSFT]| Sr. Support Escalation Engineer | CSS Security -TMG Beta support team | Email: bala.natarajan@microsoft.com | Office 425.704.4626 Bing it on bing.com
