thr3ads.net - samba - [Samba] nmbd woes (still) [Apr 2003]

If this information is useful, please help other people find it:
Share via:

James

2003-Apr-13 18:07 UTC

[Samba] nmbd woes (still)

Ok I've fed this problem with about five hours of my time to post to a list
about it.  nmbd does not appear to be
doing what it should.  Why I'm not certain.  The unix host (running samba)
is not appearing in on the windows
browse list (i.e. it's not showing up in the network neighbourhood).

when I run nmbd with -d2 I get the following:

Netbios nameserver version 2.2.8 started.
Copyright Andrew Tridgell and the Samba Team 1994-2002
standard input is not a socket, assuming -D option
added interface ip=10.0.0.3 bcast=10.0.0.207 nmask=255.255.255.48
making subnet name:10.0.0.3 Broadcast address:10.0.0.207 Subnet
mask:255.255.255.48
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet
mask:0.0.0.0
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet
mask:0.0.0.0
find_response_record: response packet id 8430 received with no matching
record.
find_response_record: response packet id 8431 received with no matching
record.

The only details pertaining to the "find_response_record: response packet
id
8430 received with no matching record." message in the output that I could
find in the mailing lists or by googling was to do with malformed localhost
entries in /etc/hosts and incorrectly configured loopback interface.  I have
confirmed that my /etc/hosts correctly specifies 127.0.0.1 localhost and my
lo0 (loopback if) is correction configured.  Also, just incase you were
wondering yes that is a correct subnet mask.

My smb.conf looks like this, very minimally configured.

[global]
        workgroup = WORKGROUP
        netbios name = dough
        encrypt passwords = yes
        remote announce = 10.0.0.7/WORKGROUP
        hosts allow = 127.0.0.1 10.0.0.0/255.255.255.48

[homes]
        guest ok = no
        read only = no

[tmp]
        comment = temporary files
        path = /tmp
        read only = yes

If someone can tell me why nmbd isn't serving up names as it should be
please let me know.  I've hacked away at it all day and can't figure it
out
:).  If a higher level of debugging output is required let me know I'l
provide it.

James

2003-Apr-14 14:48 UTC

head link

[Samba] nmbd woes (still)

I've decided that my nmbd must just be "broken".  I configured
smbd to be a
wins servier and I can do everything.  The only thing is my samba server
still doesn't appear in the workgroup list.

Comments?

----- Original Message -----
From: "James" <list_mail@softhome.net>
To: <samba@lists.samba.org>
Sent: Monday, April 14, 2003 4:07 AM
Subject: [Samba] nmbd woes (still)

> Ok I've fed this problem with about five hours of my time to post to a
list> about it.  nmbd does not appear to be
> doing what it should.  Why I'm not certain.  The unix host (running
samba)
> is not appearing in on the windows
> browse list (i.e. it's not showing up in the network neighbourhood).
>
> when I run nmbd with -d2 I get the following:
>
> Netbios nameserver version 2.2.8 started.
> Copyright Andrew Tridgell and the Samba Team 1994-2002
> standard input is not a socket, assuming -D option
> added interface ip=10.0.0.3 bcast=10.0.0.207 nmask=255.255.255.48
> making subnet name:10.0.0.3 Broadcast address:10.0.0.207 Subnet
> mask:255.255.255.48
> making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet
> mask:0.0.0.0
> making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0
Subnet> mask:0.0.0.0
> find_response_record: response packet id 8430 received with no matching
> record.
> find_response_record: response packet id 8431 received with no matching
> record.
>
> The only details pertaining to the "find_response_record: response
packet
id> 8430 received with no matching record." message in the output that I
could
> find in the mailing lists or by googling was to do with malformed
localhost> entries in /etc/hosts and incorrectly configured loopback interface.  I
have> confirmed that my /etc/hosts correctly specifies 127.0.0.1 localhost and
my> lo0 (loopback if) is correction configured.  Also, just incase you were
> wondering yes that is a correct subnet mask.
>
> My smb.conf looks like this, very minimally configured.
>
> [global]
>         workgroup = WORKGROUP
>         netbios name = dough
>         encrypt passwords = yes
>         remote announce = 10.0.0.7/WORKGROUP
>         hosts allow = 127.0.0.1 10.0.0.0/255.255.255.48
>
> [homes]
>         guest ok = no
>         read only = no
>
> [tmp]
>         comment = temporary files
>         path = /tmp
>         read only = yes
>
> If someone can tell me why nmbd isn't serving up names as it should be
> please let me know.  I've hacked away at it all day and can't
figure it
out> :).  If a higher level of debugging output is required let me know I'l
> provide it.
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

