similar to: Samba/Winbind

Hi, I have set up the samba/winbind (2.2.5) on my HPUX 11i, and have joined the domain with no problem. If i'm right, I should then be able to connect to the samba share as if i was an ordinary domain user or what ?? But I can't. The debug on winbind says: Added domain BRAPT98 (S-1-5-21-654460698-771908679-1844936127) [2002/08/19 10:30:33, 2] libsmb/namequery.c:(421) Got a positive

I am install Samba on a New RS/6000 M 80. I am installing Samba 2.0.7. I have the services and inedt.conf files with the needed entries and have add a program check my entry. I get the following error in the log file and can not figure out what is wrong. [2001/01/17 12:31:59, 0] lib/util_sock.c:open_socket_in(863) bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)

Is anyone familiar with using a samba server in Android Termux? It works OK for an smbmount in a Linux qemu VM, in the instance started by the -nic smb=$PATH option of qemu (both qemu-system-x86_64 and samba installed to Termux) but smbd -D fails with this log: [2024/01/06 11:46:54.038658, 0] ../../source3/smbd/server.c:1741(main) smbd version 4.16.11 started. Copyright Andrew Tridgell and the

On Wed, 10 Jan 2024 16:25:57 +0000 Mike Yates via samba <samba at lists.samba.org> wrote: > Is anyone familiar with using a samba server in Android Termux? > It works OK for an smbmount in a Linux qemu VM, in the instance > started by the > -nic smb=$PATH option of qemu (both qemu-system-x86_64 and samba > installed to Termux) but smbd -D fails with this log: > >

