| Bug ID |
8437
|
| Summary |
Windows PortableApps version of Wireshark tries to open .wireshark directory
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.8.5
|
| Hardware |
x86
|
| OS |
Windows XP
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 10193 [details]
Trace file showing SMB queries for ".wireshark"
Build Information:
Version 1.8.5 (SVN Rev 47350 from /trunk-1.8)
Copyright 1998-2013 Gerald Combs <[email protected]> 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 (32-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS
2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Jan 29 2013), with AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap, from the
PortableApps U3 device in drive E:.
Built using Microsoft Visual C++ 10.0 build 40219
--
Whenever I start or re-start live capturing from my work computer, Wireshark
tries to access ".wireshark" in my home directory. My home directory is located
on a NetApp filer and not on the local PC, so a series of SMB queries are
transmitted. Because this directory does not exist, the filer responds to each
query with "Error: STATUS_OBJECT_NAME_NOT_FOUND." Wireshark never creates a
file or directory named ".wireshark", even when preferences are changed and
saved.
I did not see this behavior prior to v1.8.5, and I believe .wireshark is used
by *NIX versions of Wireshark, not by the Windows version.
A trace file showing the SMB queries and responses is attached.
You are receiving this mail because:
- You are watching all bug changes.