Bug 5371 - FreeBSD entirely OpenLDAP auth access to root (list of available shares)
Summary: FreeBSD entirely OpenLDAP auth access to root (list of available shares)
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.28
Hardware: Other FreeBSD
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-03 01:50 UTC by Sergey
Modified: 2008-04-17 03:56 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey 2008-04-03 01:50:48 UTC
I have FreeBSD (6.2 RELEASE #0) server with switched to OpenLDAP (2.3.41) both system and samba authentification.

When I try to connect to root of file server with smbclient (results are similiar for smbclient on the same server, smbclient on another server with FreeBSD 6.3 and for my workstation with Gentoo Linux), I get the following error:
$ smbclient //localhost/ -U user
Password:
Domain=[SAMBA] OS=[Unix] Server=[Samba 3.0.28]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

When I try to mount share directly everything works OK:
$ smbclient //localhost/test -U user

Listing of available shares
$ smbclient -L 127.0.0.1 -U user
also works OK.

The same config (differs only in declaration of shares) on the server with FreeBSD 6.3 and authorization in OpenLDAP only for Samba users (system auth is default) works OK.

WTF?
Comment 1 Gerald (Jerry) Carter (dead mail address) 2008-04-03 07:10:44 UTC
If you want to list shares, use "smbclient -L server".  The syntax you 
list is invalid.
Comment 2 Sergey 2008-04-03 08:29:23 UTC
But from wondow$ workstation (2003 server) attempt to get access to file server by entering
'\\samba\' in explorer fails.
But access to '\\samba\test' works.

And nothing is written in logs. That is why I described configuration on smbclient.
Comment 3 Sergey 2008-04-17 03:56:00 UTC
It was mine error.
After correct restart of services on server everything works as it should do.