Hi again, Now I verified this is the case. With the proxy exception too* I can not install Gears, removing the exception install works fine. During the installation there is no visible reference to any server but dl.google.com. Today when I ping gears.google.com or dl.google.com there is no reference in the reply to tools.i.google.com. But still the installation fails if the proxy exception 'too*' is active. We have a policy decision of having 'too*' as a proxy exception, since we have a number of tools* servers internally. It is not easy to change this, nor is it easy to have salesmen around the world with non standardized hard and software to temporarily change proxy rules to install Gears. Can anyone spread some light the Gears install process?
On 30 Mar, 13:34, Lasse <[email protected]> wrote: > Hi again, > the network guys (at my office) checked my install problems for me. > They say it is the google servername that is the problem > "tools.l.google.com". when we ping "gears.google.com" this > "tools.l.google.com" responds. Now the company I work for "Atlas Copco > Tools" have a proxy exeption "too*". Can that exeption and the > "tools.l.google.com" servername intercept Gears install? > I really really appreciate an answer on this. > > On 19 Mar, 16:08, Lasse <[email protected]> wrote: > > > Hi all, > > Last summer we built a Gears application 'Torquearm Wizard' for our > > sales force and we posted progress > > athttp://groups.google.com/group/gears-users/browse_thread/thread/55659... > > > The use of the application is severely hampered by install problems. > > It looks like most of the problems comes from proxies in our networks. > > It is almost impossible to track down and fix each and every failure > > since the presumptive users are spread all over the world in different > > networks. > > What I need is a standalone Gears installer which I can distribute on > > a stick or inside our firewall.
