609089 - news.mozilla.org unreachable with SeaMonkey 2.0.10 & 2.1b1

Status: RESOLVED WONTFIX

(mozilla.org Graveyard :: Server Operations, task)

Description

[Felix Miata]

Ping & traceroute to news.mozilla.org 216.196.97.169 aka news.mozilla.giganews.com succeed but SM times out trying do anything useful like viewing previously subscribed newsgroup messages (e.g. mozilla.dev.tech.layout; mozilla.dev.ports.os2), or update subscription or groups messages databases. Address I'm trying from is 72.40.110.xxx.

Comment 1

[Aravind Gottipati [:aravind]]

what does "telnet news.mozilla.org 119" show you?  This is what I see from my work computer.

~ $telnet news.mozilla.org 119
Trying 216.196.97.169...
Connected to news.mozilla.org.
Escape character is '^]'.
200 news.mozilla.org
^]
telnet> q
Connection closed.
~ $

Comment 2

[Aravind Gottipati [:aravind]]

Also, I just checked it using gnus, and I can fetch/read old news posts just fine.

Comment 3

[Felix Miata]

$ telnet news.mozilla.org:119
telnet: news.mozilla.org:119 : name or service not known
$ telnet news.mozilla.org 119
Trying 216.196.97.169...
telnet: connect to address 216.196.97.169: connection timed out

N4 mailnews also times out.

Comment 4

[Aravind Gottipati [:aravind]]

I logged a case with giganews and referred them to this bug.

Comment 5

[Aravind Gottipati [:aravind]]

Giganews says that they haven't seen any network issues.  Have there been any changes on your end (firewall, a.v. software, etc)?  Also they need a traceroute from your end to their host.  Your full ip would also help.  If you are un-comfortable posting that information in the bug, feel free to e-mail it to me directly.

Comment 6

[Felix Miata]

Traceroute & IP emailed to aravind. No system changes. Continued session of SM functioned as expected previous day and prior. WWW, email & IRC sessions all work as expected.

Comment 7

[Aravind Gottipati [:aravind]]

Here is the response from giganews.

---------------------------------------------------------------------------
We heard from a couple other users today, who are in the same region as your user, and had similar complaints.  I confirmed that we haven't made any changes with regard to their network, so I suspect the change
came from one of the ISP's involved.

Please have him try telnetting to the server on port 80.  If that works, he can use that port in his newsreader as well.

His route to our server in DC is a bit weird.  It goes from Tampa Bay, to Dallas, to Atlanta, to DC.  But I wouldn't expect that to cause a total loss of connectivity.

If we hear back that port 80 doesn't work, there may be other things we can try.
---------------------------------------------------------------------------

In short - may be a problem caused by something your isp did.  Please try port 80 as suggested and let us know.

Comment 8

[Felix Miata]

Using 80 instead of 119 works. The ISP here is Earthlink via Bright House cable.