similar to: printing server

I have just posted this message, forgetting to add the subject....: Bonjour, I have recently somme difficulties to use samba -M, the answer is: Cannot resolve name <name>#0x3. Here is an exemple: $ smbclient -M falstaff added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0 Cannot resolve name falstaff#0x3 But if I use -L, the name is resolved: $ smbclient -L falstaff

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

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

Hi everyone , i'm not very well in english language but please just try to understand . When i tried to launch ragnarok on wine , i received this error : Exception EAccessViolation dans le module Oxygene.exe ? 008F2BE8. Violation d'acc?s ? l'adresse 008F3BE8.Lecture de l'adresse 0000FFF8 and sometime wine doesn't send this message; it just doesn't do anything. Good bye

Greetings! I'm experiencing these problems as described in this mail: ------- From: Thomas Quinot (thomas@melusine.cuivre.fr.eu.org) Subject: Rsync 2.5.5: FreeBSD mknod can't create FIFO's This is the only article in this thread View: Original Format Newsgroups: mailing.unix.rsync Date: 2002-06-24 06:05:25 PST The following patch

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 =

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

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

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

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

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]

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

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