Massimo, I notice in this discussion that the dates that many of the failures seem be to occuring on the weekends 7th, 14th and now the 20th. Does the DePaul network team perform maintenance schedules on the weekends?
JohnMc On Jun 20, 11:52 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > Can you try once more and tell me if anything has changed? > > Massimo > > On Jun 20, 10:59 pm, adonm <adon.metca...@gmail.com> wrote: > > > Yeah I'm experiencing the same, but I'm in Australia > > > Through iinet (@home) I get > > > tracepath web2py.com > > 1: 192.168.1.20 (192.168.1.20) 0.214ms > > pmtu 1500 > > 1: my.router (192.168.1.254) 2.734ms > > 1: my.router (192.168.1.254) 4.550ms > > 2: nexthop.wa.ii.net (203.59.14.16) 26.722ms > > 3: gi2-3.per-qv1-bdr2.ii.net (203.215.4.30) 50.684ms > > 4: gi0-15-1-0.syd-stl-core1.ii.net (203.215.20.64) 82.413ms > > asymm 5 > > 5: 202.139.19.37 (202.139.19.37) 82.608ms > > asymm 7 > > 6: 203.208.192.201 (203.208.192.201) 289.825ms > > asymm 9 > > 7: gi1-7.ccr01.lax04.atlas.cogentco.com (154.54.12.221) 289.277ms > > asymm 8 > > 8: te8-3.ccr02.lax01.atlas.cogentco.com (154.54.2.237) 283.725ms > > asymm 9 > > 9: te3-8.ccr02.iah01.atlas.cogentco.com (154.54.5.193) 311.391ms > > asymm 11 > > 10: te3-8.mpd02.iah01.atlas.cogentco.com (154.54.0.246) 313.274ms > > asymm 12 > > 11: te8-1.mpd01.dfw01.atlas.cogentco.com (154.54.7.253) 329.011ms > > asymm 13 > > 12: te4-3.mpd01.mci01.atlas.cogentco.com (154.54.5.158) 352.054ms > > asymm 11 > > 13: no reply > > 14: vl3489.mpd01.ord03.atlas.cogentco.com (154.54.5.18) 341.370ms > > asymm 13 > > 15: DePaul.demarc.cogentco.com (66.250.5.34) 306.553ms > > asymm 13 > > 16: mfc-sac-1s-v844.netequip.depaul.edu (140.192.9.145) 293.154ms > > asymm 14 > > 17: mfc-cst-bs-v841.netequip.depaul.edu (140.192.9.177) 293.692ms > > asymm 15 > > 18: no reply > > 19: no reply > > 20: no reply > > ^C > > > and through globaldial (my company's isp) I get success (atm I'm > > tunneling via work to get to web2py.com, but depauls network guys > > really should take a look?) it does appear to be the firewall at the > > end of the chain > > > tracepath web2py.com > > 1: 5.167.209.203.static.globaldial.com (203.209.167.5) 0.356ms > > pmtu 1500 > > 2: kryten (203.209.167.1) 0.574ms > > pmtu 1460 > > 2: Globaldial-Labyrinthdata.globaldial.com (203.24.54.237) 65.863ms > > 3: ge-0-0-5.core-pop1-per.globaldial.com (203.24.54.33) 36.294ms > > 4: FastEthernet-12-1-0.GW1.PER1.ALTER.NET (203.166.42.181) 62.458ms > > 5: 421.AT-6-0-0.XL2.PER1.ALTER.NET (210.80.32.113) 63.814ms > > asymm 6 > > 6: 0.so-1-1-1.XT4.SYD2.ALTER.NET (210.80.33.29) 118.895ms > > asymm 7 > > 7: 0.so-4-1-0.IR2.SAC2.Alter.Net (210.80.48.93) 258.628ms > > asymm 8 > > 8: 0.so-2-0-0.IL2.SAC1.ALTER.NET (152.63.48.41) 263.628ms > > asymm 9 > > 9: 0.so-5-2-0.XT2.SCL2.ALTER.NET (152.63.1.69) 277.118ms > > asymm 10 > > 10: po2-1.core01.sjc03.atlas.cogentco.com (154.54.13.113) 261.189ms > > asymm 11 > > 11: te2-4.mpd01.sjc03.atlas.cogentco.com (154.54.6.85) 256.958ms > > asymm 15 > > 12: te2-2.mpd01.sjc01.atlas.cogentco.com (66.28.4.73) 276.928ms > > asymm 13 > > 13: te2-1.mpd01.sfo01.atlas.cogentco.com (154.54.1.25) 293.688ms > > asymm 14 > > 14: te2-1.mpd01.mci01.atlas.cogentco.com (154.54.6.37) 322.677ms > > 15: no reply > > 16: vl3489.mpd01.ord03.atlas.cogentco.com (154.54.5.18) 377.949ms > > asymm 12 > > 17: DePaul.demarc.cogentco.com (66.250.5.34) 308.701ms > > asymm 14 > > 18: mfc-sac-1s-v844.netequip.depaul.edu (140.192.9.145) 308.597ms > > asymm 14 > > 19: mfc-cst-bs-v841.netequip.depaul.edu (140.192.9.177) 327.921ms > > asymm 15 > > 20: 140.192.37.194 (140.192.37.194) 322.006ms > > reached > > Resume: pmtu 1460 hops 20 back 49 > > > For reference both these IP's are in the 203 block > > home (doesn't work): 203.59.99.179 > > companyisp (does work): 203.209.167.0/24 (we own the subnet) > > > On Jun 20, 10:43 pm, Jason Brower <encomp...@gmail.com> wrote: > > > > There was some mention of a firewall. Sadly, I think we are on that > > > list. I don't think it's punishment though. :P > > > > On Sat, 2009-06-20 at 08:30 -0500, Douglas Horst wrote: > > > > It's not working for me either from home but it is from work. Both > > > > are in the Chicago area. Trace route from home still dies at > > > > mfc-cst-bs-v841.netequip.depaul.edu. > > > > > On Thu, Jun 18, 2009 at 7:14 PM, Yarko Tymciurak <yark...@gmail.com> > > > > wrote: > > > > look athttp://en.wikipedia.org/wiki/Tracerouteforlistsof > > > > tools; if going to the ip address directly doesn't work for > > > > you (nslookupwww.web2py.com), you can try to filter just http > > > > messages with wireshark to see what messages are going back / > > > > forth. > > > > > I'm not having trouble - but I'm in the Chicago area (and so > > > > isweb2py.com); I did note that the first access toweb2py, > > > > tracepath showed a _really_ long delay at what looks like the > > > > gateway into DePaul... > > > > > On Thu, Jun 18, 2009 at 6:37 PM, Eddie Eyles > > > > <ho...@heddonsgate.co.uk> wrote: > > > > > I'm getting a gateway timeout again, trying to open > > > > web2py.com. This > > > > after several days of no problems at all. > > > > Surprisingly, traceroute > > > > shows all nodes responding, all the way through to the > > > > web2py.com > > > > host. Does anyone know how to diagnose this kind of > > > > problem? > > > > > Eddie > > > > > On Jun 14, 10:04 pm, mdipierro > > > > <mdipie...@cs.depaul.edu> wrote: > > > > > I do not know. It works now. > > > > > > On Jun 14, 11:46 am, Jesse Bever > > > > <jesse.be...@gmail.com> wrote: > > > > > > > I still can't accessweb2py.com :(. The trace > > > > still dies at > > > > > > mfc-cst-bs-v841.netequip.depaul.edu. Is there some > > > > firewall that is > > > > > > filtering out certain ip ranges? I can access it > > > > from work but not from > > > > > > home. > > > > > > > On Mon, Jun 8, 2009 at 8:14 AM, mdipierro > > > > <mdipie...@cs.depaul.edu> wrote: > > > > > > > > I was having problems from home. At the office > > > > everything looks fine > > > > > > > but I restarted the server anyway. > > > > > > > > Does it work for you know? If not, any hint > > > > about the problem? > > > > > > > Could it have been temporary DNS issue? > > > > > > > > The log shows people have been accessing the > > > > server all along. > > > > > > > > Massimo > > > > > > > > On Jun 7, 11:51 pm, Yarko Tymciurak > > > > <yark...@gmail.com> wrote: > > > > > > > > interesting.... nslookup shows > > > > this:http://140.192.37.194/-andthat > > > > > > > > returns too... > > > > > > > > > Is this some DNS thing? You should be able to > > > > get to the address (if it > > > > > > > > is)... > > > > > > > > > I can - but i have been able to get to it by > > > > name all afternoon / > > > > > > > evening... > > > > > > > > > On Sun, Jun 7, 2009 at 9:56 PM, Jesse Bever > > > > <jesse.be...@gmail.com> > > > > > > > wrote: > > > > > > > > > I can't access it it either I thought it was > > > > just me > > > > > > > > > > On Sun, Jun 7, 2009 at 1:30 PM, Hans Donner > > > > <hans.don...@pobox.com> > > > > > > > wrote: > > > > > > > > > >> for me it works fine... > > > > > > > > > >> On Sun, Jun 7, 2009 at 10:27 PM, > > > > mdipierro<mdipie...@cs.depaul.edu> > > > > > > > > >> wrote: > > > > > > > > > >> > Now I cannot accessweb2py.com either. I > > > > cannot look into this > > > > > > > until > > > > > > > > >> > tomorrow morning. > > > > > > > > > >> > Massimo > > > > > > > > > >> > On Jun 7, 3:15 pm, "mr.freeze" > > > > <nfre...@gmail.com> wrote: > > > > > > > > >> >> Yes. > > > > > > > > > >> >> On Jun 7, 3:13 pm, mdipierro > > > > <mdipie...@cs.depaul.edu> wrote: > > > > > > > > > >> >> > can you accesswww.cdm.depaul.edu? > > > > > > > > > >> >> > On Jun 7, 2:47 pm, "mr.freeze" > > > > <nfre...@gmail.com> wrote: > > > > > > > > > >> >> > > Strange...a route trace dies at > > > > > > > > >> mfc-cst-bs-v841.netequip.depaul.edu > > > > > > > > >> >> > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
