similar to: Weird problem in NMBD

I have recently upgraded my Redhat 7.3 server to Fedora FC1 with all related updates. I also upgraded my samba version from 3.0.0 to 3.0.2a. It now seems that my nmbd daemon will not start & subsequently I cannot log in from any Windows client as the netbios server name PDC is not found I think. Before this problem started, I noticed that in order for my DNS ping requests from Windows clients

hi, samba will work normally if i issue the command '/etc/init.d/samba start', but as for starting up properly at boot time, it will go down when booted as the end of log.nmbd shows. as far as i'm able to read the logs, there is nothing suspicious happening. why is this occurring and how do i fix it. i'm running samba version 3.0.14a-3sarge2. i've included my smb.conf

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]

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()

Hello, I am using samba 2.0.4b on Linux 2.0.36. Since I changed some of the parameters in my smb.conf I have a very strange Problem. Everytime my Samba-Box wins the browselist election process two nmbds are started and my WinXX-Clients do not get access to samba (I could see the server but not access the shares nor login to the domain). smbclient -L server from server works fine. From another

I'm stumped on getting Samba to work again on our small network. I've got one Windows 95 machine that started to refuse to talk to Samba last week. I *was* running one of the 1.9.18 releases, but when it stopped working, I figured I would delete the old release and do a clean install of 2.0.3. I've done that, and used SWAT to configure the smb.conf file (which can be seen below).

Hi All; I'm currently trying to expand my Samba env by including my IBM z/800 mainframe running 64 bit RHEL v3.0, CUPS printing environment into Samba. When I start Samba, the nmbd dies almost immediately. Any insight would be greatly appreciated. [root@stlpr003 root]# rpm -qa | egrep "kern|samba" kernel-2.4.21-9.0.1.EL ... samba-common-3.0.2-6.3E samba-3.0.2-6.3E

I have a Solaris box and Windows 2K box connecte through a hub, along with a DSL modem. I cannot get the two boxes to work via Samba, here is the relevant details. The status report from SWAT # Samba config file created using SWAT # from localhost (127.0.0.1) # Date: 2001/03/02 12:54:01 # Global parameters [global] netbios name = MARISOL server string =

Hi, I have had samba 3.0 running on my FreeBSD 5.2 sparc64 system for a few weeks without any issues. Recently I had to reboot, and now nmbd won't run. I have NOT changed my config one bit. I have verified nothing is bound to port 137 via netstat -an . The error is as follows: [2004/03/19 05:20:10, 0] lib/util_sock.c:open_socket_in(646) bind failed on port 137 socket_addr =

I manage a Samba server that has been working nicely for a couple of months (after it replace the old Samba server which worked happily for years). We use LDAP for accounts, but don't use domain logons or anything fancy. All users have their home dir on Samba mapped to drive 'M:'. In their home, there are symbolic links to various directories they're entitled to access. Links

Freebsd 12.0-RELEASE-p10 samba 4.8.12 Recently, my machine has started going into an endless loop with the following message rolling off the screen continuously: nmbd_subnetdb:make_subnet() Failed to open nmb bcast socket on interface 0.255.255.255 for port 137. Error was Can't assign requested address

Hello I'm a biginner on samba and mailinglists. But I desperate need same help. After updating my samba 2.2.1a to 2.2.2 I can't logon to the domain again. The log.nmdb gives out this information: [2001/11/02 01:22:28, 0] nmbd/asyncdns.c:start_async_dns(150) started asyncdns process 184 [2001/11/02 01:22:28, 0] lib/util_sock.c:open_socket_in(820) bind failed on port 137

Am Do 01.02.2018 um 12:04 schrieb Martin Schwenke: > Hi Nicolas, > > On Thu, 1 Feb 2018 10:57:59 +0100, Nicolas Zuber via samba > <samba at lists.samba.org> wrote: > >> I try to update two clustered samba file servers. Right now samba 4.7.0 >> with ctdb is running on both of them. To update samba I stopped ctdb on >> one of the servers, and compiled and

I've been having problems installing Samba on AIX 4.32. I have spent well over two weeks on the issue and have not had any major success. I can get samba 1.9 series of source code and binaries to work fine but the new Samba 2.0 series code is causing me problems. I have the following system and problem. I have a H50 with 2 NICs; one is ether and the other is token. I can't seem to browse

-----Original Message----- From: Mike [mailto:vje@adelphia.net] Sent: Monday, November 03, 2003 1:23 AM To: rruegner Subject: RE: [Samba] XP joining domain - problem Hi, Thanks for the quick reply. Here are the smbd and nmbd logs. I'm not sure if you need the nmbd, but I wanted to include it just in case. Sorry I did not include them in the initial email. Sincerely, Mike ====START OF

Following a working fine samba install, I just did a new installation of samba 2.2.8 on FreeBSD 4.8(s) and while I can explore the network and I can copy files to unix, I cannot print to unix. Then log.nmbd file says; [2003/03/17 16:58:10, 0] nmbd/nmbd.c:main(795) Netbios nameserver version 2.2.8 started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/03/17 16:58:10, 1]

hi, i've been trying for like two weeks to figure out why samba doesn't run properly. from the logs it looks like smbd will start followed by nmbd. then nmbd will exit for no apparent reason. i'm able to start samba manually with the command '/etc/init.d/samba start'. right now i'm assuming nmbd is the reason why samba doesn't load. i'm running samba version

On Fri, 16 Dec 2016 13:46:24 +0100 Artur Moor via samba <samba at lists.samba.org> wrote: > If I remove 'nmbd bind explicit broadcast = no' in 'smb4.conf', then > nmbd wan't start and I get following in the log: > > [2016/12/16 12:37:35.075428, 0] > ../source3/lib/util_sock.c:396(open_socket_in) > bind failed on port 137 socket_addr = 10.0.140.255.

Hi. I got this email-address from BUGS.txt file of the samba distribution. I read it carefully. I got configured and working samba, I work with samba above one year. I still have a problem, and, according to the samba log output, I think it's probably a bug. When I try to use the shares with audit support, I have my Far disconnected and telling me that something is wrong. I have that

Hi All, I am using samba Version 3.5.4 on AIX 6.1. The installation is through pware binary ( pware53.samba.rte 3.5.4.0). There seems to be a strange issue with NetBios where it terminates with the following error logged just after starting. The diagnosis fails in step 4 of Samba Diagnosis test ("nmblookup -B BIGSERVER __SAMBA_") because no netbios (nmbd) is running. snippet from