similar to: Problems with Samba 2.0.7, Solaris 8, and Windows 2K

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

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

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

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

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

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.

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]

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 =

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

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

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

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

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

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:

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

I am having a lot of problems with nmbd. Basically it refuses to open its socket to listen on. I have checked, and the reason cannot be that the port is in use, as I can set any port with the -p switch, and I get the same error. The relevant part of the nmb log is: Netbios name list:- my_netbios_names[0]="DIRAC" lp_file_list_changed() file /usr/local/samba/lib/smb.conf ->

Hello, I'm having problems using Samba as an primary domain controller. I am using debian woody as our platform. The version of samba is "2.2.3a-12.3 for Debian" and i followed the instructions which can be found on the following url: http://www-106.ibm.com/developerworks/eserver/tutorials/samba/. In short this covers: - creating the config file - creating the users /