Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!swrinde!cs.utexas.edu!usc!news.cerf.net!nic.cerf.net!elya From: elya@nic.cerf.net (Elya Kurktchi) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Trn and FreeBSD with WinNT Date: 24 Nov 1995 15:50:12 GMT Organization: CERFnet Lines: 23 Distribution: world Message-ID: <494pjk$8gm@news.cerf.net> NNTP-Posting-Host: nic.cerf.net Has anybody tried using trn with a remote windows NT news server? I always get connection closed socket errors. Users who are on my freebsd box are trying to read news via trn to a windowsNT nntp server and they always lose the connection. Examples of things that we reduplicate over and over again are: 1) While in trn, if you get as far as getting a newsgroup, you type "=" to get the listing of what's available to read. After the first article listing, it closes the connection with an unexpected socket error. 2) Say you don't type "=" and you just hit return to read whatever article comes up first, you also get the connection closed. 3) If you're in tin, it vaporizes your .newsrc file that trn created with all of the newsgroups. Anybody have any ideas? I'm on FreeBSD 2.0.5 running Trn3.6. Everything in trn has been configured to point directly to a windowsNT machine to read its news (remote nntp server). Thanks. Elya.