Difficulties accessing Forum

[ParrLeyne]

I haven't been able to connect from home during any time of day...

While can't say for absolute certainty (since I'm not home most of the time -- I work at a separate office) but my home PC is also unable to connect, regardless of time of day.

I have tried at a variety of time on weekdays (mornings between 9:30a-11:00a and 9:00p-1:00a) [all times Eastern US/Canada] and weekends (10:00a-1:00a).

[codysluder]

I haven't been able to connect from home during any time of day...

While can't say for absolute certainty (since I'm not home most of the time -- I work at a separate office) but my home PC is also unable to connect, regardless of time of day.

I have tried at a variety of time on weekdays (mornings between 9:30a-11:00a and 9:00p-1:00a) [all times Eastern US/Canada] and weekends (10:00a-1:00a).

Post the tracert information from that PC.

[ParrLeyne]

Post the tracert information from that PC.

The tracert for the last occurance was the same as the one I posted, below, on Sat Jan 24, 2009 12:39 am .

[codysluder]

There are clearly some problems somewhere. I expect that it will eventually be singlehop or one of ISPs that they connect to.

I'm not experiencing any problems, but I just got two entirely different paths.

Code: Select all

  6    15 ms    16 ms    16 ms  ae-73-73.ebr3.LosAngeles1.Level3.net [4.69.137.37]
  7    24 ms    31 ms    19 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
  8    28 ms    20 ms    30 ms  ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]
  9    21 ms    31 ms    34 ms  ae-62-62.ebr2.SanJose1.Level3.net [4.69.134.209]
 10    46 ms    54 ms    52 ms  ae-3.ebr1.Denver1.Level3.net [4.69.132.58]
 11    45 ms    49 ms    52 ms  ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38]
 12    74 ms    70 ms    70 ms  ae-3.ebr1.Chicago2.Level3.net [4.69.132.62]
 13    71 ms    72 ms    70 ms  ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
 14    69 ms    71 ms    70 ms  ae-13-51.car3.Chicago1.Level3.net [4.68.101.7]
 15    67 ms    67 ms    66 ms  263.xe-0-3-0.cr2.ord1.us.scnet.net [4.71.100.38]
 16    66 ms    66 ms    66 ms  v21.ar1.ord1.us.scnet.net [216.246.95.243]
 17    68 ms    67 ms    67 ms  as32475.1514.tge4-4.ar1.ord1.us.scnet.net [75.102.19.131]
 18    67 ms    67 ms     *     216.104.35.221
 19    67 ms    68 ms    67 ms  dr02.ord02.singlehop.net [67.212.191.186]
 20    68 ms    66 ms    66 ms  ns1.m202.sgded.com [99.198.108.202]

Trace complete.

Code: Select all

  6    12 ms    12 ms    12 ms  te7-1.mpd01.lax01.atlas.cogentco.com [154.54.0.53]
  7    23 ms    23 ms    22 ms  te7-3.mpd01.sjc01.atlas.cogentco.com [154.54.2.130]
  8    25 ms    24 ms    24 ms  te9-3.mpd01.sfo01.atlas.cogentco.com [154.54.2.53]
  9    27 ms    28 ms    27 ms  te4-1.ccr01.smf01.atlas.cogentco.com [154.54.24.114]
 10    42 ms    42 ms    42 ms  te4-3.ccr01.sea01.atlas.cogentco.com [154.54.3.90]
 11    42 ms    44 ms    45 ms  te4-2.ccr01.sea02.atlas.cogentco.com [154.54.1.198]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22  ^C

[ParrLeyne]

Here is my tracert from tonight, still not able to connect from Home.

Code: Select all

  2     *        6 ms     7 ms  vl-201.gw03.ym.phub.net.cable.rogers.com [66.185.90.17]
  3     7 ms     8 ms     7 ms  te-15-1-0.gw01.ym.phub.net.cable.rogers.com [24.153.5.37]
  4     6 ms     7 ms     7 ms  ge-5-3-3.gw02.bloor.phub.net.cable.rogers.com [64.71.240.141]
  5    48 ms    49 ms    50 ms  pos-3-0.igw01.chfdrl.phub.net.cable.rogers.com [66.185.81.1]
  6    48 ms    48 ms    48 ms  so-0-2-2.mpr1.ord2.us.above.net [64.124.11.25]
  7    50 ms    48 ms    47 ms  xe-1-1-0.er1.ord2.us.above.net [64.125.26.186]
  8    32 ms    33 ms    33 ms  64.124.200.142
  9    35 ms    35 ms    35 ms  216.104.35.221
 10    33 ms    33 ms    34 ms  dr02.ord02.singlehop.net [67.212.191.186]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.

[PeterT]

The thing I find SO frustrating in all this is that there appears to be no real interest by anyone in solving this issue. Sure this is a "free" service many of us are using, but we ARE using it in an attempt to help out the scientific and research worlds.

I for one would be far more likely to visit and ask questions if I did not have to head through a proxy server each and every time to access these forums.

Do we have to wait until maybe other parts of the Folding infrastructure go in accessible to people before a solution is found..

For instance, has someone who has access to the server(s) where these forums run ever tried to traceroute back to one of (for instance) the Rogers devices?

Have ISnghleHop emplyees even tried to that from some of their infrastructure servers?

