Community
Participate
Working Groups
Build Identifier: Version: 3.6.1 Build id: M20100909-0800 Just downloaded new eclipse Java package, tried to add rest of the software I need. updates from the default Helios site, the js-test-driver, WTP, subeclipse, and PDT dev tools sites all report the same error when trying to sync: "Unable to connect to repository" and the error details say "request timed out." So the new version is dead in the water. Went back to my last version of eclipse on the same box, same network, same everything, and it can reach the update sites just fine. Working version: Version: 3.4.2 Build id: M20090211-1700 Reproducible: Always Steps to Reproduce: 1. download eclipse v. 3.6.1 2. select Help > Install New Software 3. Pick one of the default sites that came pre-installed with eclipse in the drop-down at the top of the box. Progress window says "Fetching children of Helios" (or whatever update site you're trying). It grinds for a few minutes, gets to 50% progress, then pops the error dialog. Repeat with any other update site you can think of, watch them all fail.
Are you on an enterprise network that has proxies?
Nope, I'm home for Thanksgiving break and my home network has no firewall. Note that Ganymede can get to the update sites just fine, but this is preventing me from upgrading to Helios. Also, I don't think the "Fetching children of ..." is the first step in the update process, is it? Does Eclipse do a network access before that? Thanks, - John
OK - I found the issue - this is on Windows XP, and the IE network configuration had a hard proxy setting that was throwing Helios off. The weird part is that this didn't seem to affect Ganymede or most of my other apps. So I'm back in business, and you guys can close out as no bug, but I would still recommend seeing if you can make Helios updates withstand mis-configed IE network setup.
(In reply to comment #3) > OK - I found the issue - this is on Windows XP, and the IE network > configuration had a hard proxy setting that was throwing Helios off. The weird > part is that this didn't seem to affect Ganymede or most of my other apps. So > I'm back in business, and you guys can close out as no bug, ok > but I would still > recommend seeing if you can make Helios updates withstand mis-configed IE > network setup. Any other Microsoft issues you would like us to fix while we are at it :)
