Any progress made on this ?
I'm facing the same bug on Debian Wheezy, Samba version 3.6.6.
Windows 7 clients.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/526464
Title:
** Attachment added: crystal3.log.old
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1917956/+files/crystal3.log.old
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
/var/log/auth.log file.
** Attachment added: auth_log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1915502/+files/auth_log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
smb.conf file.
** Attachment added: smb.conf
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1915503/+files/smb.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: crystal3_2011-01-25_1345.pcap
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1912733/+files/crystal3_2011-01-25_1345.pcap
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
** Attachment added: fs1_2011-01-25_1345.pcap
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1912734/+files/fs1_2011-01-25_1345.pcap
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Failure vs Success screenshot. Failure is left screen and success is
right screen.
** Attachment added: wireshark_auth_screenshot.png
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1912735/+files/wireshark_auth_screenshot.png
--
You received this bug notification
Samba log showing failure and success that match up with the wireshark
dumps.
** Attachment added: crystal3.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1912741/+files/crystal3.log
--
You received this bug notification because you are a member of Ubuntu
Server
@Surbhi,
I uploaded two additional wireshark traces. These traces are for the
same two machines, but from an earlier date. The two wireshark traces
show sucessful auths and failures for both users(service_bhavnacrysta
and crystaluser).
I also uploaded the samba log for this time period. The
@Joseph Salisbury,
Can you attach the wireshark trace in case of a failure _and_ in case of
success. We need to find out the difference in the data that the windows client
is sending to the samba server. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server
Comparing the success and the failure logs attached by the bug reporter,
I can see the following difference:
Success-log:
[2010/03/11 08:05:57, 3] libsmb/ntlmssp.c:ntlmssp_server_auth(739)
Got user=[someuser] domain=[SOMEDOMAIN] workstation=[SERVER3] len1=24 len2=24
[2010/03/11 08:05:57, 2]
** Attachment added: crystal3_2011-02-08_1000.pcap
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1901891/+files/crystal3_2011-02-08_1000.pcap
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
** Attachment added: fs1_2011-02-08_1000.pcap
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1901896/+files/fs1_2011-02-08_1000.pcap
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Two wireshark traces were uploaded. The system crystal3 is the Windows
server. The system fs1 is the Ubuntu server.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
https://bugs.launchpad.net/bugs/526464
Title:
@Surbhi, unfortunately increasing the log level to 10 caused a
production outage. The high amount of logging overloaded the system and
made it unresponsive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
@Joseph Salisbury, yes please do attach the logs with the log level set
to 10. It will give us more voluminous output.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
https://bugs.launchpad.net/bugs/526464
Title:
@Surbhi, We have logs with the log level set to 5. Will setting the
log level to 10 provide additional valuable data? We would like to
prevent any changes, since this is a production environment, and
changing the log level requires a maintenance window.
--
You received this bug notification
@Joseph Salisbury, can you please attach the relevant logs in /var/log/samba/
after doing the following:
1) In /etc/samba/smb.conf set the debuglevel =10 (in the
Debugging/Accounting section, before log =something)
--
You received this bug notification because you are a member of
@ Surbhi, thanks for the feedback. I don't see debuglevel in the
smb.conf file. Is the parameter log level = N the same option? In
the previous logs we had this set to 5. I can see if we can increase
it to 10. If debuglevel and log level are different, I can see if
we can add that
We performed a full Wireshark trace when the authentication failure
happens.
It looks like all successful authentications send packets to the domain
controller and perform an LDAP searchRequest. However, when the failures
happen, we don't see any data being sent to the Windows domain
controllers.
We disabled the AppArmor profile, but there was no effect on this error.
We reviewed the domain controller logs when one of these authentication
failures happened. There was not entry in the domain controller logs
stating that the authentication was attempted. For all successful
This also looks suspicious too (dmesg.log):
[14076616.248406] audit(1294765455.905:2753): type=1503
operation=inode_permission requested_mask=w:: denied_mask=w::
name=/var/run/samba/winbindd_privileged/pipe pid=23931
profile=/usr/sbin/cupsd namespace=default
I wonder if AppArmor profile for
That is an AppArmor message from the AppArmor cups profile, not a samba
one.
I doubt it's related, but you could try and temporarily disable the
AppArmor cups profile to make sure.
Instructions for doing so are here:
https://wiki.ubuntu.com/DebuggingApparmor
--
You received this bug
This has happened again. Since this is Hardy, there is no apport-
collect. The following information has been added to the bug:
1) uname -a uname-a.log
2) dmesg dmesg.log
3) sudo lspci -vvnn lspci-vvnn.log
4) cat /proc/version_signature version.log
Please let us know if any additional data
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791464/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: lspci-vvnn.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791465/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: uname-a.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791466/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791467/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
One additional detail. The following error was reported on the
application side:
destination file error: CrystalEnterprise.DiskUnmanaged: Access is
denied.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Has any progress been made on this? Any chance Lucid Lynx doesn't have
this bug?
--
intermittent authentication: check_ntlm_password: Authentication for user
[someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED
https://bugs.launchpad.net/bugs/526464
You received this bug
** Changed in: samba (Ubuntu)
Status: Incomplete = Confirmed
--
intermittent authentication: check_ntlm_password: Authentication for user
[someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED
https://bugs.launchpad.net/bugs/526464
You received this bug notification because
Could you attach a log with a successful identification ?
Looks like it's password that is failing, which doesn't make sense if it's
intermittent:
check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED
with error NT_STATUS_ACCESS_DENIED
--
intermittent authentication:
What version of windows are the clients running that are giving you
fits?
Regards
chuck
** Changed in: samba (Ubuntu)
Importance: Undecided = Medium
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
intermittent authentication: check_ntlm_password: Authentication for user
Windows 2003 Server Standard SP2.
--
intermittent authentication: check_ntlm_password: Authentication for user
[someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED
https://bugs.launchpad.net/bugs/526464
You received this bug notification because you are a member of Ubuntu
Server
34 matches
Mail list logo
