Usenet still up the spout after upgrades.

[#1]

I'm still getting "480" errors here (at work).  IP address 212.159.*.*.  I can't raise a ticket since I am not the sysadmin.  Can Bob or someone else help please?

[#2]

Just set up a new newsgroup account and it's working fine : 212.159.121.*
B.

[#3]

USENET IS STILL NOT WORKING HERE.
It would be nice if Bob Pullen would acknowledge that he is aware that some of us still don't have access to USENET.
It would also be nice to know that something IS being done about this.
    Brian Gladman
[Moderator's note by Peter (PJ): Please do not quote the previous post in full, as per the link:rules]

[#4]

Mostly working here since last night.  Still not able to get New messages from uk.telecom and comp.dcom.telecom.tech though?
My other newsgroups are now updated; de-duplicated and resynchronised.
Very slow updating messages 1 per second! 
M

[#5]

Quote from: gladman

Quote from: Barry Just set up a new newsgroup account and it's working fine : 212.159.121.* B. USENET IS STILL NOT WORKING HERE. It would be nice if Bob Pullen would acknowledge that he is aware that some of us still don't have access to USENET. It would also be nice to know that something IS being done about this.     Brian Gladman

I'm sure Bob is still on the case:  See http://portal.plus.net/supportpages.html?a=2&support_action=messages&ispservice_id=usenet

[#6]

The last status post was early yesterday evening, OVER 16 HOURS AGO.
Bob asked a question here at about 07:30 this morning but has not been seen since.
I have a ticket outstanding that has not been answered.
So, sadly, I don't share your confidence. 
Bob, what are you doing to solve this problem?
When will I have a USENET service again?
    Brian Gladman
[Moderator's note by Peter (PJ): Please do not quote the previous post in full, as per the link:rules]

[#7]

Brian,
Bob is aware that some of our customers are still experiencing difficulties when trying to use our usenet services.
He and Chris are currently liaising with our contact within our Networks team who is dealing with Giganews.

[#8]

Quote from: Jameseh

Brian, Bob is aware that some of our customers are still experiencing difficulties when trying to use our usenet services. He and Chris are currently liaising with our contact within our Networks team who is dealing with Giganews.

James
I am grateful for the update but you don't seem to have any idea of when my USENET service might be restored.  It could even be days by the look of it.
Since (a) Giganews seem to have created this problem, and (b) we have no idea when it will be solved, why don't you ask Giganews to offer a free direct USENET account to those of us who they have bumped off your service until such a time as they can offer the service via PlusNet again?
    Brian Gladman

[#9]

Still dead at 12:25pm.
OE gives the following error message:
Configuration:
  Account: news.plus.net
  Server: news.plus.net
  Protocol: NNTP
  Port: 119
  Secure(SSL): 0
  Code: 800ccc0e

[#10]

Still nothing here either same OE error message too
I know the team are working on it but haven't you just gotta love Bobs Service Status the most most recent by the way ..quote> 
01/04/2008 @ 18:27  Usenet Access (50908) - UPDATE
We have since corrected this error, and most customers are now able to access the service without problems.
Bob Pullen
Customer Support
Well done Bob! you are correct we are not "Most" customers

[#11]

Brian,
I'll see about getting an update out via Service Status.
Basically:

• Access has been restored for most PlusNet customers including those in the RIN network.
  
• It would appear that there are still some issues with certain IP addresses.
  
• Authentication for PlusNet accounts that allow it is not currently working.
  
• Access to the Metronet news server may not currently be possible.
  

Seems like its 212.xxx.xxx.xxx and 81.xxx.xxx.xxx ranges at the moment
I can't apologise enough to those of you without access. We're continuing to work on this as a priority.

[#12]

Bob - I've successfully connected using a 212.159.121.x  address, but this was a completely new nntp account
Stab in the dark, but perhaps it's a cached DNS entry causing problems?
If those of you having problems could try the following:
Start->Run
Type in 'cmd' and hit Enter
type:
ping news.plus.net
And see what IP you're given.
My output:

H:\>ping news.plus.net
Pinging plusnet.vsrv-ams.supernews.net [138.199.67.64] with 32 bytes of data:
Reply from 138.199.67.64: bytes=32 time=29ms TTL=112
Reply from 138.199.67.64: bytes=32 time=30ms TTL=113
Reply from 138.199.67.64: bytes=32 time=31ms TTL=112
Reply from 138.199.67.64: bytes=32 time=30ms TTL=112
Ping statistics for 138.199.67.64:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 31ms, Average = 30ms
H:\>exit

If the IP address differs in any way, close your news reader, then type in:
ipconfig /flushdns
then reopen your newsreader and see if you can then connect.
B.

[#13]

Quote from: Barry

Stab in the dark, but perhaps it's a cached DNS entry causing problems? If those of you having problems could try the following: Start->Run Type in 'cmd' and hit Enter type: ping news.plus.net And see what IP you're given.

"Destination host unreachable."
Grr!

[#14]

Quote from: Bob

Brian, I'll see about getting an update out via Service Status. Basically: Access has been restored for most PlusNet customers including those in the RIN network. It would appear that there are still some issues with certain IP addresses. Authentication for PlusNet accounts that allow it is not currently working. Access to the Metronet news server may not currently be possible. Seems like its 212.xxx.xxx.xxx and 81.xxx.xxx.xxx ranges at the moment I can't apologise enough to those of you without access. We're continuing to work on this as a priority.

Bob
Thanks for the update.  Its good to know that you are on the case.
I have not tried deleting and renewing my news account (very onerous) but I have tried the other ideas suggested here to no avail.
    Brian Gladman

[#15]

Quote from: Barry

Bob - I've successfully connected using a 212.159.121.x  address, but this was a completely new nntp account Stab in the dark, but perhaps it's a cached DNS entry causing problems? If those of you having problems could try the following: Start->Run Type in 'cmd' and hit Enter type: ping news.plus.net And see what IP you're given. My output: H:\>ping news.plus.net Pinging plusnet.vsrv-ams.supernews.net [138.199.67.64] with 32 bytes of data: Reply from : bytes=32 time=29ms TTL=112 Reply from 138.199.67.64: bytes=32 time=30ms TTL=113 Reply from 138.199.67.64: bytes=32 time=31ms TTL=112 Reply from 138.199.67.64: bytes=32 time=30ms TTL=112 Ping statistics for 138.199.67.64:     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 29ms, Maximum = 31ms, Average = 30ms H:\>exit If the IP address differs in any way, close your news reader, then type in: ipconfig /flushdns then reopen your newsreader and see if you can then connect. B.

I got the same addresses as you namely 138.199.67.64  Where do you type in the  ipconfig /flushdns ? I guess into the same Start/Run box  which I did but upon reopeniong my OE and creating a new news account still theres no server found. I guess also it's still  news.plus.net    is it?
Dave