similar to: nmbd dies as soon as it's started

Displaying 20 results from an estimated 2000 matches similar to: "nmbd dies as soon as it's started"

2003 May 20
2
Need help troubleshooting nmbd -D
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()
2001 Nov 01
2
Stupid beginner
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
2019 Oct 21
1
ERROR: Failed to open nmb broadcast 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
2004 May 06
1
nmbd doesn't start: Address already in use
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
2016 Dec 16
1
Fwd: net ads join -> "The connection was refused"
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.
2016 Dec 16
2
Fwd: net ads join -> "The connection was refused"
On Fri, 16 Dec 2016 12:36:33 +0100 Artur Moor via samba <samba at lists.samba.org> wrote: > If I remove 'nmbd bind explicit broadcast = no' then 'smbd' can't > start because samba is running i jailed einvironment. You should still be able to start 'smbd', are any Samba deamons running when you try the join? Which Samba daemons are you starting ? >
2012 Oct 14
5
wins: no nmblookup on 192.168.1.255 but 192.168.1.2
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:
2004 May 18
3
nmbd crash on z/800 64 bit RHEL v 3.0
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
2004 Dec 08
1
printing server
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
2013 Jul 31
2
nmbd is not running
Hi I have samba domain controller in my network. and recently I have changed the netmask of the network. Then nmbd is not working could you please help me to solve this issue ---------------------------------------------------------------- nmbd -i nmbd version 3.5.6 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 Unknown parameter encountered: "wide symlinks"
1999 Sep 29
3
AIX 4.32 install (PLEASE HELP)
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
1998 Jan 26
6
nmbd
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 ->
2004 Mar 19
0
nmbd won't bind on FreeBSD 5.2-RELEASE sparc64
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 =
2001 Mar 02
0
Problems with Samba 2.0.7, Solaris 8, and Windows 2K
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 =
2003 Nov 03
1
FW: XP joining domain - problem
-----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
2016 Dec 16
0
Fwd: net ads join -> "The connection was refused"
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)
2010 Aug 18
1
netbios uses incorrect broadcast value and termintaes
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
2004 Feb 15
0
Nmbd errors & not starting since upgrade to 3.0.2a?
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
2002 Jun 05
0
Weird problem in NMBD
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
2003 Dec 16
5
A domain controller for the domain could not by contacted (2.2.3a-12.3 for Debian)
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 /