similar to: Improved diagnostics patch

on systems that has separate IPv4/v6 socket layer (i.e. IPv4 packet does not get routed to AF_INET6 socket) rsync --daemon would accept IPv6 sessions only. open_socket_in() tries to deal with the situation, but it was not enough. here's the patch. (it is required on all *BSDs to accept both IPv4 and IPv6 connections with --daemon mode) itojun --- ? configure.lineno ? lib/dummy

Hello I need to check that the NHS numbers in my database are valid. I''m storing them as ten-digit strings: the first nine are the identifier and the tenth is a check digit. There are four steps to calculating the check digit (from http://www.connectingforhealth.nhs.uk/systemsandservices/nsts/docs/tech_nn_check_digit.pdf): 1. multiply each of the first nine digits by a weighting factor

Hi folks, I've discovered a local stack overflow bug in rsync 2.5.7. Problem is in open_socket_out function (socket.c). ... char portbuf[10]; char *h; int proxied = 0; char buffer[1024]; char *cp; ... h = getenv("RSYNC_PROXY"); proxied = (h != NULL) && (*h != '\0'); ... if (proxied) {

We have a windows 2003 dc here at the university and I have successfully setup samba-3.0.2-6.3E on a RHEL WS3 machine. The problem is that after several hours, or several days winbind stops running and connections fail. I have seen instances of this on other sites, but no firm answers. I can provide files and logs if helpful

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)

Hi, I have a problem with getting winbind to work on my domain. I have installed ver 2.2.5 with winbind as a depot file, and that went ok. I have set up samba, and testparm finds no errors. I have joined the domain, again, no problem ! Now here's the thing: I cant use wbinfo: # ./wbinfo -u Error looking up domain users # ./wbinfo -t Could not check secret # ./wbinfo -g Error

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)

Hi, I installed Samba on Solaris to enable me print from the solaris workstation to a windows print server. When I start smbd and nmbd , smbd does not run but nmbd runs

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: > >

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.

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

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:

My production DC machine owns the mail filesystems and is running DC V1.0.15 and mbox folder format. I am looking to test V1.1.3 on another machine, which NFS mounts the mail filesystems, but has its own local index FS. I have made this test environment my default connection in TBird, and it seems to work just fine. Also, I have made sure that my TBird client isn't connecting to the

Hi. Today I upgraded samba from 3.0.34 to 3.4.4 without changing anything in smb.conf but with changing local and domain sid: old samba 1) net getdomainsid and getlocalsid new samba 2) net setdomainsid and setlocalsid to ones (both the same) from 1) after restarting samba I can't log into domain: XP says : domain controller unavailable ... I tried to rejoin domain - and I can ;) however

Adds reclocking for NVA0, and a whole lot of work for other cards. Had these patches collecting dust for a little, but tested them with both my NVA0, and Martin's a while back. Success not guaranteed, but should be quite a leap forward. Happy reviewing and testing. Cheers, Roy

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)