Unable to connect port 119

[Paul]

Most of today I have been unsuccessful in connecting to news.eternal-
september.org on port 119, but I can connect OK on port 80.

Have I missed something?

Thank you.
--
Paul

[Lynn McGuire]

Me too. Port 119 refuses connections but
port 80 works just fine.

Lynn

[Geopelia]

"Lynn McGuire" <l...@winsim.com> wrote in message
news:kdpm3d$58q$1...@dont-email.me...

I can't connect either. What is a port? How do I know where to find it, and
what am I supposed to do please?
Do I need the computer man?
Or is this just something eternal-september will fix their end?

Geopelia

[Paul]

Lynn McGuire <l...@winsim.com> wrote in

news:kdpm3d$58q$1...@dont-email.me:

Thank you. At least I am not imagining things.

--
Paul

[GlowingBlueMist]

On 1/23/2013 3:34 PM, Paul wrote:

I don't know about 119 but 563 using SSL/TLS has been working OK so far
on Thunderbird.

[Barry Margolin]

In article <kdpqme$fej$1...@dont-email.me>,

I just switched my MT-Newswatcher similarly.

--
Barry Margolin
Arlington, MA

[FirstPost]

On Thu, 24 Jan 2013 11:30:53 +1300, "Geopelia" <phil...@xtra.co.nz>
wrote:

http://michaelstevenstech.com/outlookexpressnewreader.htm

[suzeeq]

I just switched it to port 80 and it's working.

[Martin Riddle]

"GlowingBlueMist" <Glowing...@truly.invalid> wrote in message
news:kdpqme$fej$1...@dont-email.me...

Confirmed 563 SSL works.
But 119 does not.

Cheers

[Ray Banana]

Thus spake Paul <pssa...@comcast.net.INVALID>

> Most of today I have been unsuccessful in connecting to news.eternal-
> september.org on port 119, but I can connect OK on port 80.
> Have I missed something?

No, I have, obviously, Due to a previous problem with user
authentication, the daemon listening on port 119 seems to have hung (it
was still running, but it unable to bind to the port). I have just
restarted it and everything is back to normal.

--
Time flies like an arrow, fruit flies like a Banana.
http://www.eternal-september.org

[Ray Banana]

Thus spake Paul <pssa...@comcast.net.INVALID>

> Most of today I have been unsuccessful in connecting to news.eternal-
> september.org on port 119, but I can connect OK on port 80.
> Have I missed something?

No, I have, obviously, Due to a previous problem with user
authentication, the daemon listening on port 119 seems to have hung (it

was still running, but it was unable to bind to the port). I have just

[Ian]

On 2013-01-24, Ray Banana <ray...@banana.shacknet.nu> wrote:

Still seem to be having problems using IPV6. Was working briefly,
now getting no response on port 119:

[ian@vm45 ~]$ host news.eternal-september.org
news.eternal-september.org has address 88.198.244.100
news.eternal-september.org has IPv6 address 2a01:4f8:140:9383::4

[ian@vm45 ~]$ ping6 news.eternal-september.org
PING news.eternal-september.org(news.eternal-september.org) 56 data bytes
64 bytes from news.eternal-september.org: icmp_seq=1 ttl=54 time=46.9 ms
64 bytes from news.eternal-september.org: icmp_seq=2 ttl=54 time=48.9 ms
64 bytes from news.eternal-september.org: icmp_seq=3 ttl=54 time=47.7 ms

[root@vm10 ~]# tcpdump -i eth1 port nntp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
08:16:25.935561 IP6 vm45.home.jusme.com.51431 > news.eternal-september.org.nntp: Flags [S], seq 3628865925, win 5760, options [mss 1440,sackOK,TS val 2991309432 ecr 0,nop,wscale 6], length 0
08:16:47.173809 IP6 vm45.home.jusme.com.51437 > news.eternal-september.org.nntp: Flags [S], seq 3401415202, win 5760, options [mss 1440,sackOK,TS val 2991330670 ecr 0,nop,wscale 6], length 0


--
Ian

"Tamahome!!!" - "Miaka!!!"

[Jay E. Morris]

At least not in this case. But those glowing pink things in the corner
of your office *are* out to get you, you know.

