derrell.lipman at unwireduniverse.com
Mon Jun 21 15:17:51 MDT 2010
On Mon, Jun 21, 2010 at 16:00, Rechtien, Elizabeth J <
Elizabeth.Rechtien at stlukes-stl.com> wrote:
> Okay, I found tcpdump on the server but I get this error. If I run it
> without –s, it doesn’t write to the file. Can you help?
> /usr/sbin/tcpdump -s 0 -w liz <
Was tcpdump running in a separate window from the smbclient command?
I don't see the smbclient command shown here at all. You initially said that
you could access the file properly using the samba tools, which I assume to
> params.c:OpenConfFile() - Unable to open configuration file "0":
> No such file or directory
> smbclient: Can't load 0 - run testparm to debug it
> Domain=[W8PSCIMAGE2] OS=[Windows Server 2008 R2 Enterprise 7600]
> Server 2008 R2 Enterprise 6.1]
I think before we worry about libsmbclient issues, it's probably worthwhile
for you to work with the samba-users list to get things working using the
client tools. Once you've got that working, and can generate a network dump
using tcpdump, then it makes sense to go back to your app with libsmbclient
to see what's up with it.
The -s 0 option to tcpdump tells it to save an unlimited amount of data per
packet. The default is to truncate the packet at something less that what we
need to track down problems.
The -w liz option tells it to save the binary network dump in a file called
More information about the samba-technical