New issue 17 by abitt...@gmail.com: googleupdate.exe using old long-ago
removed proxy address for connection first
http://code.google.com/p/omaha/issues/detail?id=17
please see my other original bugreport over at the chromium folks, as the
bug
is mainly visible over there from within google chrome.
never the less the component that behaves this way and is having the bug is
the googleupdate.exe process (win32, winxp pro sp3, latest patches feb2010,
latest chrome 4.x release from february 2010)
chrome bugreport:
http://code.google.com/p/chromium/issues/detail?id=35527
so maybe its you guys who would be in charge and fixing this bug.
thanks and regards.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
i did some little more debugging, i have some apps from the googlepack
already
installed on this winxp sp3 machine (win32), so i went for pack.google.com
and
selected googletalk there.
the google pack installer (this time googleupdater.exe (notice the r at the
end))
also tried for my long-ago removed proxy address: 192.168.10.9:8080 for
quite a
while, eventually managed to fetch the googletalk package, installed it and
googletalk.exe came up.
i tried to log-in with my gmail credentials there, and it once again took a
long
while, as googletalk.exe process as well tries first to go for the old
proxy setting
192.168.10.9:8080, which is nowhere listed on this system any more
(apparently still
is, otherwise the google tools wouldnt always try using it :(((( ) so
anyway, after a
while googletalk.exe was able to log-in properly.
so where the heck is this proxy address stored.
surfing the web with chrome, firefox and internetexplorer all works fine,
only these
fundamental googleinstallers, googleupdate/googleupdater and the
google-network-layer
tools seem to still be using the old proxy setting from somewhere. i am
going nuts
with this stuff......
i know maybe i could simply remove all the google stuff from this machine
and
reinstall the google tools but i really want to get this bug sorted out and
solved
and get behind the reason for this bug and track the source of the bug down.
i also have had googleearth.exe installed before and that one app is
immediately
going for the google-datacenter servers immediately via direct connection to
1e100.net domain or something, so not trying to use some old outdate proxy
address in
contrast to the many other affected google apps.
FYI ... Pls try this if you are facing this problem:
THe GoogleUpdate exe uses proxy settings from WinHTTP.
http://msdn.microsoft.com/en-us/library/windows/desktop/ms761351(v=vs.85).aspx