cannot connect to ftp.mozilla.org (ftp://mozilla.isc.org/pub/mozilla.org/) from ip block 60.234.0.0 - 60.234.255.255

RESOLVED FIXED

Status

--
major
RESOLVED FIXED
14 years ago
14 years ago

People

(Reporter: siimo2005, Assigned: kveton)

Tracking

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040910

When i try to visit ftp.mozilla.org it doesn't work most of the time. As i was
told it picks one of the mirrors from the list of primary mirrors on
http://www.mozilla.org/mirrors.html, i discovered that i cannot connect to
ftp://mozilla.isc.org/pub/mozilla.org/ but rest of them work fine for me. 

I was advised by my isp that the mirror may have an outdated bogon list filter.
There are/were a few other sites having this problem as well and theres a
newsgroup post made by a staff of the isp regarding this issue here:
http://tinyurl.com/3wg52

Reproducible: Always
Steps to Reproduce:
1. Be connected to the internet and assigned an ip from this (60.234.0.0 -
60.234.255.255) ip block, futher information: http://tinyurl.com/42q7j 
2. type ftp.mozilla.org in any browser window (and be routed to mozilla.isc.org
mirror)
Actual Results:  
connection times out.

Expected Results:  
access to the ftp server
(Reporter)

Updated

14 years ago
Summary: cannot connect to ftp.mozilla.org (ftp://mozilla.isc.org/pub/mozilla.org/) → cannot connect to ftp.mozilla.org (ftp://mozilla.isc.org/pub/mozilla.org/) from ip block 60.234.0.0 - 60.234.255.255 60.234.255.255
(Assignee)

Comment 1

14 years ago
ISC has fixed this problem on their end.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
Summary: cannot connect to ftp.mozilla.org (ftp://mozilla.isc.org/pub/mozilla.org/) from ip block 60.234.0.0 - 60.234.255.255 60.234.255.255 → cannot connect to ftp.mozilla.org (ftp://mozilla.isc.org/pub/mozilla.org/) from ip block 60.234.0.0 - 60.234.255.255
You need to log in before you can comment on or make changes to this bug.