cancel
Showing results for 
Search instead for 
Did you mean: 

Usenet still up the spout after upgrades.

TrentSC
Grafter
Posts: 32
Registered: ‎06-08-2007

Re: Usenet still up the spout after upgrades.

Quote from: dgdclynx
I am back. My static IP is 84.92.108.121. Giganews aint as bad as that although reports from the customer-feedback newgroup say that their porn filters are quite inadequate. I will have 2GB to download for my 60 newsgroups so I will do that in my Free time.

I'm on 81.174.169.105 if it's relevant
bobpullen
Community Gaffer
Community Gaffer
Posts: 16,899
Thanks: 5,008
Fixes: 316
Registered: ‎04-04-2007

Re: Usenet still up the spout after upgrades.

Can everybody who's been unable to connect try again please. We've made a few more changes that we're hoping should have reinstated your access.
Quote from: TrentSC
So, let's recap on this problem.
We don't know exactly what the problem is; we can only surmise rather than accurately identify the problem.

For the record, it seems that Giganews' systems do not like having permitted netblocks shared between reseller accounts. As we now have 3 accounts (Metronet, Madasafish & PlusNet) all with varying degrees of access, the situation becomes slightly more complex. We think we might be close to fixing this and most PlusNet customers should be able to connect.
We're still looking at Metronet as something quite odd seems to be happening with that:
C:\Users\Bobby>nslookup news.metronet.co.uk
Server:  ptn-cdns02.plus.net
Address:  212.159.6.10
Non-authoritative answer:
Name:    corp.supernews.com
Address:  216.168.3.44
Aliases:  news.metronet.co.uk
supernews.metronet.co.uk

Quote
We don't know how long it'll take to fix it.

Should be fixed for PlusNet and Madasafish brands by the end of today (if not already).
Quote
We don't know the scope of the problem, or how many customers might be affected.

Any netblocks that were shared between our Giganews accounts will have been affected. This comprises largely of dynamic IP addresses although some static IP users will have been (or may still be) affected too.
Quote
We didn't realise that web-based Usenet access (through our portal) was borked.

No, not specifically until somebody pointed it out, but that was caused by the same issue (and should now be fixed).
Quote
We don't know if we have an SLA in place with our service provider.

I don't, no. I can probably find out though so will ask around.
Quote
There doesn't appear to be any meaningful communication between the comms team and the back-end technicians who are supposed to be fixing this.

I've been in continuous contact with the technician who's been working with Giganews.
Quote
We don't know what the service provider is doing to fix the problem.

They've managed to modify their systems to bypass the aforementioned limitation.
Quote
We don't appear to have tested this changed service before it went live.

How? Given the nature of the work I don't think there would have been a feasible means of doing this. It's kind of all or nothing TBH.
Quote
We don't appear to have planned this changeover adequately and we had no change management contingency plan to account for problems during or immediately after the switchover.

The change management ball is firmly in Giganews' court. We weren't expecting this level of disruption.
Quote
Despite the service status (finally) showing red, we're not planning to issue more than one update in a full 24-hour period.

How many Service Status posts do you want if there's no update to provide? The 'next update' time is quite often set to 6:00pm the following day as a matter of course. You'll notice this will other announcements.
Quote
Latest from the ping...
ping news.plus.net
Pinging plusnet.vsrv-ams.supernews.net [138.199.67.64] with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Ping statistics for 138.199.67.64:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss).
ping sn-ip.vsrv-sjc.supernews.net
Pinging sn-ip.vsrv-sjc.supernews.net [216.168.3.44] with 32 bytes of data:
Reply from 216.168.3.44: bytes=32 time=94ms TTL=111
Reply from 216.168.3.44: bytes=32 time=144ms TTL=111
Reply from 216.168.3.44: bytes=32 time=87ms TTL=111
Reply from 216.168.3.44: bytes=32 time=136ms TTL=111
Ping statistics for 216.168.3.44:
Packets: Sent = 4, Received = 4, Lost = 4 (0% loss).
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 144ms, Average = 115ms

I'd suggest everybody use the server address news.plus.net as opposed to the specific supernews addresses that were used when testing the old platform.

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

andyburns
Newbie
Posts: 8
Registered: ‎01-04-2008

Re: Usenet still up the spout after upgrades.

Quote from: pnuser
Don't like the sound of all that spam

That's not the half of it, the article numbers on the new servers are all over the shop  Cry
A thread from yesterday "mixed" into an unrelated thread from 2 years ago
No articles at all available in plusnet.announce
p.s. I fully know the the article numbers will have changed, so I have created a brand new usenet account within thunderbird and re-subscribed to groups from scratch.
bobpullen
Community Gaffer
Community Gaffer
Posts: 16,899
Thanks: 5,008
Fixes: 316
Registered: ‎04-04-2007

Re: Usenet still up the spout after upgrades.

