On Tue, Aug 4, 2009 at 20:10, Akos P.<[email protected]> wrote: > > On Aug 4, 3:58 pm, David Anderson <[email protected]> wrote: >> On Tue, Aug 4, 2009 at 15:52, Akos P.<[email protected]> wrote: >> >> > Hi Google stuff! >> >> > It seems that my ISP changed its IP range, and now I have 403 error on >> > code.google.com. I can't see any project. >> >> > Country: Croatia, EU >> > ISP: Iskon >> > IP: 82.132.*.* >> >> > Can you check it out, pls? >> >> Could you also give us the DNS resolution of code.google.com from your >> current IP, as well as a traceroute to code.google.com ? Information >> about where you are routed and how you get to that point is usually >> useful in investigating such issues. Also check to make sure that your >> ISP doesn't do any kind of filtering of client connections >> (transparent proxy, nanny filter or somesch). >> >> It's also implicit in what you said, but I assume you can still access >> google.com and other Google properties? Can you give a couple of >> examples of URLs that are returning 403? >> >> Cheers, >> - Dave > > Hi guys! > > Thx both for your response... > > My ISP has a subcontractor, Carnet. Anyway, the problem is the same. > One system admin told me, that this is an old Iranian IP-range!? > Anyway, here is what you requested: > > *************************************************** Nslookup begin > Server: sx763.gigaset.lan > Address: 192.168.100.1 > > Name: code.l.google.com > Addresses: 74.125.39.139, 74.125.39.101, 74.125.39.102, 74.125.39.113 > 74.125.39.138, 74.125.39.100 > Aliases: code.google.com > *************************************************** Nslookup end > > *************************************************** Tracerout begin > Tracing route to code.l.google.com [74.125.39.113] over a maximum of > 30 hops: > 1 10 ms <1 ms <1 ms router [192.168.100.1] > 2 23 ms 24 ms 23 ms 193.198.190.242 > 3 24 ms 24 ms 24 ms 193.198.190.241 > 4 24 ms 23 ms 23 ms CN-Srce-01-RO.zg.core.CARNet.hr > [193.198.228.21] > 5 33 ms 32 ms 33 ms carnet.rt1.vie.at.geant2.net > [62.40.124.9] > 6 33 ms 32 ms 34 ms > tenGigabitEthernet1-3.ar2.VIE1.gblx.net [64.214.145.145] > 7 45 ms 44 ms 66 ms 74.125.50.189 > 8 47 ms 43 ms 44 ms 209.85.255.172 > 9 57 ms 93 ms 45 ms 209.85.254.114 > 10 53 ms 46 ms 52 ms 209.85.254.134 > 11 47 ms 46 ms 45 ms fx-in-f113.google.com [74.125.39.113] > Trace complete. > *************************************************** Tracerout end > Strange, in the traceroute above, I dont see my public IP address: > 82.132.0.*
That's normal, the device with that IP is (I'm assuming) your router. Your router has 2 interfaces, and the first hop in the traceroute reported the router's IP as seen from you. So, it reported the LAN IP instead of the WAN IP. Nothing to worry about. > *************************************************** > Maybe there is some filtering, not sure. > *************************************************** > Some of the forbidden urls: > http://code.google.com/ > http://code.google.com/p/csvlib/ > http://code.google.com/p/fabrication/ > http://code.google.com/p/twitter-api/ > etc... > *************************************************** > > Just now I've noticed that http://appengine.google.com/ is forbidden > as well (403). Thanks for the details. As Nathan said, we're investigating the issue, but unfortunately it may take some time to resolve. Until it is resolved, I'm afraid the only workaround is as Nathan suggested, to use a proxy service such that you reach Google Code from a different IP range. Sorry for the inconvenience :-( - Dave > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
