Discussion Locked

Publishing A Site using ISA Server

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are currently publishing a website to the internet thru our ISA (microsoft's new firewall and proxy software) server. After a bit of configurations, we finally published the homepage (default). The problem is when we are going to log-in (now using SSL (HTTPS)) to the site, error occurs. I've already opened port 80(http) and 443(https), still i got "page cannot be displayed" errors). How to I fix this? Does it need certficates for ssl tunneling? Help me please. Please include procedures. Thanks.

7 replies

by vicmen23

In our local intranet, when you log-on to the server, a message will prompt you to "allow these certificates" or something like that, we usually choose ok, then we can get through, how do i do that in the intranet? How do i export certificates from an IBM Websphere Server to an ISA server running on win2k Adv. Server.

by buckle

This sounds like access is only being allowed from your local net. Have you checked the access permissions for requesting addresses on the server/proxy.
You might also check your routers permissions etc.
This is just a guess of course, could you please give us the text of your error messages this is not the problem.

by rkelly

To publish a site through ISA Server you should install ISA in either Cache or Integrated mode. Once this is done follow the console to find Web Publishing and follow the wizard - it genuinely is as simple as that. The software will enable an inbound web connection to which ever server to publish - there is a service listener on Port 80 that will listen for HTTP traffic on port 80.

If you want to publish a secure site just enure that you install the SSL Certificate on the ISA Server, you canthen either use SSL Tunneling or HTTP conversion for the traffic passing through ISA.

You do NOT need to open any ports on the ISA server UNLESS you are publishing other types of service. The HTTP Listener is part of the Web Proxy Service and does NOT require ANY firewall configuration.

This discussion is closed to new replies.