Hi,
is there any recommendation on what to do, when you want to change the Default Websites port, if it is already required by another application on the server?
Hi,
is there any recommendation on what to do, when you want to change the Default Websites port, if it is already required by another application on the server?
We had the same problem with IIS 6 on a server using Citrix that had the default port 80 reserved.
The easiest way we found to resolve this issue is to:
Now, to access your SBC, you just need to add the port to the url,like http://servername.domain:8080/avast/service.aspx
Hope this works for you.
Hi Pascal,
sorry for the late reply. I tried it today. Checking which ports are in use, changing the Default Website bindings to 8080, stopping and starting the site. However same effect…the Administration Console didn’t open. As soon as I switched back to the default 80 port, it was reachable again.
Did you perform any additional steps?
bump
Maybe also Lukas could jump in and tell if there are any other things which have to be checked?
Hello,
could you please tell me the actual URL you are using to access the Administration Console?
Hi,
URL is http://:82/Avast/Default.aspx (also tried with 8080 after changing the port of the Default Website in IIS)
OK, please read http://forum.avast.com/index.php?topic=82941.msg680947#msg680947 for the difference between http://:82/Avast/Default.aspx and http://:82/Avast/Service.aspx.
Now to your actual problem, there is a known bug related to custom port (for Default website selection). But there is also a workaround:
Now you should be able to access the secure http://:82/Avast/ or http://:82/Avast/Default.aspx normally. Please let me know if described steps solved your problem.
Works! Thank you
You are welcome