samba server problem: nmbd/nmbd_incomingrequests.c:process_name_refresh_request

samba server problem: nmbd/nmbd_incomingrequests.c:process_name_refresh_request

Post by HchC » Tue, 03 Dec 2002 18:43:32



I am running RH 8.0 and my samba server is working.
I do nothing, and the samba server just not working and I got the message as
follow:

nmbd/nmbd_incomingrequests.c:process_name_refresh_request

Any one can figure out what is the problem?

 
 
 

samba server problem: nmbd/nmbd_incomingrequests.c:process_name_refresh_request

Post by Paul Lutu » Wed, 04 Dec 2002 02:48:49



> I am running RH 8.0 and my samba server is working.
> I do nothing, and the samba server just not working and I got the message as
> follow:

> nmbd/nmbd_incomingrequests.c:process_name_refresh_request

> Any one can figure out what is the problem?

Must be something about your system, which you do not identify, or your
Samba setup, which you do not describe, or your distribution, which you do
not specify.

--
Paul Lutus
www.arachnoid.com

 
 
 

samba server problem: nmbd/nmbd_incomingrequests.c:process_name_refresh_request

Post by HchC » Wed, 04 Dec 2002 18:30:45


Well, after changing the workgroup name on both side, my W2k box and
smb.conf, my samba server is working now.
But I still do not know why this happened.




> > I am running RH 8.0 and my samba server is working.
> > I do nothing, and the samba server just not working and I got the
message as
> > follow:

> > nmbd/nmbd_incomingrequests.c:process_name_refresh_request

> > Any one can figure out what is the problem?

> Must be something about your system, which you do not identify, or your
> Samba setup, which you do not describe, or your distribution, which you do
> not specify.

> --
> Paul Lutus
> www.arachnoid.com

 
 
 

samba server problem: nmbd/nmbd_incomingrequests.c:process_name_refresh_request

Post by Paul Lutu » Wed, 04 Dec 2002 18:58:37



> Well, after changing the workgroup name on both side, my W2k box and
> smb.conf, my samba server is working now.
> But I still do not know why this happened.

It's obvious. Both machines must belong to the same workgroup. Belonging
to the same tcp/ip subnet is only one of several steps.

This is fully covered in the Samba HOWTO tutorials.

--
Paul Lutus
www.arachnoid.com

 
 
 

samba server problem: nmbd/nmbd_incomingrequests.c:process_name_refresh_request

Post by HchC » Wed, 04 Dec 2002 23:00:00


The original workgroup name of w2k is also the same as the samba server. It
is "myworkgroup". I just change it on both side to "workgroup".




> > Well, after changing the workgroup name on both side, my W2k box and
> > smb.conf, my samba server is working now.
> > But I still do not know why this happened.

> It's obvious. Both machines must belong to the same workgroup. Belonging
> to the same tcp/ip subnet is only one of several steps.

> This is fully covered in the Samba HOWTO tutorials.

> --
> Paul Lutus
> www.arachnoid.com

 
 
 

samba server problem: nmbd/nmbd_incomingrequests.c:process_name_refresh_request

Post by HchC » Thu, 05 Dec 2002 19:53:14


I think I found the real problem, I would appreciated if you can help to
solve this problem.

I have one Linux system running samba server, two window box one is W2k
another one is Win me.
Not because of changing the workgroup name to make the samba server work.
The real problem is: if Win me join the workgroup and my W2k restart. W2k
can not see the samba server.
Or we can said: without Win me it work well.
Or, if W2k join the workgroup first and stay there, it's work.
Win me does not work, I mean can not see samba server, but can assign a
network drive to user's Home directory.




> > Well, after changing the workgroup name on both side, my W2k box and
> > smb.conf, my samba server is working now.
> > But I still do not know why this happened.

> It's obvious. Both machines must belong to the same workgroup. Belonging
> to the same tcp/ip subnet is only one of several steps.

> This is fully covered in the Samba HOWTO tutorials.

> --
> Paul Lutus
> www.arachnoid.com

 
 
 

1. Samba: nmbd/nmbd_namequery.c:query_name_response messages

I did a tcpdump to examine the NBT packets going across the LAN which
is causing my Samba clients to log messages about:
query_name_response: Multiple (2) responses received
---

The tcpdump showed the following.

01:41:19.943010 linux.netbios-ns > 192.168.0.255.netbios-ns: NBT UDP
PACKET(137): QUERY; REQUEST; BROADCAST (D
F)
01:41:19.943124 linux.netbios-ns > 192.168.0.255.netbios-ns: NBT UDP
PACKET(137): QUERY; REQUEST; BROADCAST (D
F)
01:41:20.033147 lnx04.netbios-ns > linux.netbios-ns: NBT UDP
PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST (
DF)
01:41:20.034283 lnx04.netbios-ns > linux.netbios-ns: NBT UDP
PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST (
DF)

---
At the this exact time I saw in the /var/log/samba/log.nmb

[2006/09/29 01:41:20, 0] nmbd/nmbd_namequery.c:query_name_response(104)
  query_name_response: Multiple (2) responses received for a query on
subnet 192.168.0.114 for name LANSYS<1d>
.
  This response was from IP 192.168.0.201, reporting an IP address of
192.168.0.201.
[2006/09/29 06:45:25, 0] nmbd/nmbd_namequery.c:query_name_response(104)
  query_name_response: Multiple (2) responses received for a query on
subnet 192.168.0.114 for name LANSYS<1d>
.
  This response was from IP 192.168.0.201, reporting an IP address of
192.168.0.201.
---

The sequence of events occurred again five hours later.  First was the
double query request from machine [ linux ] and then two responses from
the Samba server [ lnx04 ]. In all other queries made by the machine [
linux ] the query received a response before that second query was
made. ie.

04:08:24.545699 linux.netbios-ns > 192.168.0.255.netbios-ns: NBT UDP
PACKET(137): QUERY; REQUEST; BROADCAST (DF)
04:08:24.552269 lnx04.netbios-ns > linux.netbios-ns: NBT UDP
PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST (DF)
04:13:26.553281 linux.netbios-ns > 192.168.0.255.netbios-ns: NBT UDP
PACKET(137): QUERY; REQUEST; BROADCAST (DF)
04:13:26.639053 lnx04.netbios-ns > linux.netbios-ns: NBT UDP
PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST (DF)
---

So it appears the multiple response message is bogus. I have no other
machine in the LAN with the
NetBIOS name of LANSYS<1d> acting as the domain master. It appears the
lag in the response
from machine [ lnx04 ] are causing the [ Multiple (2) responses
received ... ] messages.

2. alphastation 600 5/266 help!

3. llllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllll

4. Building Emacs with Motif

5. P L, PPCQAU7HGUTGG..........................VCCCCCCCCCCCCC AAAAAAAAAAAAAAAAAAAAANNNNNNNNNNNNNNNNNN777777777777777RRRRRRRRRRRRRRRRRBBBBBBBBBBBBBBBBBBBBBBB

6. TERM

7. TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTT

8. UK Linux Advocacy

9. small problem with nmbd and samba on redhat 5

10. Samba nmbd daemon problem

11. SAMBA - nmbd problems

12. Samba: NMBD broadcast problems

13. samba - nmbd problem - SOCKET READ ERROR