Plenty of posts in plusnet.announce for me. Sounds like a client side issue if I'm honest. I deleted my news account in it's entirety, created a new account and then resubscribed to my groups. Seems to have done the trick.

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

TrentSC
Grafter
Posts: 32
Registered: ‎06-08-2007

Re: Usenet still up the spout after upgrades.

Hasn't worked here, using either Thunderbird or OE
[Moderator's note by Jonathan (chillypenguin):  Full quote of preceding post removed. Forum Rules ]
jelv
Seasoned Hero
Posts: 26,785
Thanks: 971
Fixes: 10
Registered: ‎10-04-2007

Re: Usenet still up the spout after upgrades.

Still not working on 86.138.60.*
Edit: Nor on 86.137.51.*
Edit 2: Nor 86.152.46.*
jelv (a.k.a Spoon Whittler)
   Why I have left Plusnet (warning: long post!)   
Broadband: Andrews & Arnold Home::1 (FTTC 80/20)
Line rental: Pulse 8 Home Line Rental (£14.40/month)
Mobile: iD mobile (£4/month)
Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: Usenet still up the spout after upgrades.

That looks like a RIN range, IIRC that was one of the last blocks to be added. Should be fixed shortly jelv.
Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
jelv
Seasoned Hero
Posts: 26,785
Thanks: 971
Fixes: 10
Registered: ‎10-04-2007

Re: Usenet still up the spout after upgrades.

Still not working - another range: 81.152.31.*
jelv (a.k.a Spoon Whittler)
   Why I have left Plusnet (warning: long post!)   
Broadband: Andrews & Arnold Home::1 (FTTC 80/20)
Line rental: Pulse 8 Home Line Rental (£14.40/month)
Mobile: iD mobile (£4/month)
andyburns
Newbie
Posts: 8
Registered: ‎01-04-2008

Re: Usenet still up the spout after upgrades.

Quote from: Bob
Plenty of posts in plusnet.announce for me. Sounds like a client side issue if I'm honest. I deleted my news account in it's entirety, created a new account and then resubscribed to my groups. Seems to have done the trick.

I realise thunderbird isn't the most sophisticated news client.
I haven't actually deleted my old news account yet, but I did create a new one and subscribed to groups from scratch within that account, also tried unsubscribe/resubscribe again, but will try from scratch again, just to be sure.
For now I've created a motzarella account and using that from thunderbird seems 10x better than giganews.
EDIT:
Deleted all plusnet/supernews/giganews related accounts, added back news.plus.net, downloaded grouplist, subscribed to plusnet.announce, zero articles.
bobpullen
Community Gaffer
Community Gaffer
Posts: 16,899
Thanks: 5,008
Fixes: 316
Registered: ‎04-04-2007

Re: Usenet still up the spout after upgrades.

Quote from: jelv
Still not working - another range: 81.152.31.*

We've requested the addition of the entire RIN range jelv. Hopefully Giganews will act on this shortly.

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

pnuser
Grafter
Posts: 43
Registered: ‎31-03-2008

Re: Usenet still up the spout after upgrades.

Quote from: Bob
Plenty of posts in plusnet.announce for me. Sounds like a client side issue if I'm honest. I deleted my news account in it's entirety, created a new account and then resubscribed to my groups. Seems to have done the trick.

just did that
NADDA
jkerr82508
Grafter
Posts: 62
Thanks: 1
Registered: ‎25-06-2007

Re: Usenet still up the spout after upgrades.

Yesterday, I deleted my news account and re-created it. After more than a day of authentication failures, I now have a connection and it seems to be working O.K.
Jim
waynepyrah
Grafter
Posts: 57
Thanks: 2
Registered: ‎06-04-2007

Re: Usenet still up the spout after upgrades.

I'm still getting errors as of 18:45 (212.159.60.xxx)
mbeenham
Rising Star
Posts: 96
Thanks: 5
Fixes: 1
Registered: ‎08-12-2007

Re: Usenet still up the spout after upgrades.

Quote from: Bob
Can everybody who's been unable to connect try again please. We've made a few more changes that we're hoping should have reinstated your access.

Still not working here.
Still same problem - server is requesting authentication.
Tue, 1 Apr 2008 18:46:01 Collecting Usenet News from news.plus.net
Tue, 1 Apr 2008 18:46:01 Authentication required for news.plus.net
Tue, 1 Apr 2008 18:46:01 Unexpected NEWS 5xx : 501 bad authentication
Tue, 1 Apr 2008 18:46:01 News server does not support newsgroup rating
Tue, 1 Apr 2008 18:46:01 News connection to news.plus.net closed - filing continues
Tue, 1 Apr 2008 18:46:01 News from news.plus.net completed, 0 articles fetched, 0 posted
stathe
Rising Star
Posts: 795
Thanks: 25
Fixes: 1
Registered: ‎30-07-2007

Re: Usenet still up the spout after upgrades.

Well its Not working here , client side you say !!!! you messed it up so tell us how to put it right, please. Regards  E