I have upgraded samba to 2.2.7a and cannot print to my printer attached to my BSD machine. I can use the share dirs, etc, but cannot print. My log file contains: [2003/03/17 16:17:19, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use [2003/03/17 16:18:02, 0] smbd/service.c:make_connection(252) 50163099sp (204.250.145.147)

No, I don't have root in my Android. I understand that prevents access to ports below 1024 but I find that Linux clients can mount Termux qemu-started Samba shares nevertheless. I need to prevent smbd crashing for want of low sockets and wonder if win9x can mount without them. On Wed, 10 Jan 2024, 17:07 Rowland Penny via samba, <samba at lists.samba.org> wrote: > On Wed, 10 Jan 2024

In samba 4 log I get the following message: [2013/04/29 00:44:30,? 0] ../source4/smbd/server.c:369(binary_smbd_main) ? samba version 4.1.0pre1-GIT-5727bfa started. ? Copyright Andrew Tridgell and the Samba Team 1992-2013 [2013/04/29 00:44:31,? 0] ../source4/smbd/server.c:475(binary_smbd_main) ? samba: using 'standard' process model [2013/04/29 00:44:32,? 1]

I've compile a Samba 4.0.9 for x86_64 with the following options: CPPFLAGS="-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -march=atom -O2 -pipe -fomit-frame-pointer" \ samba_cv_HAVE_GETTIMEOFDAY_TZ=yes \ samba_cv_HAVE_IFACE_IFCONF=yes \ samba_cv_HAVE_IFACE_IFREQ=yes \ ac_cv_have_setresuid=yes \ ac_cv_have_setresgid=yes \ ac_cv_file__proc_sys_kernel_core_pattern=yes \

Hi, I've just upgraded an old samba 3.0.23 on an old Fedora Core 5 to samba 3.5.4 using an rpm built from the source. Everything works fine, but when i start the server i get some error messages(see below). Before i start the server there is no connection (tested with lsof and fuser) on the 139 and 445 ports, smbd or nmbd aren't running. With the old version i never had this

My wife and I each have our own workstation dual-booting WinXP and Gentoo Linux. We also have a third which runs Gentoo all the time. I wanted to set up samba on the third box and provide some extra storage space for both our Windows installs. It worked for a few days, then all of a sudden it stopped letting my account (michael) in while still letting my wife's account (amy) use the share.

Hi, here is a client computer and a server computer (Debian Wheezy, armel, samba Version 3.6.6, IP address: 192.168.1.2, Name: xyz). Problem: wins doesn't answer nmblookups by the client on the broadcast address: client$ nmblookup -S xyz querying xyz on 192.168.1.255 name_query failed to find name xyz Why is that so? How to fix this? When I specify the the server IP I do get an answer:

Hallo, I've just updated my slackware samba packet from 3.6.17 to 4.1.6. My start script is not changed, it still calls "nmbd -D" and "smbd -D". Seems to run as expected. But now I get strange messages like [2014/04/15 10:36:05.535423, 0] ../source3/lib/ util_sock.c:423(open_socket_in) open_socket_in(): socket() call failed: Die Adressfamilie wird von der

Hi, I just installed a new Centos 6.1 machine with Samba 3.5.6-86.el6_1.4 . I use Webmin to administer the server and configuring Samba (SWAT is also available in Webmin). I have chosen the option to convert the Linux users to Samba users and the command completes and says the users have been converted. However, when I then look at the Samba users the list is empty. Restarted the Samba

Hi Everyone, my first foray into Samba and AD both. Not sure if this is an OS or configuration problem. I've found similar issues, but nothing either recent enough (is related to samba 3) or close enough. FreeBSD-10.1-RELENG, Samba 4.2.2. I have the domain provisioned as rfc2307 I have joined a Win7-virtual machine to the domain I have created a new user with ADUC I have assigned 10000 to

Hello! I have cross-compiled Samba 2.2.3a for my Dreambox(PPC DVB receiver with Linux). smbd runs without any problems but when I start nmbd I get the following error message: -------------------------------------------- standard input is not a socket, assuming -D option open_socket_in(): setsockopt: SO_REUSEADDR = True on port 137 failed with error = Protocol not available Failed to set socket

I've built samba for an embedded mips platform. Since this is an embedded platform, it's possible that some critical file that samba needs is missing but stracing the daemons doesn't reveal anything strange. It's running 2.4.34 kernel. Samba is failing to find any interfaces. [2000/01/02 10:55:01, 3] nmbd/nmbd.c:main(759) Opening sockets 137 [2000/01/02 10:55:01, 10]

I get the following errors in the smb.log file. If anyone has any ideas about this please let me know. [2001/05/01 09:51:46, 0] lib/util_sock.c:set_socket_options(154) Failed to set socket option TCP_NODELAY (Error Connection reset by peer) [2001/05/01 09:51:46, 0] lib/util_sock.c:open_socket_in(827) Get_Hostbyname: Unknown host [2001/05/01 09:51:46, 0] smbd/oplock.c:open_oplock_ipc(93)

No-one has had this problem before? ----- Forwarded by Raymond Hoogerdijk/home on 20-12-2011 20:36 ----- From: Samba <samba at hoogerdijk.org> To: Samba Maillist <samba at lists.samba.org> Date: 14-12-2011 21:37 Subject: [Samba] Convert Unix users to Samba users Sent by: samba-bounces at lists.samba.org Hi, I just installed a new Centos 6.1 machine with

On 11/07/15 10:16, Rowland Penny wrote: > On 11/07/15 04:06, Lee Brown wrote: >> Hi Everyone, my first foray into Samba and AD both. >> >> Not sure if this is an OS or configuration problem. I've found similar >> issues, but nothing either recent enough (is related to samba 3) or >> close >> enough. >> >> FreeBSD-10.1-RELENG, Samba 4.2.2.

As soon as I start up the daemons using the following commands, nmbd dies. /usr/local/samba/bin/smbd -D /usr/local/samba/bin/nmbd -D When I view the nmbd.log it gives the following. We're trying to set up Samba to work over 2 subnets. Smbd is ok and we can still mount our shares. Does anyone have any suggestions? Thanks for any help. [2002/10/22 10:37:55, 0]