similar to: Do I need nmbd with AD samba?

I have samba+ads working fine *HOWEVER* when I run net ads keytab create it fails. Using -d 10 the debug output says it cannot write to the file. This is truly bizarre as I am running this as root! e.g. # /usr/local/opt/samba/samba-3.0.24/bin/net ads keytab create ; echo $? 183 And /usr/local/opt/samba/samba-3.0.24/bin/net -d 10 ads keytab create ; echo $? Gives [..snip..] ads_get_kvno:

We're trying to dual home samba onto 2 windows domains. We're created 2 separate smb.conf files each having it's own domain specific info. The only differences between them are - different workgroups - different interfaces to bind too - different socket addressees (matches the interface) - and different WINS server IPs. We are using the security = domain model. We've

ctdb 2.5.3 dual node file server with 4.1.9 serving AD domain Hi We have enabled the script at: /etc/cdb/events.d/50.samba but when we are the enabled node, it starts not only smbd but also nmbd. This doesn't make sense in an AD domain. I've tried disabling nmbd starting under openSUSE's systemd but ctdb overrides that, I've had a look at the script but can't decipher the bit

I get the following log when trying to run nmbd -D Netbios nameserver version 2.2.3a started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/05/20 15:02:44, 0] lib/util_sock.c:open_socket_in(789) bind failed on port 137 socket_addr = 10.10.50.4. Error = Cannot assign requested address [2003/05/20 15:02:44, 0] nmbd/nmbd_subnetdb.c:make_subnet(140) nmbd_subnetdb:make_subnet()

Hi I?ve been seeing this issue since we updated from Samba 2.X to 3.Y, and I wanted to know if anyone has seen this: I have a samba PDC mantaining a domain composed of WinXP, Win200 and win98 machines with shared folders and user authentication (smbpasswd). It works fine for hours but then everybody stops being able to logon. When anyone tries to login in a WinXP machine, it only replies

Hi, I've set up a samba server as a primary domain member with AD auth. Everything works pretty smoothly except that when you reboot the server samba will not work. AFTER REBOOT: kfrank at tldapprovider003:~$ smbclient \\\\tldapprovider003\\base Enter kfrank's password: session setup failed: NT_STATUS_MORE_PROCESSING_REQUIRED did you forget to run kinit? I don't have kerberos

Hi folks, We're seeing an odd thing happening on about 8 out of 100 UNIX machines running Samba 1.9.18p7. Mostly on HU-UX 10.20 systems, but at least once on an IRIX 6.4 system. The scenario: - SAMBA up and running in this environment for about 2 years sharing UNIX home directories with NT boxes. - SAMBA set up to start via inetd. - Had a plant shutdown over a weekend a month ago, all

I'm trying to do something fairly simple: login to a Linux box using a Windows AD-based account. I've followed the various recipes available online for configuring Linux (winbind, PAM, etc.) to this send, and I've got it working ... almost. I'm able to authenticate an AD-based user immediately after bringing up the Linux box, but a short time later (roughly 5 minutes, but it

Hi, (3.0.21b, OpenBSD -current) I'm trying to get the smbd and nmbd processes to run under daemontools and to log to multilog. Using the -F -S switches should work, and is widely cited in google searches, but logging to multilog stops shortly after the daemons start. The last message that goes to multilog is standard input is not a socket, assuming -D and from then on logging goes to the

Hello, I have a Debian machine with samba 3.0.2a-1 (which should bei identical to samba-latests, AFAIK). For a reason not yet known nmbd processes keep hanging around forever, eating up memory slowly, but steadily. Logfiles do not show anything suspicious (to me, at least, I don't want to put a days level 10 log in here), except from things like | Mar 8 10:06:22 bertha kernel: Out of

Hi, we had upgraded our SAMBA PDC from 3.0.14 to 3.0.22 on a Gentoo system. Now we have problems with peculiar spwaning of too many "nmbd" processes. In smb.conf WINS support is activated, so I would expect two nmb processes. But as you can see in the process list, during SAMBA is running after some minutes another nmbd child is spawned. I tracked down the problem to one example: We

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sometime after I installed samba and got everything working, one of my colleagues changed the IP address on the box I did the install on. So after I got passed all the other issues that plaqued me after moving over to fedora 11, I discovered that I could not added Win clients to the domain. I dug into the log files: Jul 8 15:24:03 ldap2

Hi, I'm running Samba 3.0 on a Solaris 9 server. If you look at the output of top you'll see that that nmbd process is killing this machine: I've restarted Samba numerous times, and each time the load goes down immediately and when I restart it the load goes up and nmbd starts to take up all the processor time. load averages: 21.18, 19.61, 24.65 11:04:20 210 processes: 187

Every day, I get this error message. It's always around 4:02AM. Jul 6 04:02:10 print-server nmbd[3069]: [2006/07/06 04:02:10, 0] nmbd/nmbd.c:process(596) Jul 6 04:02:10 print-server nmbd[3069]: Got SIGHUP dumping debug info. Jul 6 04:02:10 print-server nmbd[3069]: [2006/07/06 04:02:10, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(284) Jul 6 04:02:10 print-server nmbd[3069]:

Hi, I've installed a samba 3.0.10 (configured with --enable-cups, --withsmbmount, --with-acl-support) on a standard SUSE Linux 9.2-Distribution with Kernel 2.6.8-24.10-smp. The Samba-Server works as PDC since a month now and does it fine. But one big problem still exists: After about 10-20 hours after the start of smb+nmb the nmbd stops working. The symtoms are: No new users can login into

Hello all, I'm in the process of moving over my Samba server (using LDAP). I believe everything is functioning correctly, except for this error I get when nmbd starts. Looking back at my old server, it was apparently doing this as well... so it may not even affect needed functionality. Still, I'd like to figure out why it's happening! If anyone has an idea, please let me

Hello, I'd be grateful for any hints or insight into the following messages which are being written to the log.nmbd file on my samba server "samba2000". samba2000 is running Samba version 2.2.8a. Sincerely, Derek Moran [2003/06/10 15:40:17, 0] nmbd/nmbd.c:main(795) Netbios nameserver version 2.2.8a started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/06/10

After running several days in the same configuration, my 3.0.6 nmbd crashed with the above error (see log below). Maybe there is a connection to this message some seconds before: register_name_response: server at IP 192.168.0.4 rejected our name registration of AK<1d> IP 192.168.0.12 with error code 6. The ip .4 machine is a win2k server, which works (or should work) as an ordinary

The only thing related to 'addresses' in my /etc/samba/smb.conf file is a "hosts allow": hosts allow = 192.168.3.0/24 127.1 I'm going to ignore the 'local hosts case, as if I solve the other, the localhost case may get solved by inference. I thought the 'hosts allow' would allow any host on the local 192.168.3.0/24 subnet. The hosts have no problems

Anyone seen anything like this before? I start samba and both nmbd and smbd crash imediatly. Winbind stays running but the other 2 crash, Below is my log files. Anyone have any idea why this is happening? Is my Lib.c fubar or somethin screwy or do I have some setting wrong? Chris -------log.smbd------------------------------------------------- [2003/10/22 15:54:41, 0] smbd/server.c:main(747)