Page 1 of 1
Question about NNTP and WG 3.2
Posted: Fri May 30, 2008 12:17 am
by Talonp
Hello everyone...I am running WG 3.2 and I have DNews server I had everything working and some news came into the BBS and now its not and I am unsure what I have done...so I thought maybe ask here seeing some of you are running the same setup and might be able to help
The error I am getting in the WG Server audit log is NNTP SERVER TIMEOUT
The DNews server shows the error: info: (19:25) NNTP closed unexpectedly {192.168.1.82} check dnews.log
and this is what is in the dnews.log:
29 19:25:04 1:warn: suck: BAD status code returned {400 Closing connection - timeout value exceeded } {192.168.1.82} {192.168.1.82}
29 19:25:04 :out: reject: {<3f8e7c96$0$26359$
a32e20b9@news.nntpservers.com>} {
someone@someplace.org} {Easiest Way To Make Money! Turn into 000! 10231 bytes} remote err: 400 Closing connection - time
29 19:25:04 1:info: wsock: (socket_read failed) The virtual circuit was reset by the remote side.
29 19:25:04 1:info: nntp: Closing socket chan[1] 248 192.168.1.82
I am sure I am just going brain dead but I have been messing with this for two or three days now so I must be over looking something.
Thanks for any and all help in advance.
Talonp
Re: Question about NNTP and WG 3.2
Posted: Fri May 30, 2008 7:55 pm
by Toyduck
Talonp wrote:Hello everyone...I am running WG 3.2 and I have DNews server I had everything working and some news came into the BBS and now its not and I am unsure what I have done...so I thought maybe ask here seeing some of you are running the same setup and might be able to help
The error I am getting in the WG Server audit log is NNTP SERVER TIMEOUT
The DNews server shows the error: info: (19:25) NNTP closed unexpectedly {192.168.1.82} check dnews.log
and this is what is in the dnews.log:
29 19:25:04 1:warn: suck: BAD status code returned {400 Closing connection - timeout value exceeded } {192.168.1.82} {192.168.1.82}
29 19:25:04 :out: reject: {<3f8e7c96$0$26359$
a32e20b9@news.nntpservers.com>} {
someone@someplace.org} {Easiest Way To Make Money! Turn into 000! 10231 bytes} remote err: 400 Closing connection - time
29 19:25:04 1:info: wsock: (socket_read failed) The virtual circuit was reset by the remote side.
29 19:25:04 1:info: nntp: Closing socket chan[1] 248 192.168.1.82
I am sure I am just going brain dead but I have been messing with this for two or three days now so I must be over looking something.
Thanks for any and all help in advance.
Talonp
I don't think you are doing anything wrong. Is DNews connecting properly without WG involved?
How long is their 'eval' version? - still good?
I don't use dnews, but I tried connecting to the newserver, and also received timeouts (but I do have a slow connection at my office).
Posted: Fri May 30, 2008 10:02 pm
by Talonp
Yeah the eval is still good and Dnews was working with WG and then died, the best I can tell its all correct but I am uninstalling DNews and starting over to be sure. Who needs sleep hehe
Thanks for the help

Posted: Sat May 31, 2008 2:27 am
by Toyduck
Talonp wrote:Yeah the eval is still good and Dnews was working with WG and then died, the best I can tell its all correct but I am uninstalling DNews and starting over to be sure. Who needs sleep hehe
Thanks for the help

You could try running DNews in standalone mode (it does that with some changes to the config file) and see how it works, if it does work properly it would help point to communication problems with WG.
Posted: Sat May 31, 2008 4:29 pm
by Talonp
Thats a good point, I will try that thanks Toyduck

Posted: Mon Jun 02, 2008 4:45 pm
by Talonp
Ok got it working it was the DNews configuration, needed to set the bbe as a DFeed ...but its working
Another question, does anyone know why WG3.2 changes the dates of the posts as they come in? three years of posts and all have todays date on them hehe not a big deal but would be nice if it had the correct dates.
Thanks
Talonp
Posted: Tue Jun 03, 2008 1:37 am
by Malakai
Any possible way you can write a tutorial on how to set up dnews, once you get it working correctly? And which version do you have to buy to push/pull the feeds to one bbs?
Posted: Tue Jun 03, 2008 1:51 am
by Talonp
I was planning on doing that after I get done working all the bugs out

Posted: Tue Jun 03, 2008 9:51 pm
by Toyduck
Talonp wrote:Ok got it working it was the DNews configuration, needed to set the bbe as a DFeed ...but its working
Another question, does anyone know why WG3.2 changes the dates of the posts as they come in? three years of posts and all have todays date on them hehe not a big deal but would be nice if it had the correct dates.
Thanks
Talonp
Yes, WG is adding the date it actually received the messages; at least I believe it does. I noticed that when I used to run a news feed, unfortunately at the time the news feed I had did not work on it's own. So I was never entirely sure if it was WG or the news program.
If you have luck with this news server, let us know.
TD
Posted: Tue Jun 03, 2008 11:20 pm
by Talonp
I will keep you posted, I have the WG server receiving news feeds without a problem and my Dev server is testing feeds from fido and qwk networks now but I am still working on the Time Date issues

Posted: Wed Jun 04, 2008 3:24 pm
by Toyduck
Talonp wrote:I will keep you posted, I have the WG server receiving news feeds without a problem and my Dev server is testing feeds from fido and qwk networks now but I am still working on the Time Date issues

There are no options to set for importing news that affect the date used, and one would assume it would be a straightforward pass-through to WG. I always thought the news server I was using was changing the messages to my local system time/date, but I never found how to configure that or change it.
I might have to take the time to DL Dnews and look it over.
Posted: Thu Jun 05, 2008 3:00 am
by Talonp
Well gone through all the configs in DNews and talked to there Techs about the issues and its not DNews...all the feeds are on the DNews server with the correct dates and times....so some how and some way WG is changing the dates and times when the feeds are coming in...back to testing
