Hello folks, I would like to have an echoServer setup that will work for nearly all kinds of proxy servers in any company. During my first tests within some enterprise environments I got some errors I would like to tell you about. I also attached (anonymized) debugging information to this mail.
First I describe my general association for a typical configuration within an enterprise environment: - all network traffic between network segments is controlled by a firewall - no direct traffic between internal and external networks, no open ports - all traffic between internal and external networks over application layer - browsers (esp. IE) use an http proxy and have automatic configuration via proxy.pac/wpad only or a combination of proxy.pac/wpad and autoconf.ins. Settings for path to proxy.pac or autoconf.ins are hardcoded or will be detected via wpad settings with DHCP and/or DNS - proxy server(s) need browser-integrated user authentication via NTLM and often work not well with manual basic authentication or do even not allow to do so. During my tests of EchoVNC viewer I noticed the following: 1. It does not recognize the proxy with automatic proxy configuration through an autoconf.ins script configured staticly in IE. FAILED_demo2_autoconf-ins_and_proxypac.log shows the error log for this case, autoconf.ins.txt shows an example of a real used autoconf file für IE, which implies the use of the file proxy.pac.txt through loading it from a webserver. the autoconf file is being reloaded from a webserver through a link in the autoconf file itself. -> very bad for InstantVNC :-( 2. If I enter the proxy manually in EchoVNC viewer without username/password there is no functional NTLM. IN logfile FAILED_demo2_staticproxy_withoutauth.log you see that a NetApp proxy is used and it demands authentication via NTLM. 3. If I also enter my login data for the proxy server it takes a loooong time for the echoWare to connect to it (see file SUCCESS_demo2_staticproxy_withauth.log). BUT: I can not safely establish a connection to a VNC server, very often I click on an entry and get a timeout with a failure that the partner has not been found. After a few tries it runs with a Windows VNC Server to connect to. Unfortunately I cannot connect to my Vine Server at Mac OS X 10.5 (yes I'm using the current beta). I could not yet verify if the direct use of a proxy.pac auto configuration without the use of an autoconf.ins file works as I need to test it in another customers environment within the next few days. I also did not yet verify it the automatic detection from IE for the path/address of the proxy.pac through DHCP and/or DNS works. Maybe you could give me a few suggestions, I'm willing to give you all nessessary information to improve EchoVNC viewer. I really would like to use this product (and buy the server :-)) but it should work as easy as possible. Teamviewer for example works perfectly within my environments (detects every proxy and uses seamless NTLM single-sign-on for them). Regards from Munich Julian
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Echovnc-users mailing list Echovnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/echovnc-users
