What is your actual network configuration? Internet <-> HW FW <-> SGD <-> ISA Proxy <-> Internal Client
Or something else? Cheers Ken -----Original Message----- From: Robert Jackson [mailto:[email protected]] Sent: Tuesday, 9 February 2010 4:13 PM To: NT System Admin Issues Subject: SSGD ISA 2006 Issues Does anyone know if ISA 2006 configuration changes are specifically required in order to get Sun's Secure Global Desktop operational? My scenario is this: We have a SGD server on our local LAN. A laptop on our local LAN can access SGD no problem using an internal ip address in the browser - as you would expect. The same laptop can access SGD with a public address in the browser (and going through an ISA 2006 server used as a proxy server). Again, the same laptop, on the local LAN, can by pass the ISA 2006 proxy server and using the public ip address access the SGD no problem. My issues occur when the laptop (or a different computer) not on the local LAN tries to access the SGD server using the public ip address. I keep getting the error: Cannot connect to the server <servername>:443 I can telnet on port 443 through the public ip address, so at least I know that traffic can pass through our front internet facing hardware firewall to the SGD server. Anyone have any ideas? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
