similar to: net group members ?

Ello -- For the past few months our Samba installation, currently at Version 3.0.28 has filling the log. file with [2008/04/17 13:25:30, 0] smbd/notify_inotify.c:inotify_handler(234) No data on inotify fd?! This is started to happen almost weekly and it continues to output those lines until the log partition is full, then leaves a single process spiked to 100% until I kill it. There is

Hello, We have a RHEL4 x64 running for 3 years, which is a samba member server integrated with a AD domain without any problems (we was using samba-3.0.10-1.4E.6). Last Saturday we performed an entire server update, applying all RHN available patches. Everything is running fine, except for winbind service which has a strange behavior: often we are receiving some errors at logs, and the

Installed Samba 3.0.10 via 'pkgadd' on Solaris 2.6 workstation s080 (137.223.31.80) - previously running Samba 2.2.8 which has worked for a long time. Samba 3.0.10 smb.conf file - changed to security =DOMAIN from SERVER at 2.2.8 version password server = 137.223.33.45, 137.223.33.72 - these are DCs # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date:

I have configured winbind on a Linux file server, connecting to a Samba PDC. When I run wbinfo -g, I can see the group "domain users". On the other hand, when I run getent group, I do not see this group. Apart from a few other groups, all groups are visibile in both wbinfo -g and getent group. When running for the first time wbinfo -u, getent passwd and wbinfo -g, I got the results

Packet send failed to 62.101.92.90(137) ERRNO=Network is unreachable [2004/05/03 10:27:45, 0] nmbd/nmbd_packets.c:reply_netbios_packet(975) Hi list, once again looking for some good advice. I apologize for the long email and for the mistakes I could have done. I'm running Samba 3.0.2-6.3E on White box linux 3.0 kernel 2.4.21-4.EL (clone of Red Hat EL 3.0), the environment is a Win 2k ADS

Hello All, I don't know how, but I managed to get my no logon server found error to go away, but now I am experiencing another problem. When I run "net join ads -d 3" I get the following error message. I know it's authenticating, because if I enter an incorrect password it says "The username or password was not correct." So it's accessing the correct server, but

Hi! I've set up a Samba server (running winbind) as a Win domain member server. Users authenticated from win domain and mapped to NIS uids and gids. Everything was working well, but the next morning winbind stopped to respond. I reset it, so now I get wbinfo, ypbind (ypcat) results ok as before, but users suddenly cannot authenticate any more. My <client>.log files are empty,

Hello, Occasionally when I perform "net rpc group members (group a)," I get a timeout. When I do "net rpc group members (group b)," I always get a timeout. I get the following error: [2007/01/05 16:36:18, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790) rpc_api_pipe: Remote machine 127.0.0.1 pipe \samr fnum 0x72cdreturned critical error. Error was Call timed out: server did not

I'm exeperiencing a strange ntlm_auth problem: I'm running two domain with a trust; the trusting one, (EUFEMIA with the PDC Beatrice) uses the WINS facility of the trusted one (LETTERE, PDC Alice). Users of EUFEMIA and LETTERE alike have a successful logon to Beatrice. LETTERE users do authenticate in Beatrice with ntlm_auth. EUFEMIA users do not: beatrice:/home# ntlm_auth --username

Hi all. Yesterday morning, we had a problem with our Samba box (3.0.20b-SUSE), traced to the root(/) partition becoming full. Upon restart, it was later reported that users at another office (trusted domain), could not access our server. Everything had been running smoothly for over 5 months. Running 'wbinfo -u/-g' returns a list of users/groups from the local domain, prefixed with

Hi We have a problem with samba (winbind) when we enable idletimeout on the OpenLDAP servers. If it is set we sometimes get an error: mhansen@scenic32:~> smbclient -Umhansen //cups/p6 Password: session setup failed: NT_STATUS_IO_TIMEOUT The log entries (log.wb-DOMAIN)on the DOMAIN MEMBER server (cups in this case) are: [2006/11/20 14:24:07, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790)

I upgraded from 2.2.12 (and kept my tdb files -- it is a possibility that this is a part of my problem, but let me run it by you anyway). I'm attempting to do a domain trust between my production domain and a test domain. However, on my production domain, I have the following problem: # /products/samba/bin/net rpc trustdom list -U novosirj Password: Trusted domains list: NWK-DEV

Samba occasionally fails with the following. I have seen many questions regarding this but no answers unfortunately. I am wondering what the setting is where I can increase this time out value of 10000 milliseconds in case that specific request is just slow. This is called many times a day and only just occasionally fails. I have looked through the entire manual for smb.conf and can't find a

Hello When I perform the "net rpc trustdom list" command I get the "couldn't enumerate accounts" error. I use LDAP as passdb backend with approximately 30000 accounts. If I run the command, I can see from my LDAP logs that it tries to list every account on the LDAP server. Therefore the "net rpc trustdom list" command times out. Is this normal behaviour?

I have set up a Samba PDC migrating from NT4. I can logon computers and users that came from the old NT4 domain. I began setting up a SambaBDC following the directions in Section 5.5 of Samba3 by Example. Using samba3.0.20b on RHEL4 whenever try # net rpc join -U root%secret or # net rpc join -S SAMBAPDC -U root%secret I get the following error

Using "ldap password sync=yes" I can modify user password as admin through "net rpc user password" but if I try to modify it from the user (net rpc password myuser mypw -U myuser) or from windows (ctrl+alt+del). I get a timout error: [2006/03/16 21:52:40, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790) rpc_api_pipe: Remote machine alphacserver pipe \samr fnum 0x70e9returned

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, all. Last night, access to our samba server was interrupted, and the only thing I can find is these repeated over and over again in the messages file: Jul 8 07:44:15 knorr winbindd[24628]: cli_pipe: return critical error. Error was NT_STATUS_PIPE_DISCONNECTED Jul 8 07:44:15 knorr winbindd[24628]: [2005/07/08 07:44:15, 0]

This is with 3.0.11 and the idealx smbldap-tools 0.8.7 ----------8<------------------------------------------- # /opt/IDEALX/sbin/smbldap-groupshow 'Domain Admins' dn: cn=Domain Admins,ou=Groups,dc=wetron,dc=es objectClass: posixGroup,sambaGroupMapping gidNumber: 512 cn: Domain Admins memberUid: Administrator,luca description: Netbios Domain Administrators sambaSID:

Dear Samba users. I have tried to add my Samba server to a Win2k AD mixed mode domain for several days. I have searched the Internet for information, but couldn't find a solution. So I will try to describe my problems here. I first tried to use "security = ADS" and add the Samba server as a native member. I have changed the settings in my krb5.conf and tested this with kinit: --