[homepc]

On 23/01/2013 9:43 PM, Ray Banana wrote:
> Thus spake Paul <pssa...@comcast.net.INVALID>
>
>> Most of today I have been unsuccessful in connecting to news.eternal-
>> september.org on port 119, but I can connect OK on port 80.
>> Have I missed something?
>
> No, I have, obviously, Due to a previous problem with user
> authentication, the daemon listening on port 119 seems to have hung (it
> was still running, but it was unable to bind to the port). I have just
> restarted it and everything is back to normal.
>

Could someone please post all the alternate settings to apply if this
type of outage happens again?

For example, I am using Thunderbird with port 119 server
news.eternal-september.org News server NNTP. What changes could I
apply to try out another connection?

Use KISS in your responses please ;-P

[homepc]

Here is a picture link of my TB ET settings described in my earlier post.

http://img4.imageshack.us/img4/6533/tbetsettings.png


Thanks!

[Paul]

Ray Banana <ray...@banana.shacknet.nu> wrote in
news:m2pq0v6...@banana.shacknet.nu:

> Thus spake Paul <pssa...@comcast.net.INVALID>
>
>> Most of today I have been unsuccessful in connecting to
>> news.eternal- september.org on port 119, but I can connect OK on
>> port 80. Have I missed something?
>
> No, I have, obviously, Due to a previous problem with user
> authentication, the daemon listening on port 119 seems to have
> hung (it was still running, but it was unable to bind to the
> port). I have just restarted it and everything is back to normal.

Thanks, Ray, for all the great service!

--
Paul

[Kerner]

On Thursday, January 24, 2013 9:13:57 AM UTC-8, homepc wrote:
> On 24/01/2013 11:02 AM, homepc wrote:
>
> > On 23/01/2013 9:43 PM, Ray Banana wrote:
>

> >> Thus spake Paul <pssawyer@*.INVALID>

>
> >>
>
> >>> Most of today I have been unsuccessful in connecting to news.eternal-
>
> >>> september.org on port 119, but I can connect OK on port 80.
>
> >>> Have I missed something?
>
> >>
>
> >> No, I have, obviously, Due to a previous problem with user
>
> >> authentication, the daemon listening on port 119 seems to have hung (it
>
> >> was still running, but it was unable to bind to the port). I have just
>
> >> restarted it and everything is back to normal.
>
> >>
>
> >
>
> > Could someone please post all the alternate settings to apply if this
>
> > type of outage happens again?
>
> >
>
> > For example, I am using Thunderbird with port 119 server
>
> > news.eternal-september.org News server NNTP. What changes could I
>
> > apply to try out another connection?
>
> >
>
> > Use KISS in your responses please ;-P
>
> >
>
> >
>
> >
>
> >
>
> Here is a picture link of my TB ET settings described in my earlier post.
>
>
>
> http://img4.imageshack.us/img4/6533/tbetsettings.png
>
>
>
>
>
> Thanks!

On Thursday, January 24, 2013 9:13:57 AM UTC-8, homepc wrote:
> On 24/01/2013 11:02 AM, homepc wrote:
>
> > On 23/01/2013 9:43 PM, Ray Banana wrote:
>

> >> Thus spake Paul <pssawyer@*.INVALID>

>
> >>
>
> >>> Most of today I have been unsuccessful in connecting to news.eternal-
>
> >>> september.org on port 119, but I can connect OK on port 80.
>
> >>> Have I missed something?
>
> >>
>
> >> No, I have, obviously, Due to a previous problem with user
>
> >> authentication, the daemon listening on port 119 seems to have hung (it
>
> >> was still running, but it was unable to bind to the port). I have just
>
> >> restarted it and everything is back to normal.
>
> >>
>
> >
>
> > Could someone please post all the alternate settings to apply if this
>
> > type of outage happens again?
>
> >
>
> > For example, I am using Thunderbird with port 119 server
>
> > news.eternal-september.org News server NNTP. What changes could I
>
> > apply to try out another connection?
>
> >
>
> > Use KISS in your responses please ;-P
>
> >
>
> >
>
> >
>
> >
>
> Here is a picture link of my TB ET settings described in my earlier post.
>
>
>
> http://img4.imageshack.us/img4/6533/tbetsettings.png
>
>
>
>
>
> Thanks!

