From: Mike Fedyk <mfedyk@matchmail.com>
To: John Jasen <jjasen1@umbc.edu>
Cc: Mike Galbraith <mikeg@wen-online.de>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: reading your email via tcpdump
Date: Tue, 19 Mar 2002 10:11:30 -0800 [thread overview]
Message-ID: <20020319181130.GQ2254@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10203191009290.5694-100000@mikeg.wen-online.de> <Pine.SGI.4.31L.02.0203190915250.7550126-100000@irix2.gl.umbc.edu>
On Tue, Mar 19, 2002 at 09:20:25AM -0500, John Jasen wrote:
> > > 16:42:49.412862 10.0.0.101.netbios-dgm > 10.255.255.255.netbios-dgm:
> > > >>> NBT UDP PACKET(138) Res=0x1102 ID=0x54 IP=10.0.0.101 Port=138 Length=193
> > > Res2=0x0
> > > SourceName=T1H6I3 NameType=0x00 (Workstation)
> > > DestName=
> > > SMB PACKET: SMBunknown (REQUEST)
> > > SMB Command = 0x43
> > > Error class = 0x46
> > > Error code = 20550
> > > Flags1 = 0x45
> > > Flags2 = 0x4E
> > > Tree ID = 17990
> > > Proc ID = 18000
> > > UID = 16720
> > > MID = 16707
> > > Word Count = 66
> > > SMBError = ERROR: Unknown error (70,20550)
>
> This looks like standard SMB garbage. It probably repeats on a regular
> basis. From what I remember, I think it is a Windows box browsing
> the network trying to discover other SMB boxes, finding a 'master
> browser', and other such stuff.
>
> I see it all the time when there are Windows machines about, and I'm
> running tcpdump.
>
> I imagine that someone who knows better, such as the Samba guys, would be
> able to tell you exactly whats going on, and maybe some other interesting
> tidbits of information.
>
> (I hate SMB ... its really chatty ...)
That's not the problem part of the tcpdump output. The problem is that part
of an email previously read on the linux box (with no samba runing. (also,
no smbfs MikeG?)) showed up in the tcpdump output...
next prev parent reply other threads:[~2002-03-19 18:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 17:20 reading your email via tcpdump Mike Galbraith
2002-03-19 11:39 ` Denis Vlasenko
2002-03-19 9:19 ` Mike Galbraith
2002-03-19 14:20 ` John Jasen
2002-03-19 14:58 ` Mike Galbraith
2002-03-19 18:11 ` Mike Fedyk [this message]
2002-03-19 15:47 ` Andreas Dilger
2002-03-19 20:02 ` Mike Fedyk
2002-03-19 20:19 ` Richard B. Johnson
2002-03-20 0:34 ` Alan Cox
2002-03-20 1:00 ` Petko Manolov
2002-03-19 21:04 ` Urban Widmark
2002-03-20 7:46 ` Mike Galbraith
2002-03-19 18:56 ` Mike Galbraith
2002-03-19 18:52 ` Mike Fedyk
2002-03-19 19:16 ` Mike Galbraith
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=20020319181130.GQ2254@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=jjasen1@umbc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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).