mwestern@sola.com.au

2003-Apr-15 02:16 UTC

head link

[Samba] nmbd woes (still)

I share your pain.

I've been playing with this very thing and have just joined the list.  I too
have been bashing my head against the wall.

I've been trying to get static mappings to work for quite a while and
finally after much annoyance I've got

[global]
	wins support = yes
	name resolve order = wins dns lmhosts hosts
	dns proxy = yes


then start chucking entries into /etc/hosts and voila it starts to resolve
these static mappings..

here's what I also figured out (whether it's a bug or not).  nmbd WINS
doesn't like having complicated addressing.:

1.  server.  10.160.0.170
		 203.45.56.78

test client.  203.45.56.79 - gw 203.45.56.1
		  10.160.0.50 - WINS 10.160.0.170  

ie secondary address on a winxp machine is the one pointing directory to
wins.  this fails to resolve anything sometimes and other times it does a
few and drops.  as soon as i simplify my IP addressing on the client
ie 10.160.0.50	only it works a treat.  

I've been trying to replace a MS WINS server with a samba one and so far the
microsoft one has been far less pain.  

anyway, this probably won't help your problem, but i felt like a rant...
(also i only got this message just then, no history)....
M
		  
	

-----Original Message-----
From: samba-bounces+mwestern=affairs.net.au@lists.samba.org
[mailto:samba-bounces+mwestern=affairs.net.au@lists.samba.org]On Behalf
Of James
Sent: Tuesday, April 15, 2003 12:19 AM
To: samba@lists.samba.org
Subject: Re: [Samba] nmbd woes (still)


I've decided that my nmbd must just be "broken".  I configured
smbd to be a
wins servier and I can do everything.  The only thing is my samba server
still doesn't appear in the workgroup list.

Comments?

----- Original Message -----
From: "James" <list_mail@softhome.net>
To: <samba@lists.samba.org>
Sent: Monday, April 14, 2003 4:07 AM
Subject: [Samba] nmbd woes (still)

> Ok I've fed this problem with about five hours of my time to post to a
list> about it.  nmbd does not appear to be
> doing what it should.  Why I'm not certain.  The unix host (running
samba)
> is not appearing in on the windows
> browse list (i.e. it's not showing up in the network neighbourhood).
>
> when I run nmbd with -d2 I get the following:
>
> Netbios nameserver version 2.2.8 started.
> Copyright Andrew Tridgell and the Samba Team 1994-2002
> standard input is not a socket, assuming -D option
> added interface ip=10.0.0.3 bcast=10.0.0.207 nmask=255.255.255.48
> making subnet name:10.0.0.3 Broadcast address:10.0.0.207 Subnet
> mask:255.255.255.48
> making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet
> mask:0.0.0.0
> making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0
Subnet> mask:0.0.0.0
> find_response_record: response packet id 8430 received with no matching
> record.
> find_response_record: response packet id 8431 received with no matching
> record.
>
> The only details pertaining to the "find_response_record: response
packet
id> 8430 received with no matching record." message in the output that I
could
> find in the mailing lists or by googling was to do with malformed
localhost> entries in /etc/hosts and incorrectly configured loopback interface.  I
have> confirmed that my /etc/hosts correctly specifies 127.0.0.1 localhost and
my> lo0 (loopback if) is correction configured.  Also, just incase you were
> wondering yes that is a correct subnet mask.
>
> My smb.conf looks like this, very minimally configured.
>
> [global]
>         workgroup = WORKGROUP
>         netbios name = dough
>         encrypt passwords = yes
>         remote announce = 10.0.0.7/WORKGROUP
>         hosts allow = 127.0.0.1 10.0.0.0/255.255.255.48
>
> [homes]
>         guest ok = no
>         read only = no
>
> [tmp]
>         comment = temporary files
>         path = /tmp
>         read only = yes
>
> If someone can tell me why nmbd isn't serving up names as it should be
> please let me know.  I've hacked away at it all day and can't
figure it
out> :).  If a higher level of debugging output is required let me know I'l
> provide it.
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

