similar to: query_name_response: Multiple (2)

Displaying 20 results from an estimated 300 matches similar to: "query_name_response: Multiple (2)"

2016 Mar 03
2
query_name_response: Multiple (2)
Hello, does someone could explain me what means this message : query_name_response: Multiple (2).... example : samba4 nmbd[88458]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.151.237 for name SAMBA_DOMAIN<1d>. samba4 nmbd[88458]: This response was from IP 192.168.152.237, reporting an IP address of 192.168.152.237. The server has 3 nic (vlans)
2016 Mar 03
1
query_name_response: Multiple (2)
> On 03/03/16 08:23, Pascal Legrand wrote: >> Hello, >> >> does someone could explain me what means this message : >> query_name_response: Multiple (2).... >> >> >> example : >> >> samba4 nmbd[88458]: query_name_response: Multiple (2) responses >> received for a query on subnet 192.168.151.237 for name SAMBA_DOMAIN<1d>. >>
2016 Feb 05
1
query_name_response: Multiple (2)
> Can you post the smb.conf from '192.168.152.237' as i said before there is only one samba server with 3 network interface The smb.conf # IDENTIFICATION netbios name = Samba workgroup = Samba_Domain server string = %h #Informations annuaire LDAP passdb backend = ldapsam:"ldap://192.168.151.247" ldap suffix = ou=Samba,dc=annuaire,dc=fr ldap admin dn =
2016 Feb 05
0
query_name_response: Multiple (2)
On 05/02/16 14:36, Pascal Legrand wrote: > Hello, > > does someone could explain me what means this message : > query_name_response: Multiple (2).... > > > example : > > samba4 nmbd[88458]: query_name_response: Multiple (2) responses > received for a query on subnet 192.168.151.237 for name SAMBA_DOMAIN<1d>. > > samba4 nmbd[88458]: This response was from
2000 Aug 14
1
query_name_response: Multiple responses received
Hi all, I've just noticed I'm getting a load of these query_name_response: Multiple (2) responses received for a query on subnet 193.62.43.24 for name INFORMATICS<1d>. This response was from IP 193.62.43.39 In the log.nmb on one of my (several) Samba servers. I've not had a chance yet to check if it's happening on all of them. Most pertiant question for me is why is it
2007 May 21
1
RPC Error with PC Netlink - some additional info
Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =
2019 Jan 11
5
samba-tool auth in scripts
Am 10.01.19 um 14:09 schrieb Rowland Penny via samba: > You don't ;-) > You do what the script should have done (I feel version 0.8.10 will > soon make an appearance), export the cache to use <export > KRB5CCNAME="/tmp/dhcp-dyndns.cc"> and then use '$KRB5CCNAME' wherever > '/tmp/dhcp-dyndns.cc' appears, except for: > [...] Yes, that worked.
2002 May 28
0
query_name_response error
Hello, I've looked through multiple mailing list archives and cannot find an answer to this problem, but have found many others who are having the same problem. I hope this list can help. I have a Solaris 2.7 server running Samba 2.0.5 with multiple interfaces: hme0: 172.17.5.56 public qfe0: 172.18.30.36 backup network qfe1: 192.168.30.36 private qfe3: 172.18.10.36 private I have Samba
2002 Jun 07
0
RE: [SOLUTION]query_name_response error
Hi all, I don't make it a point to answer my own posts, but I thought this information would be useful: In researching the problem our client was having below, I found that there were two NT servers on the same subnet as my Unix server running Samba. Both these NT servers were "arguing" over who was the master browser for that network segment. Once the NT SysAdmin corrected the
2019 Mar 19
2
Samba warning message
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]
1997 Oct 15
8
OPLOCKS
Robert Dal Santo wrote: > Is there any work underway to get Samba to support OPLOCKS? I know > they are difficult to implement but I'm faced with a decisions now to buy an > NT box (Ugh!) or do a lot of messing around to get this application > to perform decently. The application in questions takes around 5 > hours to do a taks without OPLOCKS and around an hour to do the
2018 Aug 20
6
Can't connect after Ubuntu 18.04.1 Upgrade???
I have a server which we use for backing up files. Noticed there was an upgrade available to 18.04.1. Now I cannot connect to from my win7 machine to the Ubuntu share. Any thoughts on what would have changed??? Tom
1998 Feb 23
7
nmb log file entry
Hi, I am getting this log entry in the nmb.log file. Any ideas why I am getting it? query_name_response: Multiple (2) responses received for a query on subnet 9.36. 220.43 for name WHITE<1d>. This response was from IP 9.36.223.255 Thanks Chip
2018 Feb 01
2
Upgrading a ctdb cluster: samba not listening on TCP port 445
Hi all, 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 installed samba 4.7.1 with: ./configure --with-cluster-support --with-shared-modules=idmap_tdb2,idmap_ad,vfs_glusterfs --with-systemd Trying to start ctdb on the updated server fails with "
2020 Jul 13
10
Problem with network browsing
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
2019 Mar 19
1
Samba warning message
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
2008 Jul 23
3
Trouble authenticating to Samba shares with Win 2k3 ADS
I may have a deficiency in understanding the procedure for ADS authentication with samba, but most of the server setup works so far. I have bound a Red Hat Enterprise 5 server to our windows domain, it shows up in DNS and ADS, I can ping it, but I can't get samba shares to be accessible to users, or even get the smbclient to return shares properly. wbinfo -g returns the domain groups
2023 Apr 01
1
Standalone - Multiple (2) responses received for a query on subnet ...
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
2004 Jun 08
1
nmbd/nmbd_namequery.c:(104)
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)
2002 Nov 20
2
RE - servers keeps disapearing
>Hi, > >> Is there a known problem with samba servers that keeps disappearing >> from network neighborhood? Had this problem with 2.2.3, have to >> restart nmbd to get them back on, but nmbd never stops. > >Yes - there _was_ a known problem with nmbd not reregistering names. >Has disappeared since 2.2.5. > I have upgraded to 2.2.6, still have the problem, but