Wireshark-bugs: [Wireshark-bugs] [Bug 3386] New: WINS multicast packets not captured
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 2 Apr 2009 07:34:10 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3386

           Summary: WINS multicast packets not captured
           Product: Wireshark
           Version: 1.0.4
          Platform: Other
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: Major
          Priority: High
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: f.walther@xxxxxxxxxx


Build Information:
Version 1.0.4 (SVN Rev 26501)

Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt 1.4.1, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.

Running on Windows Server 2003 Service Pack 2, build 3790, with WinPcap version
4.0.2 (packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.

Built using Microsoft Visual C++ 6.0 build 8804

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Wireshark v 1.0.4
WinPCap v 4.0.2
Windows Server 2003 / Standard Edition / Service Pack 2

WINS multicast packets (that HAD been on the wire) were NOT captured by
Wireshark.

There had been a multicast storm; switches had terrific CPU load; backup
streams at night failed because of inacceptable latency caused by the WINS
multicasts.

Wireshark based on LINUX PC could "see" the WINS multicast packets.
Wireshark based on the Windows Server 2003 could not.

Does anyone know something about this ?

Is this an known bug, would it be fixed with current version Wireshark 1.0.6 ?

Frank R. Walther


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.