similar to: Samba 3.0.23c-1.fc5 problem - groups

Hi, I've just updated (using yum under fedora 5) to the latest version of samba and am now encountering a major problem with samba. Whenever I attempt to access shares (don't have printers or other such non disk shares) the access fails (after prompting for password, and performing some level of authentication, it notes if no password is entered that Anonymous login successful).

Hi there, I?m using FC5 and since I updated to Samba 3.0.23c-1.fc5 I?m not able to access some shares from the workstations. Lookin at the log, i found this error: [2006/09/29 19:34:27, 0] lib/fault.c:fault_report(41) =============================================================== [2006/09/29 19:34:27, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 3646

I have a file server with two shares accessible to 2 different groups. After the last update ( from debian 2:3.2.5-4 to 2:3.3.2-1 ) i cannot any more access ONLY ONE of the two shares and I can't understand the reason! Can anyone hel me? I'm getting mad! Thanks Giorgio from smb.conf: [documenti_movi] path = /home/documenti_movi valid users = @staffmovi read

Hi, When I use "valid users" in smb.conf to limit access on my share, I have this message with smbclient : [global] workgroup = MYDOM domain master = no local master = no security = user passdb backend = ldapsam:ldap://x.x.x.x:389 ldap admin dn = cn=admin,dc=company,dc=com ldap suffix = dc=company,dc=com ldap user

Are all versions of openldap compatible with Samba 3.0.23c? If no, please let me know the least version of openldap which I need to have for Samba 3.0.23c working? Thanks, Dil

Hello, I have upgraded my gentoo samba server to version 3.0.23c using the ebuild script on bugs.gentoo.org that was suggested top me on this list. I am having some trouble accessing my "public" folder and I have a "valid users = +users" for that share. I have tried using "valid users= +Solidus\users" as well and that does not work. The first way seems to work just

Hi, In 3.0.23 and 3.0.23c in our domain controlled by samba with an ldapsam backend when I try to add a machine to the domain I now get this message: [2006/10/04 12:08:03, 0] passdb/pdb_interface.c:pdb_new_rid(1067) 'algorithmic rid base' is set but a passdb backend without algorithmic RIDs is chosen. Please map all used groups using 'net groupmap add', set the maximum

Hi people. I use centos on many my servers and they are running samba which comes with centos: samba-3.0.10-1.4E.9 From samba-3.0.10 to 3.0.23c many thnigs in code had change. Many bug fixes etc., code rewrote (for example oplock in later version of samba than 3.0.10). RedHat people don't have made a full of backports to their samba, only security things. So I have question, what do

Hello! I've read various information on the web, including the HOWTO on how to configure Printers, but I am struggling with making my printers publicly printable. My samba server is joined to a W2K3 domain. How do I configure it to be printable by anyone, even a user/system not part of the domain? Here is my current config: [printers] comment = All Printers path =

We built a new server running Samba 3.0.23c and configured it to replace our corporate PDC that was running Samba 3.0.7. The PDC uses tdbsam and has the "admin users" directive defined. All user accounts were copied to the new server. Using the output of "net groupmap list" from the old server we mapped the windows accounts and SIDs to their unix group counterparts on the

I can't seem to get a Windows XP Media Center Edition system to see a very simple print share. [global] workgroup = HOME realm = SHAUN server string = Samba Server security = SHARE encrypt passwords = No log file = /var/log/samba/%m.log max log size = 50 dns proxy = No wins support = Yes valid users = shaun admin users = shaun read list = shaun write list = shaun printer admin

Hi there, Since upgrading our debian sarge boxes to 3.0.23c, we have found that we are unable to connect to shares using the official hostname of the servers (short or fully qualified) but can still use its netbios aliases (again, short or fully qualified). As nothing else has changed in our configuration, I think that the change of behaviour is down to the newer release and can find nothing in

Hi everyone! I have some trouble with samba 3.0.23 as PDC for NT4 workstations with SP6a. I have upgraded from samba2. 1. The ntconfig.pol from the netlogon-share does'nt work. I get a prf1.tmp in the User-Profile-Folder and the policy wouldn't mix to the registry. In the Event-Log I found an entry "RegLoadKey ist mit dem Fehler 87 f?r C:\WINNT\Profiles\aba\prfD.tmp

I've recently rebuilt a samba server and noticed this problem keeps coming up with groups. If I use a user in smb.conf valid users = me It works and I'm able to access the shared drive. There are no messages in the log file. However if I use group valid users = @admin I can't access the drive and I get a lot of errors in my messages file. Here is some of the errors.

Hi, We have been running samba file server about 2 years without this problem. The problem appeared at the same time on our debian and centos servers. Not sure if it's related to any updates on our windows AD servers. Debian Squeeze sernet-samba-3.5.8-27 Centos 5.5 samba3-3.5.5-43.el5 Use Active Directory for user login authentication Use uid/gid from ldap The reason we still want winbind

Hello, I have just performed a yum update on my Fedora 5 machine, which I think included a samba update, and I cannot connect from WinXP to the shares defined on Fedora. When I select the samba server from WIndowsXP, a dialog box prompts for the userid and password. When userid and password are entered the dialog box just redisplays and I am not logged on, no matter how many time I try. I

Hi all, I have a Samba 3.0.20b installation on a Redhat 9 system running as PDC for a Windows Domain. I now would like to move the PDC funktionality to an existing Debian Sarge system running Samba 3.0.23c and then decommision the Redhat system. I did search for information on how to do this but all the information that I could find seems to deal with Samba 2.x PDCs since the MACHINE.SID file is

We had to power down all servers today for electrical maintenance in the building and for some reason I began having access problems related to the valid users lists when power was restored. The dialog from the 'Samba-3.0.23 broke my network' thread seemed as if it might be related even though I had not performed any software upgrade so I tried adding the group mappings as discussed in

Hello, I am running samba on a machine running fedora 5. I did not know the system was configured to automatically update the system via cron, and when it put the new samba on last night, seems to have broken things. It is coredumping now whenever a user tries to authenticate. Our system is set up with user level security which i manage via smbpasswd so there are no windows domains involved. The

I have the winbind login working on FC5 but now logins to local accounts cannot authenticate. My config files are here: http://www.pigeonnier.org/nsswitch.conf http://www.pigeonnier.org/pam.d/ http://www.pigeonnier.org/krb.conf Again, if I try to ssh in as a user that exists only as a local account on the remote host, I am rejected. User msh is -not- a AD account and only exists on the FC5