Error: Code : Unexpected response: '' Ubuntu 13.10 update

[pupwiz]

nzedb stopped updating last night after a ubuntu update including below

Code: [Select]

Start-Date: 2014-03-10  19:32:15
Commandline: apt-get install smartmontools+
Install: heirloom-mailx:amd64 (12.5-2, automatic), smartmontools:amd64 (6.1+svn3812-1)
End-Date: 2014-03-10  19:32:24

Start-Date: 2014-03-10  19:32:59
Commandline: apt-get install lm-sensors+
Install: lm-sensors:amd64 (3.3.3-1ubuntu1)
End-Date: 2014-03-10  19:33:03

Start-Date: 2014-03-10  19:33:56
Commandline: apt-get install ctdb+
Install: ctdb:amd64 (2.4+debian0-1)
End-Date: 2014-03-10  19:34:02

Start-Date: 2014-03-10  19:37:42
Commandline: apt-get install udisks2:amd64+ libudisks2-0:amd64+ udisks:amd64+ python-psutil:amd64+ python3-distupgrade:all+ ubuntu-release-upgrader-core:all+
Install: python-httplib2:amd64 (0.8-2, automatic), python-keyring:amd64 (1.6-1, automatic), python-apport:amd64 (2.12.5-0ubuntu2.2, automatic), python-oauth:amd64 (1.0.1-3build1, automatic), python-wadllib:amd64 (1.3.2-2, automatic), python-problem-report:amd64 (2.12.5-0ubuntu2.2, automatic), python-secretstorage:amd64 (1.0.0-1, automatic), python-simplejson:amd64 (3.3.0-2ubuntu2, automatic), python-lazr.uri:amd64 (1.0.3-1, automatic), python-launchpadlib:amd64 (1.10.2+ds-1, automatic), python-lazr.restfulclient:amd64 (0.13.3-1, automatic)
Upgrade: udisks2:amd64 (2.1.0-4, 2.1.0-4ubuntu0.1), python-psutil:amd64 (0.6.1-2ubuntu1, 0.6.1-3), python3-distupgrade:amd64 (0.205.4, 0.205.5), udisks:amd64 (1.0.4-8ubuntu1, 1.0.4-8ubuntu1.1), ubuntu-release-upgrader-core:amd64 (0.205.4, 0.205.5), libudisks2-0:amd64 (2.1.0-4, 2.1.0-4ubuntu0.1)
End-Date: 2014-03-10  19:38:05

any updates from the news group return an error

Code: [Select]

Starting group 1 of 31
Processing a.b.astronomy
Error: Code : Unexpected response: ''
Skipping group: alt.binaries.astronomy


Starting group 2 of 31
Processing a.b.blu-ray
Error: Code : Unexpected response: ''
Skipping group: alt.binaries.blu-ray
Im not sure how or what is causing the issue but thought I would see what suggestions I could get here
before doing a reinstall of ubuntu.

Thanks

[pupwiz]

Some digging and it seems to be only related to using NNTP Proxy switching back to one usenet provider has allow the script to run again.