GNOME Bugzilla – Bug 691863
Not asking for credentials when anonymous pass fails
Last modified: 2016-01-22 14:49:51 UTC
So I've been debugging samba login issues with user running Ubuntu 12.10 (gvfs-1.14.0, libsmbclient-3.6.6) connecting to a NAS box running Samba 3.0.32. Going through Nautilus smb-browse, clicking the share icon (anonymous mode) will return an error "Failed to mount Windows share" without any credentials prompt. Manually specifying user in the URI works. Log excerpt: > Queued new job 0x1b92830 (GVfsJobMount) > smbc_stat(smb://nas/homes) > Connecting to 192.168.1.12 at port 445 > session request ok > Doing spnego session setup (blob length=58) > SPNEGO login failed: Logon failure > session setup ok > send_reply, failed: 1 Things to do: - add more debugging prints like we do in smb-browse to see what error codes are returned - return more specific error, fix /* TODO: Error from errno? */ - try to reproduce locally
commit 5ca4ebdac6bc5c6d87802ae527bb7880d81e823c Author: Tomas Bzatek <tbzatek@redhat.com> Date: Fri Feb 8 16:35:27 2013 +0100 smb: More verbosity for easier debugging This adds more debugging output for both smb and smb-browse backends and also brings more verbosity for user-visible error messages. Changes made to be able to debug weird samba issues remotely: https://bugzilla.gnome.org/show_bug.cgi?id=691863 This will be included in the 1.15.4 release and hopefully we would be able to reveal more details.
Also worth noting is an issue I've come across today. My system hostname didn't correspond with forward nor reverse DNS records and that made samba confused. Apparently resolving netbios name led to translation to a hostname that was then resolved through DNS, resulting in outdated IP address which libsmbclient then used for connecting to the server. That timed out eventually and led to an error while trying to list workgroup members (smb-browse mode). Activating GVFS_SMB_DEBUG=99 brought more messages from libsmbclient that were repeatedly printed out until the timeout: > s3_event: Added timed event "tevent_req_timedout": 0x7f5518009d90 > s3_event: Schedule immediate event "tevent_queue_immediate_trigger": 0x7f55180095f0 > s3_event: Run immediate event "tevent_queue_immediate_trigger": 0x7f55180095f0 > s3_event: Destroying timer event 0x7f5518009d90 "tevent_req_timedout" This is samba-3.6.9, standalone smbclient failed with NT_STATUS_UNSUCCESSFUL.
Any update on this Tomas, or can it be closed?
Let's close this as obsolete...