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?
Thanks!
/usr/sbin/tcpdump -s 0 -w liz <
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=[Windows
Server 2008 R2 Enterprise 6.1]
From: derrell.lipman at gmail.com [mailto:derrell.lipman at gmail.com] On Behalf Of Derrell Lipman
Sent: Monday, June 21, 2010 11:43 AM
To: Rechtien, Elizabeth J
Cc: samba-technical at lists.samba.org
Subject: Re: smbc_open error
On Mon, Jun 21, 2010 at 12:25, Rechtien, Elizabeth J <Elizabeth.Rechtien at stlukes-stl.com<mailto:Elizabeth.Rechtien at stlukes-stl.com>> wrote:
I'm still having this issue. I think I need to re-phrase my question. I know how to run this command command line but the tcpdump needs to be run within my C code when the smbc_open is called. Does that work with what you have below?
No, tcpdump is not run from within your C code. tcpdump is a command-line utility that monitors a network interface and saves what it sees going in and out on the wire. You run tcpdump in a terminal window and while it's running, in a different terminal window, run your smbclient command that (in your original message) you said works properly. After smbclient has succeeded, kill tcpdump, which will save the network traffic in binary format to the file that you specified after the -w option.
Next, run tcpdump again, using a different output file name, and then run your libsmbclient application that fails, and then again kill tcpdump.
You've now got two files with the output of tcpdump, one showing the network traffic of a working access to the file, and one showing the network traffic of a failing access to the file. Attach both of those files to the bug report, and I'll be able to compare them to see what smbclient is doing that libsmbclient isn't (or vice versa).
Derrell
Thanks,
Liz
From: Rechtien, Elizabeth J
Sent: Tuesday, March 30, 2010 9:29 AM
To: 'Derrell Lipman'
Cc: samba-technical at lists.samba.org<mailto:samba-technical at lists.samba.org>
Subject: RE: smbc_open error
How do you run this command line?
/usr/local/samba/bin/smbclient //xx.xx.x.x/XXX -U tok>
params.c:OpenConfFile() - Unable to open configuration file "0":
No such file or directory
/usr/local/samba/bin/smbclient: Can't load 0 - run testparm to debug it
session setup failed: NT_STATUS_LOGON_FAILURE
Thanks for your help!
From: derrell.lipman at gmail.com<mailto:derrell.lipman at gmail.com> [mailto:derrell.lipman at gmail.com<mailto:derrell.lipman at gmail.com>] On Behalf Of Derrell Lipman
Sent: Thursday, March 25, 2010 8:30 PM
To: Rechtien, Elizabeth J
Cc: samba-technical at lists.samba.org<mailto:samba-technical at lists.samba.org>
Subject: Re: smbc_open error
On Thu, Mar 25, 2010 at 16:07, Rechtien, Elizabeth J <Elizabeth.Rechtien at stlukes-stl.com<mailto:Elizabeth.Rechtien at stlukes-stl.com>> wrote:
Does anyone have information on getting an error when calling smbc_open? A file or directory in the path name does not exist. This same file can be pulled from the same server using command line samba commands. This code using libsmbclient.h has worked fine but now seems to be having an issue with a Windows 2008 server.--
Please describe this problem in a new bug report in bugzilla. To the bug report, attach two packet traces: one which shows the command working, using the command line tools to copy the file; and one which fails, using your libsmbclient application. The packet traces should be created with a command line like this:
tcpdump -s 0 -w outputFileName
Thanks,
Derrell
--
"There are two ways of constructing a software design.
One way is to make it so simple that there are obviously no deficiencies.
And the other way is to make it so complicated that there are no obvious deficiencies."
C.A.R Hoare
DISCLAIMER: The contents of this e-mail, including any attachments, contain information which may be confidential, legally privileged, proprietary in nature, or otherwise protected by law from disclosure, and is solely for the use of the intended recipient(s). If you are not the intended recipient, any use, disclosure or copying of this e-mail, including any attachments, is unauthorized and strictly prohibited. If you have received this e-mail in error, please notify us via return e-mail and immediately delete all copies of it from your system. Any opinions either expressed or implied in this e-mail and all attachments, are those of its author only, and do not necessarily reflect those of St. Luke's Hospital.
--
"There are two ways of constructing a software design.
One way is to make it so simple that there are obviously no deficiencies.
And the other way is to make it so complicated that there are no obvious deficiencies."
C.A.R Hoare
DISCLAIMER: The contents of this e-mail, including any attachments, contain information which may be confidential, legally privileged, proprietary in nature, or otherwise protected by law from disclosure, and is solely for the use of the intended recipient(s). If you are not the intended recipient, any use, disclosure or copying of this e-mail, including any attachments, is unauthorized and strictly prohibited. If you have received this e-mail in error, please notify us via return e-mail and immediately delete all copies of it from your system. Any opinions either expressed or implied in this e-mail and all attachments, are those of its author only, and do not necessarily reflect those of St. Luke's Hospital.