On Sat, Sep 12, 2009 at 21:36, [email protected] <[email protected]> wrote: > > I'm using Windows (XP) and TortoiseSVN. > No, I can't access other googlecode SVNs, but I CAN access them (even > securely) through Firefox, so I think it may be a problem with my SVN > client...
Okay, that sounds like TortoiseSVN is configured with a proxy that doesn't exist. When it can't connect to the proxy, it reports the confusing "connection failed" error, when what it actually means is "connection failed *to the proxy*". Unfortunately I don't have a Windows machine or virtual machine handy to check what the TortoiseSVN configuration stuff looks like, but try to look through the configuration for TortoiseSVN and see if there are any proxies configured anywhere. If there are, remove them and try again. - Dave > > On Sep 12, 3:24 pm, David Anderson <[email protected]> wrote: >> Yup, that works. So, we've established that a traceroute can reach >> Google Code, here's the next things to check: >> - Are you behind an HTTP proxy? If you are, maybe that proxy has >> connectivity problems. From the traceroute and time of week though, >> this looks like a residential internet connection, where a proxy is >> less likely than in a company... >> - Is your computer configured with any kind of HTTP proxy? Depending >> on the operating system, this can live in various places. What OS and >> Subversion client are you using (eg. Linux and commandline client, >> Windows and TortoiseSVN...) ? >> - Are you able to connect to other *.googlecode.com addresses? In >> particular, are you able to check out other projects that you own >> (where you have permission to access over https) ? >> >> I've just done another quick check, and as far as I can tell, >> everything is serving happily on our end. That doesn't mean it's >> necessarily something wrong on your end, but the above are the usual >> suspects with connection problems (especially having a proxy >> configured when none exists), so we should take a look at those first. >> >> - Dave >> >> On Sat, Sep 12, 2009 at 21:13, [email protected] >> >> <[email protected]> wrote: >> >> > Well, the tracert seems to make it. >> >> > Tracing route to googlecode.l.google.com [74.125.91.82] >> > over a maximum of 30 hops: >> >> > 1 645 ms 29 ms 30 ms 192.168.1.1 >> > 2 * * * Request timed out. >> > 3 14 ms 30 ms 30 ms 68.85.152.165 >> > 4 29 ms 30 ms 30 ms 68.86.210.213 >> > 5 17 ms 32 ms 11 ms po-90- >> > ur02.hersheymills.pa.panjde.comcast.net [6 >> > 8.86.209.137] >> > 6 30 ms 30 ms 30 ms >> > pos-0-11-0-0.ar01.plainfield.nj.panjde.comcast.n >> > et [68.86.153.98] >> > 7 30 ms 30 ms 15 ms pos-0-7-0-0- >> > cr01.newyork.ny.ibone.comcast.net [6 >> > 8.86.90.29] >> > 8 30 ms 30 ms 15 ms xe-10-2-0.edge1.NewYork2.Level3.net >> > [4.78.169.49 >> > ] >> > 9 15 ms 14 ms 20 ms vlan51.ebr1.NewYork2.Level3.net >> > [4.69.138.222] >> > 10 46 ms 30 ms 19 ms ae-3-3.ebr2.Washington1.Level3.net >> > [4.69.132.89] >> >> > 11 30 ms 29 ms 30 ms ae-82-82.csw3.Washington1.Level3.net >> > [4.69.134.1 >> > 54] >> > 12 17 ms 35 ms 39 ms ae-3-89.edge1.Washington1.Level3.net >> > [4.68.17.14 >> > 4] >> > 13 31 ms 30 ms 30 ms GOOGLE- >> > INC.edge1.Washington1.Level3.net [4.79.22 >> > 8.38] >> > 14 46 ms 30 ms 26 ms 209.85.240.136 >> > 15 37 ms 37 ms 38 ms 209.85.248.73 >> > 16 62 ms 34 ms 58 ms 209.85.254.235 >> > 17 77 ms 62 ms 56 ms 209.85.240.25 >> > 18 61 ms 46 ms 61 ms qy-in-f82.google.com [74.125.91.82] >> >> > Trace complete. >> >> > But I'm not sure. I've never actually read one before. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
