similar to: recurring samba error

Our log.nmb file fills up very quickly with the following pattern of messages: [2000/06/19 05:10:59, 0] nmbd/nmbd_namequery.c:query_name_response(93) query_name_response: Multiple (2) responses received for a query on subnet 129.130.10.136 for name NT.CIS.KSU.EDU<1d>. This response was from IP 129.130.10.24 [2000/06/19 05:10:59, 0] nmbd/nmbd_namequery.c:query_name_response(93)

This is a repost with some new information: Our log.nmb file fills up very quickly with the following pattern of messages: [2000/06/22 11:58:25, 0] nmbd/nmbd_namequery.c:query_name_response(93) query_name_response: Multiple (2) responses received for a query on subnet 129.130.10.136 for name NT.CIS.KSU.EDU<1d>. This response was from IP 129.130.10.24 [2000/06/22 11:58:25, 0]

Thanks for the replys... Just a basic samba server...being accessed by windows 7 to the gc and tmr shares with \\10.10.171.9\gc and \\10.10.171.9\tmr This has been running for a year without any issues...till the update yesterday afternoon :-( The file server is Ubuntu 18.04 and there was an update to Ubuntu 18.04.1, which I thought would be a mild step. The current version of samba is...

Hello, Don't know what happened, but Samba stopped serving up shares. Top shows 'smbd' using 66% of the cpu and 'rpc.mountd' using 33%. The samba log on shows; [2006/01/19 16:34:54, 0] nmbd/nmbd.c:main(668) Netbios nameserver version 3.0.13-1.1-SUSE started. Copyright Andrew Tridgell and the Samba Team 1994-2004 [2006/01/19 16:40:03, 0]

Hi, I have joined a RedHat-7.1 box with Samba 2.2.2 to a NT Domain, and everything works perfect. Except when I look in de log file I see a name query error every 5 minutes , and I don't know how to solve this problem. The PDC-A is de primary domain controller and tux is the linux box with samba. I made u tcpdump on the same moment when I receive the error and it seems that the NT box sends

SMBv1 (the anonymous thing behind network neighborhood) because of the massive security problems it caused was decprecated. Microsoft came up with network neighborhood and they've shut it down due to their bad implementation. Samba, likewise, doesn't support SMBv1 by default. On 7/12/20 10:29 PM, Michael Jones via samba wrote: > I'm trying to diagnose why my windows 10 clients

If you have 1 member server, you could enabe nmbd in that server. Or install : llmnrd on linux and/or avahi-deamon if you dont have a member. And make sure you can use "proxy dns" as in, The primary DNS domain on linux should match (see in windows) CMD: ipconfig /all The : - primay dns suffix - DNS Suffix search order Then you are able to use \\hostname or \\hostname.FQ.DN.TLD

A reasonable alternative is to run Christgau's excellent Web Service Discovery host daemon (wsdd) on the samba server and make sure the Function Discovery Provider Host and Function Discovery Resource Publication services are running on the Windows 10 machines. Get wsdd from here: https://github.com/christgau/wsdd.git You can then stop and disable the nmbd on the samba machines as it's

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

Hi, I am using Winbind & NSS/PAM on Debian Linux, joined to a Windows 2000 AD Domain, to provide email (SMTP/POP3) based on Windows username and password. I have two Windows 2000 Servers for domain controllers, DC1 and DC2. Over the weekend DC2 had a CPU fan fail and it overheated and crashed. Once DC2 failed, PAM Winbind stopped working and my users could no longer log into their

Samba 4.8.9 FreeBSD 12.0-RELEASE-p3 / amd64 Since updating both FreeBSD and Samba, I have been getting the following screen pop-ups incessantly. They are always the same except for the time. IP 102.168.0.102 is a Win10 PRO / amd64 machine. I never received any warnings before updating. <quot> Mar 19 08:23:58 scorpio nmbd[11202]: [2019/03/19 08:23:58.049153, 0]

Hello all, I'm running samba 2.2.4 on Sun Solaris version Sunos 5.8 generic_108528-17, Samba version 2.2.4 I'm getting this error in my /var/adm/messages and don't know what it means, I suspect it is also responsible for causing the delays in the application running from the shares. Jun 8 14:53:53 krypton nmbd[3096]: [ID 702911 daemon.error] query_name_response: Multiple (2)

On Tue, 19 Mar 2019 13:02:40 +0000, Rowland Penny via samba stated: >On Tue, 19 Mar 2019 12:37:08 +0000 >Gerard Seibert via samba <samba at lists.samba.org> wrote: > >> Samba 4.8.9 >> FreeBSD 12.0-RELEASE-p3 / amd64 >> >> Since updating both FreeBSD and Samba, I have been getting the >> following screen pop-ups incessantly. They are always the same

Current Version: samba 4.18.1 All, I have several **standalone** servers on a subnet, and for quite some time, I have received log messages in other standalone machines about multiple responses from the WINS server. There is only a single WINS server on the network (as it has been since samba 2.02 or earlier). The WINS server is 192.168.6.14. The log message that is received for example

Hello, I search help for samba. In console of my server, a message appears all 5 minutes. "[] nmbd/nmbd_namequery.c: query_name_response(95) query_name_response: Multiple (2) responses received for a query on subnet (IP address of my server) for name (Domain name samba) This response was from IP (IP address of another server)" Why to correct this problem, if it's a problem ? thank

Hi, I'm running Samba 2.0.4b on a Debian Linux (v2.2) PC. If I look at the "log.nmb" file there are many messages: [1999/10/25 08:39:19, 0] nmbd/nmbd_namequery.c:query_name_response(95) query_name_response: Multiple (2) responses received for a query on subnet 130.199.xxx.yyy for name WORK<1d>. This response was from IP 130.199.xxx.zzz The frequency is every 5 minutes.

hi, when i do nevanfs01:/ # nmblookup NEVAN#1B i get querying NEVAN on 192.168.255.255 192.168.41.3 NEVAN<1b> 192.168.41.3 NEVAN<1b> i just wonder, why there's two times the same entry? i also get error messages from nmbd like these, which i think are related to the problem i mentioned at first: 2004-07-21 13:34:21 nmbd[3150]: [2004/07/21 13:34:09, 0]

Hello. Time after time users can not log in in domain and im see this in logs(time stamps deleted): nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup HQ on subnet 172.16.1.3 ...skipping... nmbd/nmbd_incomingrequests.c:process_name_release_request(80) process_name_release_request: unicast name release request

Here is my situation: I have an AIX 4.3.3 machine, that I have compiled open-ldap, kerberos5 (1.3..6), and Samba 3.0.20. Here is my smb.conf file: [global] realm = REGION.DOMAIN.COM security = ADS password server = randomdc.region.domain.com workgroup = REGION client use spnego = yes ;winbind separator = \ [homes] comment = Home Directories read only = no create mode = 0750

I'm trying to diagnose why my windows 10 clients can't do network browsing. The network neighborhood doesn't show any of my machines running samba. I've verified that all of my samba hosts are running nmbd! I've reached the end of my ability to debug this, so I could really use some help from the list to figure out why this isn't working. I've isolated the situation