Path: utzoo!utstat!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!uunet!netxcom!netxcom.iad-nxe.global-mis.dhl.com!elw
From: elw@netxcom.iad-nxe.global-mis.dhl.com (Edwin Wiles)
Newsgroups: news.software.nntp
Subject: Help with NNTP Client and RRN?
Keywords: nntp rrn help
Message-ID: <8431@netxcom.DHL.COM>
Date: 7 Oct 90 22:29:09 GMT
Sender: elw@netxcom.DHL.COM
Reply-To: elw@netx.com
Distribution: usa
Organization: NetExpress Communications Inc,. Vienna, VA.
Lines: 65

Hello!

	I need help figuring out what I've done wrong with the
	installation of RRN and NNTP in a client configuration.

	From the symptoms, I suspect it's something simple and
	stupid that I'm missing.

	We have Bnews running on an HP somethingorother with
	SCO Xenix and Excelan ethernet.  That same machine has
	an NNTP server set up on it that is known to work correctly.
	(We have TCP/IP connections to remote machines that are
	currently using it, so I know it still works.  No, I didn't
	install it on those machines.)

	Now I would like to add remote news reading capabilities
	to other machines of ours, most of which are PC clones
	running SCO Xenix Sys V 386.

	I obtained the latest NNTP from UUNET (1.5.10) and the
	latest RN as well (Patchlevel 47).  After some messing
	about with configuration, both compiled succesfully.

	I created the /usr/lib/news/server file, which points
	to the server machine.  I looked at the existing 
	/usr/lib/news/nntp_access file on our server, and
	found that it contained a single line:

		default read post

	I tried "rn" and got the long "newsnews" message.  When
	I pressed return to continue I got:

		socket:Permission denied.
		socket: Permission denied.

	Plus a message saying it couldn't reach the news server,
	but which indicated that it knew the right name.

	I then tried it as root, and got a segmentation violation,
	for which I could not find the core file.  I tried it again
	after adding "netex read post" to the nntp_access file on
	the server, and got the same results.  I tried it again
	changing the "netex" line to reflect our domain name of
	"netx.com", same problem.  Durring this, I tried the Pnews
	command as well, which failed for much the same reasons.

	Through adding a number to all the perror("socket")
	calls (e.g. perror("socket2")), I isolated the error to
	the "rresvport" call in "get_tcp_socket" near line 266
	in the common/clientlib.c file.

	I've gone through a number of configurations in
	common/conf.h, remaking both NNTP and RN (in that
	order) each time.

	If I haven't given enough info, ask.  I'd include
	the common/conf.h file and RN's config.sh file, but
	that would make this message rather long, and the
	answer might be quite simple.

	Any help will be appreciated!

					Thanks!
						Edwin Wiles.