I'm trying to use a server publishing rule to access an internal server which is not located on the ISA server itself, but that requires an ActiveX control to present an important machine display panel. From within our network and by browsing to the DHCP-reserved local address, the ActiveX control loads fine in IE. And, using the new server publishing rule, I can also browse to the designated external IP address and get everything from this server's web page (text, headers, tables, etc), but not the ActiveX control graphic. It would seem to be blocked by ISA or the gateway. I've studied the firewall logs and can't find where the ActiveX control is denied. Thoughts? Thanks all in advance for helping.
From: Taylorville, IL
There is a difference between allowing the activex control to install -vs- having it actually work after it is installed.
Installing the control is just over http,...there is nothing about ISA that should bother that.
However after it installs and executes in the user's browser it has to actually form a communication session to the server it deals with for the Panel Display. It would be just like if it was a regular user Application installed from a Setup.exe and run from the Start Menu. So you have to determine the nature of that communication and then Publish the server that it connects to. This would be a completely separate Publishing aside from the Web Site itself. The only thing the web site is really doing is acting as a delivery mechanism for the ActiveX Control, after that the web site is not part of the equation. Then the web browser is just simply providing the Operating "enviroment" for the Control to run in.
That is the best analysis I can come up with without being personally involved with it.
Thanks for your input. Just an hour ago I got tech info from the control manufacturer about which ports need to be opened to permit the activex viewer to pass thru ISA (which was not documented in their manual!). Got it working now. I appreciate your reply.