Last modified: 2010-03-17 01:03:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T24855, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 22855 - Could not see the Wikipedia - Tracert result information is added
Could not see the Wikipedia - Tracert result information is added
Status: RESOLVED DUPLICATE of bug 22641
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
PC All
: Normal critical (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-03-17 00:55 UTC by Noguchi
Modified: 2010-03-17 01:03 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Noguchi 2010-03-17 00:55:52 UTC
Since several weeks ago, I could not see (connect to) any Wikipedia
web site. Other sites or OK to see. I have checked secury tool, checked by
different browsers and also I have had support by my ISP company. However the
problem was not solved. Then my ISP company suggested to ask Wikipedia site to
solve this problem.

My PC (Home)'s IP address is 175.128.42.166.
I have to PC in my home and the OS is Windows7 and XP.

My ISP company and I guess Wikipedia is blocking this IP address.

I did tried Tracert to Wikipedia on my two PCs in my home. And the result is as follows;

> Tracing route to rr.pmtpa.wikipedia.org [298.80.152.2] over a maximum 
> of 30 hops:
> 1. *   *   *  Request timed out.
> 2. *   *   *  Request timed out.
> 3. *   *   *  Request timed out.
> 4. *   *   *  Request timed out.
> 5. *   *   *  Request timed out.
> 6. *   *   *  Request timed out.
> 7. *   *   *  Request timed out.
> 8. *   *   *  Request timed out.
> 9. *   *   *  Request timed out.
> 10. *   *   *  Request timed out.
> 11. *   *   *  Request timed out.
> 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. *   *   *  Request timed out.
> 23. *   *   *  Request timed out.
> 24. *   *   *  Request timed out.
> 25. *   *   *  Request timed out.
> 26. *   *   *  Request timed out.
> 27. *   *   *  Request timed out.
> 28. *   *   *  Request timed out.
> 29. *   *   *  Request timed out.
> 30. *   *   *  Request timed out.
> 
> Trace complete.
> 
My two PCs has dirrenet security soft and OS, but the two PC's Tracert results
are the same. ( I tried with some different Web browser but the results are the
same.)

PC-A) COMODO security / Windows7
PC-B) Security Zero / XP

When I did Tracert to www.yahoo.co.jp, the result is as follows;

> Tracing route to www.ya.gl.yahoo.co.jp [124.83.139.191] over a maximum 
> of 30 hops:
> 1. *   *   *  Request timed out.
> 2. *   *   *  Request timed out.
> 3. *   *   *  Request timed out.
> 4. *   *   *  Request timed out.
> 5. *   *   *  Request timed out.
> 6. *   *   *  Request timed out.
> 7. *   *   *  Request timed out.
> 8. *   *   *  Request timed out.
> 9. *   *   *  Request timed out.
> 10. *   *   *  Request timed out.
> 11. 18 ms    18 ms    17 ms  f2.top.vip.ogk.yahoo.co.jp
[124.83.139.191]
> Trace complete.

And attached file is the Tracert Wikipedia result from my company's PC.

Would you please checked and solve it?

Thank you in advance and best regards,

Masayoshi.Noguchi

PS. This is the continuation of Bug22641, because nobody have not helped for Bug22641 in these days and I do not know how to ask to somebody to help me. So I created this new report. If there is another way to ask somebody to help to solve old and stopped issue of bug report (22641), please let me know how to do it.
Comment 1 Bawolff (Brian Wolff) 2010-03-17 01:03:51 UTC
Just because no one has responded, please don't open a new bug, make any further comments on the previous one. Perhaps simply no one who has looked at that bug knows what the problem is. I must say though it seems rather odd to me (me being someone without a great amount of knowledge how the internet works) that the tracert to yahoo did not show any intermediate steps.

marking as dupe

*** This bug has been marked as a duplicate of bug 22641 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links