linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Miguel González Castaños" <mgc@tid.es>
To: linux-admin@vger.kernel.org
Subject: weirds traces
Date: Tue, 05 Oct 2004 17:00:40 +0200	[thread overview]
Message-ID: <4162B718.5000905@tid.es> (raw)

Dear all,
 
 I am trying to connect to a socket at 20002 port where an application 
is listening to.

 I am using ethereal to sniff what is going back and forth to that 
server. From one linux box it takes 5 secs to receive and ACK and from 
another one only 1 sec. The latter behaviour is the normal from any box 
(Windows & linux) I have tried.  I issued a telnet from both linux boxes 
and both get the ACK but the traces are a bit different. Mainly I 
realised that I keep on getting the following two traces:

1623.286532  10.95.84.67 -> 10.95.84.68  NBNS Name query NBSTAT 
*<00><00><00><00><00><00><00><00><00><00><00><00><00><00><00>
1623.286563  10.95.84.68 -> 10.95.84.67  ICMP Destination unreachable

Anyone can shed any light on this?

Regards

Miguel


                 reply	other threads:[~2004-10-05 15:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4162B718.5000905@tid.es \
    --to=mgc@tid.es \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).