similar to: RE: [SOLUTION]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

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)

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

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

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)

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

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

Hi I am trying to enable my dhcpd and pxelinux setup to use a specific config file for a booting client. I have read the pxelinux page for this (http://syslinux.zytor.com/pxe.php#special) but still seem to be encountering problems. When running the dhcpd with the '-d' debug option the daemon sees the DHCPDISCOVER from the client and then core dumps. On the client side the DHCPDISCOVER

Hi I have a problem with samba 2.2.2. (see below) I'm sure it's easy to solve but I can't figure out what to do. The thing I find confusing is that the newer and more powerful server can't perform as good as the old one. Any ideas? /Jonas Story: We had all our user homes on a Sun Ultra 2 (solaris 2.6, 30Gb store) and samba 2.0.6, and all was fine. But we ran out of disk and moved

Hello! Problem: Outbound data goes through default interface instead of specified, causing congestion. Question: How can I instruct samba to tell Solaris to SEND data through specified network interface? Detailed: I have a solaris filesserver with two network interfaces, hme0 and hme1. I'd like NFS to use hme0 and smb hme1. I intsruct samba to only listen for connections on the

I run samba 2.0.6 on Sun ultra enterprise 2 server. Lately the logs have been filled with [1999/11/29 20:11:19, 0] lib/util_sock.c:write_socket_data(537) write_socket_data: write failure. Error = Broken pipe [1999/11/29 20:19:31, 0]

Hi all, I am having an issue where my hme0 interface is always turning up and down with dhclient requesting a lease. I am thinking this could be the same issue described by Jeremy Chadwick on June 9th: http://lists.freebsd.org/pipermail/freebsd-stable/2013-June/073711.html Everything was fine on 8.2-STABLE and older versions. It was then upgraded directly to 9.0-STABLE

> > > > If it is that then either the solaris send window or the > client receive > > window is too small. > > > > Or, we could go for a vastly less complex explanation - shout > is known to not > send at the correct rate. Don't use it. > > Mike <p>Hi all, I understand, what for a livestreamer can I take ? any references ? A network

Pardon the long log file but I'm fairly new to WINS servers and probably don't know what I'm doing. We've have two subnets (lets call them xxx.xxx.xxx.??? and yyy.yyy.yyy.??) I have one samba/linux server on both networks xxx.xxx.xxx.2 and yyy.yyy.yyy.2. xxx.xxx.xxx.2 is set up to be a domain master and yyy.yyy.yyy.2 is setup to be a local master with xxx.xxx.xxx.2 as its master.

I've been prowling through the FreeBSD and Snort list archives in search of information on setting up snort on a FreeBSD bridge(4) that logs to a remote postgres box via a third interface (hme0) Snort is being started with the following command: /usr/local/bin/snort -A full -D -e -d -s -i fxp0 -c /usr /local/etc/snort.conf Where fxp0 and fxp1 are in the bridge output from sysctl:

Samba 3.0.23a Solaris 9 I have reecently upgraded my Samba server to the above version and joined an Active Directory domain. Since having achieved this I have been encountering a strange problem. On some of my printers the printing of banner pages is enabled. In some instances when a user submits a print job it prints with root as the owner on the banner page and not the user's who

I am currently running Samba 2.2.8a in a production environment on a Unix box with Solaris 8. I am hoping to migrate and upgrade to Samba 3.0.10 on a Solaris 10 box. I am however having difficulties joining the NT domain with my new (still test server). Initially I provided the administrator with the ip address and the netbios name of the samba server so that a trust account could be created.

Hi All, Samba 3.0.2a is installed on Solaris and works fine with windows NT clients, but it doesn't work with windows XP client which complains that the share path can't find. Here is the basic coniguration: workgroup = GLOBAL netbios name = test netbios aliases = test server string = test Samba 3.0.2a interfaces = hme0 bind interfaces only

On Mon, 2003-01-20 at 08:34, Daniel Knoll wrote: > Hi all, > > I understand, what for a livestreamer can I take ? any references ? for vorbis uses icecast2 and either ices2/oddcast etc, as they are tested more. > A network question: > If I decrease the MTU (on hme0 interface is 1500) maybe it can be a solution > for my problem with broken streams? ok, so it's solaris.

Hello, I have set up an IPSec tunnel to create a VPN. It works well, I can ping and telnet back and forth with no problems. I am, however, struggling to get Samba to work. The setup: Samba 2.0.7 running on Sparc Solaris 2.6 The VPN tunnel is between a OpenBSD 2.7 server and a Netopia R9100 router. The tunnel is negotiated using IKE. The server running Samba receives NetBIOS packets, I can see