Displaying 4 results from an estimated 4 matches for "reportingan".
Did you mean:
reporting
2004 Jun 08
1
nmbd/nmbd_namequery.c:(104)
...unning from the shares.
Jun 8 14:53:53 krypton nmbd[3096]: [ID 702911 daemon.error]
query_name_response: Multiple (2) responses received for a query on
subnet 10.2.17.8 for name LOGANCC<1d>.
Jun 8 14:53:53 krypton nmbd[3096]: [ID 702911 daemon.error] This
response was from IP 10.2.18.12, reportingan IP address of 10.2.18.12.
Jun 8 14:53:53 krypton nmbd[3096]: [ID 702911 daemon.error] [2004/06/08
14:53:53, 0] nmbd/nmbd_namequery.c:(104)
Jun 8 14:53:53 krypton nmbd[3096]: [ID 702911 daemon.error]
query_name_response: Multiple (3) responses received for a query on
subnet 10.2.17.8 for name LOGA...
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
2001 Nov 02
0
Samba namequery error
...935]: [2001/08/14 22:29:04, 0]
nmbd/nmbd_namequery.c:query_name_response(105)
Aug 14 22:29:04 tux nmbd[2935]: query_name_response: Multiple (2)
responses received for a query on subnet 192.168.2.7 for name
DOMEINA<1d>.
Aug 14 22:29:04 tux nmbd[2935]: This response was from IP 192.168.2.2,
reportingan IP address of 192.168.2.2.
Aug 14 22:33:58 tux nmbd[2935]: [2001/08/14 22:33:58, 0]
nmbd/nmbd_namequery.c:query_name_response(105)
Aug 14 22:33:58 tux nmbd[2935]: query_name_response: Multiple (2)
responses received for a query on subnet 192.168.2.7 for name
DOMEINA<1d>.
Aug 14 22:33:58 tu...
2003 Dec 01
0
No subject
...ba.org/pipermail/samba/
Hi!
I am currently fighting with the following messages:
...
[2001/07/10 19:28:57, 0] nmbd/nmbd_namequery.c:(104)
query_name_response: Multiple (2) responses received for a query on subnet 141.43.132.151 for name AET<1d>.
This response was from IP 141.43.132.161, reportingan IP address of 0.0.0.0.
...
141.43.132.161 is the WINS server (also a samba server).
Following the advice on this list, I checked that the server is not
dualhomed and also tried to hardcode the interface:
interfaces = 141.43.132.161/26
bind interfaces only = yes
but to now avail.
I have traced...