I have the same settings; Thunderbird is reporting a "Failed to connect to server" error. I tried changing to port 80 but no joy :(

[Bit Twister]

On Thu, 24 Jan 2013 11:02:50 -0600, homepc wrote:
>
> Could someone please post all the alternate settings to apply if this
> type of outage happens again?

Does the port numbers here help.
http://www.eternal-september.org/serverstatus.php?language=en

[homepc]

http://img694.imageshack.us/img694/8566/etnewsserver.png

I am using the first option. If I were to use port 80 would I just
change the port setting and server name in TB?

If I were to use either of the SSL ports, what other changes would I
need to make?

[Bit Twister]

On Thu, 24 Jan 2013 12:13:59 -0600, homepc wrote:
>
> http://img694.imageshack.us/img694/8566/etnewsserver.png
>
> I am using the first option. If I were to use port 80 would I just
> change the port setting and server name in TB?

If it were I, I would have a separate entry for each server.

> If I were to use either of the SSL ports, what other changes would I
> need to make?

Sorry, I do not use thunderbird/windows, so someone else will have to
help. I thought there settings for some news readers but I looked
around a little bit on the site and did not see them.

[Ray Banana]

Thus spake homepc <wieb...@gmail.com>

> Could someone please post all the alternate settings to apply if this
> type of outage happens again?
>
> For example, I am using Thunderbird with port 119 server
> news.eternal-september.org News server NNTP. What changes could I
> apply to try out another connection?
>
> Use KISS in your responses please ;-P

The following information is contained in the registration mail every newly
registered user receives. It is also available at

http://www.eternal-september.org/index.php?showpage=techinfo

Eternal-September.org can be accessed via the following server names and ports:

----------------------------------
Server name: news.eternal-september.org
----------------------------------
Port : 119
Port : 563 (encrypted)

----------------------------------
Server name: reader80.eternal-september.org
----------------------------------
Port : 80

----------------------------------
Server name: reader443.eternal-september.org
----------------------------------
Port : 443 (encrypted)
The number of concurrent connections to the server is limited to 4.

[homepc]

Thanks for the info Ray!

[Ed Cryer]

There are three settings to apply for each of the four different entries.
1. Server name
2. Port
3. Connection security. This is "none" for your current setting (the
default in TB).

Hope this is clear enough.

Ed

[Ian]

Apologies for following up my own post, but just to clarify the
previous report, IPV6 connections to news.eternal-september.org
on port 119 are actually being refused, not ignored:

19:10:20.727479 IP6 vm45.home.jusme.com.50167 > news.eternal-september.org.nntp: Flags [S], seq 1786516734, win 5760, options [mss 1440,sackOK,TS val 3030544225 ecr 0,nop,wscale 6], length 0
19:10:20.774046 IP6 news.eternal-september.org.nntp > vm45.home.jusme.com.50167: Flags [R.], seq 0, ack 1786516735, win 0, length 0

19:11:48.156627 IP6 vm45.home.jusme.com.50433 > news.eternal-september.org.nntp: Flags [S], seq 3337359080, win 5760, options [mss 1440,sackOK,TS val 3030631654 ecr 0,nop,wscale 6], length 0
19:11:48.205140 IP6 news.eternal-september.org.nntp > vm45.home.jusme.com.50433: Flags [R.], seq 0, ack 3337359081, win 0, length 0

Connection over IPV4 is fine.

[GlowingBlueMist]

To keep it simple, pick a server name that goes with the ports mentioned
by others. If it is a secure connection port like 563 then in
Thunderbird you would change the port number of your program to 563 and
in the Security Settings change it from none to SSL/TLS

For server names using unsecured ports, like 80, all you need to do is
change the server name and set the port to 80 in Thunderbird. The other
servers/ports work basically the same way. Secured turn on the
Connection Security, none secure leave the Connection Security set at None

[Lynn McGuire]

On 1/23/2013 3:34 PM, Paul wrote:

And port 80 is no longer working but port
199 is back up.

Thanks,
Lynn