[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: [leafnode-list] Delayed answers from my leafnode-server
I know the problem with the missing /etc/hosts-entry. My client has an
entry in this table.
I dont think that a problem with the network-connection exists because
the local connection (telnet 127..... 119) has the same problem. I think
it is a problem with one leafnode-database (eg articles...). I have
searched many pages in the www and articles in the usenet but i dont
find a solution or a tip. The only usable tip that i have found is
"fetchnews -f" to rebuild the group-database.
If my ideas are wrong or "i think incorrect (or in the wrong way)",
please correct me.
I dont want to use "de.comm.software.newsserver" bacause i'm courageous
> -----Ursprüngliche Nachricht-----
> Von: Matthias Andree [mailto:ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx]
> Gesendet: Dienstag, 8. Juli 2003 23:58
> An: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Betreff: Re: [leafnode-list] Delayed answers from my leafnode-server
> "Peter Reimer" <punky@xxxxxx> writes:
> > If i connect leafnode from an other pc (eg with outlook...
> Or slrn), i
> > must wait some minutes for the connection. I've tried to connect
> > leafnode from the local system. The result of "telnet
> localhost 119"
> > and "help" is nothing. If i wait some minutes and enter
> again "help",
> > i get the normaly help-screen. The newsreader on my other
> machine says
> > "the newsserver dont answer". Also on this machine: i wait some
> > minutes and it works fine...
> I see two possible problems:
> 1. DNS. Leafnode tries to resolve the client's IP to a hostname.
> 2. ident, also known as AUTH or RFC931. inetd on FreeBSD uses
> tcp_wrappers by default, and tcp_wrappers MAY conduct
> ident lookups.
> I suspect a DNS problem. To verify this, either try to
> connect from your server, giving 127.0.0.1 as the address, or
> you can put the client's IP into /etc/hosts, like (adjust the
> 192.168.4.2 myclient.reimer.example.org
> If leafnode allows quick connects, then you've found the problem.
> A definitive answer might be obtained with tcpdump that you
> run on the server. Watch for outgoing TCP port 113 from
> server to client, and watch for outgoing UDP port 53 from
> server to anywhere. You may need to run two tcpdump
> instances, one for your LAN interface (fxp0 or xl0 or
> something), one for your external interface (tun0 or something).
> Let me know what you find.
> > Thanks and again: sorry... My english...
> If it wasn't for the hen-and-egg problem, I had suggested to
> use the de.comm.software.newsserver newsgroup. ;-)
> Hope that helps,
> Matthias Andree
> leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list
> for leafnode To unsubscribe, send mail with "unsubscribe" in
> the subject to the list
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list