We have occasionally had an issue where a user will try to run a java web application such as GoToMeeting and the application will not run even though the user already has the client installed locally. By not run I mean the user cannot connect to an existing meeting or start a new one. We have seen this with other web meeting applications as well and some other java web applications.
We currently use a .pac file to point to one of three geographically placed proxy servers. Based on the IP address of the client, it will use the closest proxy server. All of which are configured identically. We have found that if we let the browser use the .pac file the java applet will not always run, yet when we point the browser directly to the proxy server, via FQDN/IP:port, we have no issues running the java app. Once this has been done, we change the browser back to using the .pac file (Auto detect), close the browser and reopen it, and the java application seems to work correctly from that point on. At least we have not had a case of a user complaining that the app stops working afterwards. We use GP to force the proxy settings to "Automatically detect" and have all the appropriate DHCP/DNS settings in place to allow the browser, IE 6 or 7, to find the .pac/wpad.dat file and resolve the proxy and access the Internet. No issues with normal web browsing at all. Only when using the .pac file to run a java based web application and not every user is affected. We do have exclusions in the .pac file to bypass for local subnets and to use the proxy for certain systems in our DMZ. This also works correctly. Has anyone seen this behavior before? David Edwards ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