James

2003-Apr-15 07:40 UTC

head link

[Samba] nmbd woes (still)

I feel that all aspects of smbd are working correctly, I can map drives
browse shares etc...
simply by accessing the shares via a location bar \\machine\share.
It's just the machine doesn't appear in the my network places workgroup.

Could it be that nmbd doesn't like non 0xffffffff netmasks?  I wish nmbd was
more thoroughly
documented.  The manpage offers no help.

----- Original Message -----
From: "James" <list_mail@softhome.net>
To: <samba@lists.samba.org>
Sent: Monday, April 14, 2003 4:07 AM
Subject: [Samba] nmbd woes (still)

> Ok I've fed this problem with about five hours of my time to post to a
list> about it.  nmbd does not appear to be
> doing what it should.  Why I'm not certain.  The unix host (running
samba)
> is not appearing in on the windows
> browse list (i.e. it's not showing up in the network neighbourhood).
>
> when I run nmbd with -d2 I get the following:
>
> Netbios nameserver version 2.2.8 started.
> Copyright Andrew Tridgell and the Samba Team 1994-2002
> standard input is not a socket, assuming -D option
> added interface ip=10.0.0.3 bcast=10.0.0.207 nmask=255.255.255.48
> making subnet name:10.0.0.3 Broadcast address:10.0.0.207 Subnet
> mask:255.255.255.48
> making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet
> mask:0.0.0.0
> making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0
Subnet> mask:0.0.0.0
> find_response_record: response packet id 8430 received with no matching
> record.
> find_response_record: response packet id 8431 received with no matching
> record.
>
> The only details pertaining to the "find_response_record: response
packet
id> 8430 received with no matching record." message in the output that I
could
> find in the mailing lists or by googling was to do with malformed
localhost> entries in /etc/hosts and incorrectly configured loopback interface.  I
have> confirmed that my /etc/hosts correctly specifies 127.0.0.1 localhost and
my> lo0 (loopback if) is correction configured.  Also, just incase you were
> wondering yes that is a correct subnet mask.
>
> My smb.conf looks like this, very minimally configured.
>
> [global]
>         workgroup = WORKGROUP
>         netbios name = dough
>         encrypt passwords = yes
>         remote announce = 10.0.0.7/WORKGROUP
>         hosts allow = 127.0.0.1 10.0.0.0/255.255.255.48
>
> [homes]
>         guest ok = no
>         read only = no
>
> [tmp]
>         comment = temporary files
>         path = /tmp
>         read only = yes
>
> If someone can tell me why nmbd isn't serving up names as it should be
> please let me know.  I've hacked away at it all day and can't
figure it
out> :).  If a higher level of debugging output is required let me know I'l
> provide it.
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

Matthew Western

2003-Apr-15 23:11 UTC

head link

[Samba] nmbd woes (still)

>  I wish nmbd was
>more thoroughly
>documented.  The manpage offers no help.
me too.  i believe that version 3 of samba has replication between servers
as one of the new features, lets hope that it has a decent stack of docs as
a new 'feature'.  :)

Possibly Parallel Threads

Search for more apparently analagous threads

samba - Apr 2003 - nmbd woes (still)

[Samba] nmbd woes (still)

[Samba] nmbd woes (still)

[Samba] nmbd woes (still)

[Samba] nmbd woes (still)

[Samba] nmbd woes (still)

Possibly Parallel Threads