similar to: Authentication fails - 3.0.26a-0.9-1787-SUSE-SLES9

I only have limited Samba experience, and expect this is a silly mistake, but have been unable to find a solution I have installed Samba and Winbind on my desktop Linux (Debian) machine (SPARKSTONELX), aiming to unify logins with other windows machines accessing the PDC, again samba/Debian, with tdbsam password backend. All is well, joining the domain, and getting account details using wbinfo -u,

All - This evening I attempted to catch up on security releases and upgraded from SLES9 3.0.20 to 3.0.26a and found that getent only returns local UNIX groups and users. We are using winbind to communicate with an NT domain. The server has been restarted and services are running. Using wbinfo -u and -g does provide NT domain groups and users as expected and net rpc testjoin result is OK. I have

I portupgraded my samba domain server and domain member to 3.0.23b from 3.0.23 and found that the domain member was not accessible from workstations. The error message: \\HOSTNAME is not accessible. There are currently no logon servers available to service the logon request. In the log.winbindd of the domain member, I found: [2006/08/23 22:52:00, 0] nsswitch/winbindd.c:request_len_recv(517)

All - We are using 3.0.20a on SLES 9 and are trying to configure a member server for our NT4 domain. The wbinfo commands (-u and -g) show correct information. The getent commands (passwd and group) work fine also. If Samba is running without winbind, I can see the shares in the config file (net view \\xxxxxxxx) from a PC. With winbind running I get an error message about the computer name

We have setup a Samba member server using Winbind (3.0.14a and NT4). I am trying to "map" the NT Domain ids to root (root = admin administrator rdehn) but this seems to be ignored when I try and connect to a share. The "username map = /etc/samba/smbusers" line is in the Global section of smb.conf and testparm is OK. What am I missing? Is this not possible? Thanks in

I am using the following in my smb.conf on samba-3.0.28-0.el5.8 idmap domains = MYDOMAIN idmap config MYDOMAIN:backend = rid idmap config MYDOMAIN:base_rid = 998 idmap config MYDOMAIN:range = 998 - 49999 idmap uid = 998-20000 idmap gid = 998-20000 template homedir = /home/users/%U # template primary group =

Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =

Hello, when i send the SIGHUP signal to Samba, then Samba won't load the printers from CUPS. I need to shutdown Samba and start it again. Now when i'am running cupsaddsmb i got the following errors(this error occours in 3.5.x but not in 3.2.x): server-p:/# cupsaddsmb -H server-p -v edv01 edv02 edv03 Kennwort f?r root erforderlich, um ?ber SAMBA auf server-p zugreifen zu k?nnen:

Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =

After recent Samba updates to one of our SLES10 SP1 systems users who open and save Excel 2007 files end up with the Read-only attribute set on the file. I had this same problem with the 3.0.28 update and the only solution I found was to roll back to the previous version. My understanding was that 3.0.32 should fix this. Did I miss something? Are there smb.conf changes that need to be made

Hello all, Relevant info up front: Gentoo PC, using 2.6.38 kernel and Samba 3.4.12. I'm trying to get a FreeRadius instance working for our Windows network. To do so, I need a Linux box running Samba. I've installed and configured Kerberos, Samba and FreeRadius, and can get most things to work. I can get a Kerberos key using kinit, and "sudo net ads keytab list" shows me

We recently upgraded our PDC from Debian 4 to Debian 5. That entailed an upgrade of Samba from 3.0.24 to 3.2.5. Since the upgrade we've had a very specific problem connecting to shares on a commercial NAS running Samba 3.0.34. The problem happens when users try to connect to shares from standalone servers--e.g., Windows XP Pro boxes that we use for testing. From those boxes users should be

Hello, I saw on my member servers in winbindd.log sometimes the following message appearing: [2009/05/29 21:51:53, 1] rpc_client/cli_pipe.c:cli_pipe_validate_current_pdu(755) cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR received from host GENOME, pipe \lsarpc, fnum 0x7101! What does this error mean and how can I fix it? PDC and meber server are running 3.3.4.

I thought I had setup winbind correctly as I can login to my ubuntu 9.04 machine with domain users, but I am trying to get ntlm working with squid, and while testing winbind I get the following error. sudo wbinfo -a MBAG\\user%passwd plaintext password authentication failed Could not authenticate user MBAG\user%passwd with plaintext password challenge/response password authentication failed error

Hi, we have a problem with your Samba4 Domain Member as with Shares. when i would connect i got an Error. In Samba Logs it tells me ==> /var/log/samba/computerid349.log <== [2016/02/10 14:39:50.313835, 1] ../source3/printing/printer_list.c:226(printer_list_get_last_refresh) Failed to fetch record! [2016/02/10 14:39:50.313949, 1]

I'm testing out a new Samba setup to hopefully replace my aging Win2k domain. I've got some of it working: - My PDC (shadow) seems to be working on the CASA domain with an LDAP backend. - nss_ldap and pam_ldap are working on shadow - I can run wbinfo -u and get the user info from LDAP on shadow. - I can run wbinfo -a username%password and authenticate a user on shadow. I can run

Hello, we run samba 3.0.14a on FreeBSD. We recently upgraded our linux clients from FC2 to FC5. Now smbpasswd (on the client) does not work. We get the following error: "cli_pipe_validate_current_pdu: RPC fault code NT code 0x1c010002 received from remote machine sambaserver pipe \samr fnum 0x70f3! machine sambaserver rejected the password change: Error was : NT code 0x1c010002. Failed

Users are having trouble accessing Samba shares via winbindd in a NT domain. If the 'valid users' parameter for a share contained the user name for example as follows: valid users = DSP-John Then John who is a member of the DSP domain can access the share. If John is a member of a domain group called DSP-production, and the 'valid users' parameter is as follows: valid

Hey List- I've got 2 samba servers. PDC: FreeBSD 5.4; samba: 3.0.23 ? name: bugs member server: FreeBSD 6-stable; samba: 3.0.23 ? name: daffy note: config files are at the bottom of the email The PDC was running an older version, but I just upgraded and it didn't fix the below issue. The member server was running fine with the old smb.conf file, but I rebuilt the server and now it

Hi! I'm seeing quite a lot of messages like this one: [2024/06/07 06:52:47.259003, 1]\ source3/rpc_client/cli_pipe.c:550(cli_pipe_validate_current_pdu) source3/rpc_client/cli_pipe.c:550: \ RPC fault code DCERPC_NCA_S_OP_RNG_ERROR received from host tsrv! in log.wb-TSRV file on a regular domain member server acting as a file server. This happens with at least samba versions 4.21