I have spent a mere day using and abusing goglobal because it seems to be the only thing that promises to publish client/server applications into a web page making it easy for me to access those non-web-enabled applications via an SSL web proxy connection over the Internet - in my case using a Cisco vpn 3000.

Looks promising, but when I try to connect via the Cisco I get the error "The application publishing service is not running on <public cisco ip address>. Contact your system adminstrator".

The system is somehow thinking the server publishing the applications is coming from the Cisco device rather that the trusted network's Windows 2000 server - so is not letting it strut its stuff.

Must be a simple solution, so I wonder if anyone can help. Thanks for your time.

The error "The application publishing service is not running..." is indicative of a network path issue. It usually means the GO-Global client cannot reach the server because a router or firewall is blocking access via port 491.

In this case, the problem may actually be that the webpage is referencing a local IP rather than a public IP. Edit the HTML page of the ActiveX control or plug-in and reflect an IP address that can be pinged and accessed by the remote client.

The other thought is that you do not have port forwarding set up correctly. In other words, when the remote client hits port 491 on the router, traffic is not being directed on to the GO-Global server.

-Erik

Thanks for the reply but I still do not have this working yet. Let me explain the network: from the remote home computer we first encouter our firewall on a public ip address - this address in turn is mapped to the DMZ address of the Cisco vpn 3000. The vpn 3000 is then allowed to connect to anything on our private lan... and this includes the goglobal server. There are no restrictions in place between the firewall and the vpn 3000, or from the vpn 3000 to the private lan.

Also, can you explain a little more fully how to edit the html file (if i still need to do that). Do i need to edit it to include the ip address of the public address?

I would try the following:

First, forget about the HTML settings for now. Use the GO-Global native Windows client to see if you can establish a connection with an external IP address to the router -> server. If you can't, you have TCP port 491 blocked somewhere on the network.

If you are successful, edit the web client HTML page (assuming you are using the ActiveX control here) and use the same IP address in the "host" parameter field.

Code:

ActiveX Control <OBJECT ID="Control1" WIDTH=0 HEIGHT=0 CLASSID="CLSID:76850F2A-FCAA-454F-82D3-BD46CB186EF5" CODEBASE="ggw-activex.cab#Version=2,0,0,0" > <PARAM NAME="user" VALUE="Jane"> <PARAM NAME="password" VALUE="Doe1"> <PARAM NAME="host" VALUE="server1"> <PARAM NAME="application" VALUE="Notepad"> <PARAM NAME="args" VALUE="C:\Readme.txt "> <PARAM NAME="isembeddedwin" VALUE="false"> <PARAM NAME="compression" VALUE="true"> </OBJECT>

You can find detailed information on how to do this on page 28-30 in the Admin guide -Erik

I installed the windows native client and noticed it wanted and IP address of the goglobal server. This indicated to me that it wanted direct access to the address. So I directly mapped the public address to the private address only opening port 491.

I mistakingly thought that because goglobal published applications as web pages that I could simply use our Cisco vpn 3000 to SSL to those pages using port 443 (https) like we do for Outlook Web Access. OWA is a web enabled application and goglobal advertise themselve as web enabling applications, so I thought the same access method could be applied - but no.

I really wanted access via our SSL device using standard web protocols in this way to govern security via the Cisco appliance.. but it seems, even though your system web enable applications, its not the same sort of web enabling!

I believe it is possible to change the port go global "pushes" to to 443. This might solve your issue.