similar to: nmbd won't bind on FreeBSD 5.2-RELEASE sparc64

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 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, I've a got kind of weird problem using nmbd. At least, I think is is weird because this problem isn't dealt with in any documentation. I got my nmbd up and running, when I issue the command 'nmblookup -U 10.0.0.1 __SAMBA__' (my IP is 10.0.0.1/255.0.0.0) I get a correct response: 'querying __SAMBA__ on 10.0.0.1 10.0.0.1 __SAMBA__<00>' But when I use a

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

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

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

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

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

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.

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

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

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. Error = Can't assign requested address [2016/12/16 12:37:35.075626, 0] ../source3/nmbd/nmbd_subnetdb.c:127(make_subnet)

Hi there. This is with regards to samba-3.0.23c, on FreeBSD 6.0-RELEASE-p12 Previously I had Samba up and running without any problems. Then I decided to do a tiny upgrade by simply switching to a new motherboard, while keeping all other hardware and software aspects the same. However, after the upgrade, netbios name resolution seems to have stopped working somehow. \\servername lookups no

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

Bonjour, I have some problem to configure a printing server with samba. I have a private network with a linux box as a gateway to the internet and several machine on this network some under windows, others under linux. One of the linux machine (which is not the gateway) has a printer which I want to be shared by the windows machines. The gateway has 192.168.0.1 as private IP number and the linux