Have they even tried to cotnact Rogers and any other ISP where clients have reported issues to work on diagnosing what is going on.

I've worked in the corporate world and in the service industry, and it's safe tp say that in either of those areas, the network administtrators would have been working on traclking down and solving this problem long before this.

Peter

[bruce]

One important reason that it hasn't been fixed is that it works fine most of the time:

Code: Select all

 10    48 ms    49 ms    52 ms  ae-3.ebr1.Denver1.Level3.net [4.69.132.58]
 11    57 ms    53 ms    51 ms  ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38]
 12    70 ms    69 ms    72 ms  ae-3.ebr1.Chicago2.Level3.net [4.69.132.62]
 13    74 ms    72 ms    69 ms  ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
 14    71 ms    70 ms    70 ms  ae-13-51.car3.Chicago1.Level3.net [4.68.101.7]
 15   104 ms    66 ms    67 ms  263.xe-0-3-0.cr2.ord1.us.scnet.net [4.71.100.38]
 16    73 ms    72 ms    71 ms  v21.ar1.ord1.us.scnet.net [216.246.95.243]
 17    67 ms    66 ms    66 ms  as32475.1514.tge4-4.ar1.ord1.us.scnet.net [75.102.19.131]
 18    71 ms    67 ms    68 ms  216.104.35.221
 19    67 ms    68 ms    80 ms  dr02.ord02.singlehop.net [67.212.191.186]
 20    71 ms    73 ms    68 ms  ns1.m202.sgded.com [99.198.108.202]

[PeterT]

Bruce I disagree.

If you look back through this thread I think you will see that MANY Rogers cable customers in Canada arenot able to access this forum directly AT ALL!

[ParrLeyne]

If you look back through this thread I think you will see that MANY Rogers cable customers in Canada are not able to access this forum directly AT ALL!

Peter,

I have reviewed the postings and there are about postings from 9 different people with connection problems, only 2 of which are for Rogers cable, so the problem is more generalized than you state.

I will open a support case with Rogers, when I get home tonight.

And the others in this list should also open cases with their ISPs. Peter is correct, the only way that this will get resolved, is for people to complain to the ISPs.

The forum hosts, though, should be exerting the greatest pressure since all of the cases have the forum ISP in the mix and they are the ones which have the best "quality of service" argument to offer an ISP. {Complaining to Rogers about not being able to connect to a small portion of the net, is a valid but not a compelling problem. The Forum complaining to their ISP that at least 9 people with 6 diverse ISPs are not able to connect, is a very compelling problem.}

[bruce]

Bruce I disagree.

If you look back through this thread I think you will see that MANY Rogers cable customers in Canada arenot able to access this forum directly AT ALL!

I was speaking from my own perspective, not necessarily from yours. (I'm a FAH donor from my own home, too.) I can get through to foldingforum.org almost all of the time, but at certain times, I cannot, and my tracert looks just like some of those posted above -- ending at one of the routers in the singlehop domain.

I don't have enough information to be able to tell if my results depend on the path my packets take through the backbone, like codysluder has demonstrated.

Notifying your ISP will certainly help, particularly if you have a hard failure. We have opened tickets with the hosting company and there may or may not have been some slight improvements, but the problem has not been solved. If they start getting calls from rogers.net or other ISPs, the techs will be able to coordinate with each other and be more effective than anyone can from a single point. The seattle failure posted above (cogentco.com) is a good example where more information is required, particularly if the routers don't find an alternate path quickly.

[PeterT]

I have tried talkign to Rogers and their first line support say no issues at their end. Trying to get through them to anyone who has the knowledge to work with someone to resolve this is impossible. I think in fact I did post earlier my reply from Rogers.

For what it's worth, my routing info. HAS been posted here, but here it is again

Code: Select all

Tracing route to foldingforum.org [99.198.108.202]
over a maximum of 30 hops:

  1     1 ms     1 ms    13 ms  ROUTER.localnet [192.168.2.1]
  2     *        *        *     Request timed out.
  3    10 ms     9 ms     7 ms  69.63.243.29
  4     7 ms     8 ms     7 ms  69.63.248.205
  5    48 ms    49 ms    49 ms  pos-3-0.igw01.chfdrl.phub.net.cable.rogers.com [66.185.81.1]
  6    50 ms    49 ms    51 ms  so-0-2-2.mpr1.ord2.us.above.net [64.124.11.25]
  7    49 ms    49 ms    50 ms  xe-1-1-0.er1.ord2.us.above.net [64.125.26.186]
  8    36 ms    36 ms    37 ms  64.124.200.142
  9    35 ms    34 ms    34 ms  216.104.35.221
 10    35 ms    35 ms    35 ms  dr02.ord02.singlehop.net [67.212.191.186]
 11     *        *        *     Request timed out.

My IP is 99.245.56.177

[uncle_fungus]

Well, with help from PeterT, this is now resolved. The problem was a faulty routing table which caused anyone with an IP address in the 99.0.0.0 range not be able to access the server, and vice-versa.

[skinnykid63]

I can confirm that the site is now working for me just fine. Thanks for getting this fixed.

[ParrLeyne]

I can confirm that the site is now working for me just fine. Thanks for getting this fixed.

I can also access the site from Home.

[mhouston]

Finally no more proxy required for me...