NNTP dowm here again

Anyone else in UK/Europe having probs with the NNTP side for the forums?

Not sure when it started as I have bveen out since anout 14:00, just tried to d/load latest headers and got zilch.

Mark:(

baskitcaise wrote:
> Anyone else in UK/Europe having probs with the NNTP side for the forums?
>
> Not sure when it started as I have bveen out since anout 14:00, just
> tried to d/load latest headers and got zilch.
>
> Mark:(
>
>
Running fine for me right now, though I’m in the US (EST). Are you still
having an issue?

Running fine for me right now, though I’m in the US (EST). Are you still
having an issue?

Ah, just came back up for me here, not sure how long ago have been on phone for last 1/2 hour :slight_smile:

It is funny it always seems to be about the same time each day between approx 18:00->2200 GMT ( not quite exactly ) but is fine for the rest of the day.

Tanks for reply though it reminded me to check again.

Hey baskitcaise:

> Tanks for reply though it reminded me to check again.

FYI you’ve reported NNTP down numerous times lately and each time I’ve
checked, NNTP has been up. I’d suggest you have some sort of
connectivity issue on port 119, perhaps a router problem, that appears
to be causing you to lose connectivity on that port. Just a thought.


Kim (12/9/2008 10:58:58 AM Mountain)

kgroneman wrote:

> Hey baskitcaise:
>
>> Tanks for reply though it reminded me to check again.
>
> FYI you’ve reported NNTP down numerous times lately and each time I’ve
> checked, NNTP has been up. I’d suggest you have some sort of
> connectivity issue on port 119, perhaps a router problem, that appears
> to be causing you to lose connectivity on that port. Just a thought.
>

Hi Kim,

Not blaming you :wink:

I know it is not at your end it seems to be that it is getting blocked somewhere en-route.

I was trying to find out if anyone else on this side of the pond has the same connection probs as me at those times of the day.

All other connections work fine from here to there and the web interface works OK, if that sort of thing floats your boat :sunglasses: the NNTP seems to die for me anywhere between approx 1800 and 2200 any other time it all goes swimmingly :slight_smile:

Could not check yesterday as I was away but will keep my eye open tonight to see if it happens again and see if I can track it down to a router/server somewhere.


Mark…

Nil illegitimi carborundum

On Wed, 10 Dec 2008 17:40:38 +0000, baskitcaise wrote:

> I know it is not at your end it seems to be that it is getting blocked
> somewhere en-route.

Hey, Mark! How you been?

tcptraceroute might be your friend for determining the problem. :slight_smile:

Jim

Jim Henderson wrote:

> On Wed, 10 Dec 2008 17:40:38 +0000, baskitcaise wrote:
>
>> I know it is not at your end it seems to be that it is getting
>> blocked somewhere en-route.
>
> Hey, Mark! How you been?

Hi Jim,

I am fine and back up and running, took ages to get a phone line and ADSL in my new bijou apartment :slight_smile: then my line went down due to an external cabling fault so only just recently got all working.

>
> tcptraceroute might be your friend for determining the problem. :slight_smile:
>
> Jim

Will try all possible things if it rears its ugly head again, obviously it will not happen again while I am here though.

Nice to hear from you again too.


Mark…

Nil illegitimi carborundum

Well things look weird now.

I cannot access the NNTP server to get headers or messages now ( not sure for how long was cooking ) but the tcptraceroute shows:-


baskitcase:/home/barkit # tcptraceroute 130.57.5.50
Selected device eth0, address 192.168.1.2, port 45270 for outgoing packets
Tracing the path to 130.57.5.50 on TCP port 80 (http), 30 hops max
1 192.168.1.1 0.805 ms 0.473 ms 0.448 ms
2 l1.ar10.f2s.hx4.dsl.pipex.net (62.241.161.237) 46.999 ms 46.692 ms 42.240 ms
3 ge-2-1-2.2.cr01.hx4.dsl.pipex.net (62.241.167.13) 42.848 ms 43.609 ms 42.498 ms
4 158.43.27.117 43.135 ms 42.205 ms 42.033 ms
5 so-1-1-0.XR2.LND2.ALTER.NET (158.43.233.110) 78.113 ms 45.674 ms 43.257 ms
6 so-2-0-0.IL2.NYC12.ALTER.NET (146.188.15.54) 121.168 ms 118.351 ms 120.881 ms
7 0.so-7-0-0.IL4.NYC9.ALTER.NET (146.188.15.2) 121.345 ms 117.891 ms 119.481 ms
8 0.so-5-1-0.XL4.DEN4.ALTER.NET (152.63.89.110) 195.476 ms 194.885 ms 196.806 ms
9 POS7-0.GW3.DEN4.ALTER.NET (152.63.72.73) 196.031 ms 196.234 ms 195.199 ms
10 65.206.183.22 198.953 ms 201.374 ms 196.991 ms
11 192.94.118.247 211.824 ms 212.742 ms 209.489 ms
12 * * *
13 130.57.5.50 [open] 198.381 ms 197.925 ms *
baskitcase:/home/barkit # whois 192.94.118.247

OrgName: Novell, Inc.
OrgID: NOVELL
Address: 2180 Fortune Drive
City: San Jose
StateProv: CA
PostalCode: 95131
Country: US

NetRange: 192.94.118.0 - 192.94.118.255
CIDR: 192.94.118.0/24
NetName: NOVELL-NET-SMALL2
NetHandle: NET-192-94-118-0-1
Parent: NET-192-0-0-0-0
NetType: Direct Assignment
NameServer: NS.NOVELL.COM
NameServer: SJFNS.SJF.NOVELL.COM
Comment:
RegDate: 1991-02-22
Updated: 1994-11-22

RTechHandle: KB60-ARIN
RTechName: Tunnell-Braun, Karl
RTechPhone: +1-408-577-7301
RTechEmail: BRAUN@novell.com

OrgTechHandle: DNJ4-ARIN
OrgTechName: Johnson, David N.
OrgTechPhone: +1-801-861-2561
OrgTechEmail: dnjohnson@novell.com

ARIN WHOIS database, last updated 2008-12-09 19:10

Enter ? for additional hints on searching ARIN’s WHOIS database.

baskitcase:/home/barkit # whois 130.57.5.50

OrgName: Novell, Inc.
OrgID: NOVELL-1
Address: 1800 South Novell Place
City: Provo
StateProv: UT
PostalCode: 84606
Country: US

NetRange: 130.57.0.0 - 130.57.255.255
CIDR: 130.57.0.0/16
NetName: NOVELL-WEST
NetHandle: NET-130-57-0-0-1
Parent: NET-130-0-0-0-0
NetType: Direct Assignment
NameServer: NS.NOVELL.COM
NameServer: NS2.NOVELL.COM
Comment:
RegDate: 1988-06-03
Updated: 2004-05-05

RAbuseHandle: BWA3-ARIN
RAbuseName: Wayne, Bruce
RAbusePhone: +1-801-861-2222
RAbuseEmail: bwayne@novell.com

RNOCHandle: BWA3-ARIN
RNOCName: Wayne, Bruce
RNOCPhone: +1-801-861-2222
RNOCEmail: bwayne@novell.com

RTechHandle: BWA3-ARIN
RTechName: Wayne, Bruce
RTechPhone: +1-801-861-2222
RTechEmail: bwayne@novell.com

OrgTechHandle: DNJ4-ARIN
OrgTechName: Johnson, David N.
OrgTechPhone: +1-801-861-2561
OrgTechEmail: dnjohnson@novell.com


Unless I am mistaken all should be well, it is like this on 3 different machines and I have not touched anything at all from them working a while ago…

Any clues?

baskitcaise,

> Well things look weird now.
>
> I cannot access the NNTP server to get headers or messages now ( not
> sure for how long was cooking ) but the tcptraceroute shows:-
>
>
> --------------------------------------------------------
> baskitcase:/home/barkit # tcptraceroute 130.57.5.50
>
> Selected device eth0, address 192.168.1.2, port 45270 for outgoing
> packets
> Tracing the path to 130.57.5.50 on TCP port 80 (http), 30 hops max

Try tracing using destination port 119 (nntp) rather than 80.

H.

Try tracing using destination port 119 (nntp) rather than 80.

H.[/QUOTE]

Still the same result, it does sttuter a bit in hop 12 but it did do that for port 80 as well.

baskitcase:/home/barkit # tcptraceroute 130.57.5.50 119
Selected device eth0, address 192.168.1.2, port 50037 for outgoing packets
Tracing the path to 130.57.5.50 on TCP port 119 (nntp), 30 hops max
1 192.168.1.1 0.710 ms 0.530 ms 0.523 ms
2 l1.ar10.f2s.hx4.dsl.pipex.net (62.241.161.237) 51.954 ms 49.802 ms 47.194 ms
3 ge-2-1-2.2.cr01.hx4.dsl.pipex.net (62.241.167.13) 49.691 ms 45.930 ms 48.200 ms
4 158.43.27.117 46.717 ms 46.382 ms 45.472 ms
5 so-1-1-0.XR2.LND2.ALTER.NET (158.43.233.110) 51.880 ms 45.716 ms 45.509 ms
6 so-2-0-0.IL2.NYC12.ALTER.NET (146.188.15.54) 119.641 ms 122.356 ms 120.073 ms
7 0.so-7-0-0.IL4.NYC9.ALTER.NET (146.188.15.2) 118.902 ms 120.159 ms 121.170 ms
8 0.so-5-1-0.XL4.DEN4.ALTER.NET (152.63.89.110) 195.205 ms 196.014 ms 196.034 ms
9 POS7-0.GW3.DEN4.ALTER.NET (152.63.72.73) 195.739 ms 197.696 ms 199.506 ms
10 65.206.183.22 199.427 ms 196.881 ms 197.183 ms
11 192.94.118.247 213.591 ms 210.161 ms 210.598 ms
12 * * *
13 130.57.5.50 [open] 203.903 ms * 201.448 ms

baskitcaise:

> baskitcase:/home/barkit # tcptraceroute 130.57.5.50 119
> Tracing the path to 130.57.5.50 on TCP port 119 (nntp), 30 hops max
> 12 * * *
> 13 130.57.5.50 [open] 203.903 ms * 201.448 ms

Should be working then - you’re getting over to the server.

are you able to telnet to 119 ?

H.

Yep I can get to there with telnet no probs, not 100% up with this though as I havenot used telnet for years :slight_smile:

Just in case it was my newsreader I tried Thunferbird and pan on all machines with same result, I even rebooted my router and turned off&on the firewall, just in case.

Still nada.

Funny it is every evening at these times.

I expext it to come back up in the next hour or two with no intervention from me.

Mark

On Wed, 10 Dec 2008 18:27:27 +0000, baskitcaise wrote:

> Jim Henderson wrote:
>
>> On Wed, 10 Dec 2008 17:40:38 +0000, baskitcaise wrote:
>>
>>> I know it is not at your end it seems to be that it is getting blocked
>>> somewhere en-route.
>>
>> Hey, Mark! How you been?
>
> Hi Jim,
>
> I am fine and back up and running, took ages to get a phone line and
> ADSL in my new bijou apartment :slight_smile: then my line went down due to an
> external cabling fault so only just recently got all working.

That’s good to hear. You know where to reach me - drop me a line and
let’s chat - would love to catch up.

> Will try all possible things if it rears its ugly head again, obviously
> it will not happen again while I am here though.
>
> Nice to hear from you again too.

Glad to help out. I ran across tcptraceroute while troubleshooting
another issue myself, and found it an interesting way to pinpoint where a
port is actually blocked.

Jim

On Wed, 10 Dec 2008 20:06:02 +0000, baskitcaise wrote:

> Unless I am mistaken all should be well, it is like this on 3 different
> machines and I have not touched anything at all from them working a
> while ago…

Yeah, that does look like it should be fine. Which newsreader are you
using?

Jim

Yeah, that does look like it should be fine. Which newsreader are you
using?

Jim[/QUOTE]

I usually use knode on OSS 11.1 rc1 and OSS 11.0 but have just tried thunderbird and pan, all to no avail.

If it comes back up on its own accord ( normally approx 2200 GMT ) then it points to something somewhere that is related to time, as stated it is only happening between 1800ish to 2200ish everyday and only on NNTP, my other groups are fine but not when it comes to Novell.

baskitcaise wrote:

<–snip–>

> Funny it is every evening at these times.
>
> I expext it to come back up in the next hour or two with no
> intervention from me.
>
> Mark
>
>

And here we are back on NNTP @ 2230 GMT.

I have changed nothing at all, still using knode which has been running all the time. no close and open no settings changed.

got to be somewhere but not here.

Go figure :slight_smile:

Thanks for the time Jim but methinks this is going to be a “Three pipe problem” ( sic ) :wink:


Mark…

Nil illegitimi carborundum

Hamish Speirs wrote:

<–snip–>.

Sorry Hamish did not realise it was you.

Hi.

:slight_smile:


Mark…

Nil illegitimi carborundum

On Wed, 10 Dec 2008 21:36:01 +0000, baskitcaise wrote:

> Yeah, that does look like it should be fine. Which newsreader are you
> using?
>
> Jim
>
>
> I usually use knode on OSS 11.1 rc1 and OSS 11.0 but have just tried
> thunderbird and pan, all to no avail.
>
> If it comes back up on its own accord ( normally approx 2200 GMT ) then
> it points to something somewhere that is related to time, as stated it
> is only happening between 1800ish to 2200ish everyday and only on
> NNTP, my other groups are fine but not when it comes to Novell.

Anything show up in a wireshark trace?

Jim

On Wed, 10 Dec 2008 22:35:58 +0000, baskitcaise wrote:

> Thanks for the time Jim but methinks this is going to be a “Three pipe
> problem” ( sic ) :wink:

Heh, no problem - any time. :slight_smile:

Jim

Mark,

> Sorry Hamish did not realise it was you.
>

NP.

> Hi.

Howdy - LTNS.

H.