1833822 Members
2493 Online
110063 Solutions
New Discussion

Re: samba

 
Peter Brimacombe
Frequent Advisor

samba

I just installed Samba 2.2 on HP-UX 11.00 (A.01.08)

I notice that nmbd is taking between 1 - 10 % of cpu unlike the older version (A.01.07) which takes just about 0%. Workload is the same.

I set log level =3 the main activity seems to be name query requests

I am assuming that nmbd is using up more cpu because it is answering these requests, there is no need to answer them, how can I tell nmbd to ignore them?
process_name_query_request: Name query from 142.61.36.215 on subnet 142.61.44.11 for name DRA-5-UV3<20>
[2002/04/17 13:30:59, 3] nmbd/nmbd_incomingrequests.c:(479)
process_name_query_request: Name query from 142.61.36.215 on subnet 142.61.44.11 for name DRA-5-UV3<20>
[2002/04/17 13:31:03, 3] nmbd/nmbd_incomingrequests.c:(479)
process_name_query_request: Name query from 142.61.44.27 on subnet 142.61.44.11 for name OTTAWA3<1d>
[2002/04/17 13:31:03, 3] nmbd/nmbd_incomingrequests.c:(479)
process_name_query_request: Name query from 142.61.46.92 on subnet 142.61.44.11 for name OTTTAWA1<1b>
[2002/04/17 13:31:04, 3] nmbd/nmbd_incomingrequests.c:(479)
11 REPLIES 11
Jeff Schussele
Honored Contributor

Re: samba

Peter,

If these requests are on behalf of other hosts then you want to set
wins proxy=no
in the smb.conf
file.

See the following URL for a good (best I've seen)reference doc on the smb.conf file:

http://us4.samba.org/samba/docs/man/smb.conf.5.html

HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Peter Brimacombe
Frequent Advisor

Re: samba

I set
wins proxy = no
but cpu is still between 1 and 10 %
log.nmbd shows all kinds of
process_name_query_request
messages

there must be a way to ignore these requests
Jeff Schussele
Honored Contributor

Re: samba

Hi Peter,

Look at this option:

interfaces (G)
This option allows you to override the default network interfaces list that Samba will use for browsing, name registration and other NBT traffic. By default Samba will query the kernel for the list of all active interfaces and use any interfaces except 127.0.0.1 that are broadcast capable.

The option takes a list of interface strings. Each string can be in any of the following forms:


a network interface name (such as eth0). This may include shell-like wildcards so eth* will match any interface starting with the substring "eth"

an IP address. In this case the netmask is determined from the list of interfaces obtained from the kernel

an IP/mask pair.

a broadcast/mask pair.

The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted decimal form.

The "IP" parameters above can either be a full dotted decimal IP address or a hostname which will be looked up via the OS's normal hostname resolution mechanisms.

For example, the following line:

interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0

would configure three network interfaces corresponding to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. The netmasks of the latter two interfaces would be set to 255.255.255.0.

See also bind interfaces only.

Default: all active interfaces except 127.0.0.1 that are broadcast capable

If 142.61.44.11 is NOT the I/F you want traffic thru then it needs to be excluded, or not included in the list of this option.




You might also try
browseable = no
This controls whether this share is seen in the list of available shares in a net view and in the browse list. If your clients KNOW what the share is they will still be able to mount it. Not sure but these might be responses to browses.

Another one to consider is

dns proxy (G)
Specifies that nmbd(8) when acting as a WINS server and finding that a NetBIOS name has not been registered, should treat the NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server for that name on behalf of the name-querying client.

Note that the maximum length for a NetBIOS name is 15 characters, so the DNS name (or DNS alias) can likewise only be 15 characters, maximum.

nmbd spawns a second copy of itself to do the DNS name lookup requests, as doing a name lookup is a blocking action.

See also the parameter wins support.

Default: dns proxy = yes

Also consider these WINS options
wins server (G)
This specifies the IP address (or DNS name: IP address for preference) of the WINS server that nmbd(8) should register with. If you have a WINS server on your network then you should set this to the WINS server's IP.

You should point this at your WINS server if you have a multi-subnetted network.

NOTE. You need to set up Samba to point to a WINS server if you have multiple subnets and wish cross-subnet browsing to work correctly.

See the documentation file BROWSING.txt in the docs/ directory of your Samba source distribution.

Default: not enabled

Example: wins server = 192.9.200.1

wins support (G)
This boolean controls if the nmbd(8) process in Samba will act as a WINS server. You should not set this to true unless you have a multi-subnetted network and you wish a particular nmbd to be your WINS server. Note that you should NEVER set this to true on more than one machine in your network.

Default: wins support = no

Only you know HOW this server is being used & what functions need to be enabled. But it appears to me that there is probably a setting that does not need to be there. I strongly encourage you to thoroughly look over that doc I gave you earlier.
And remember you'll have to bounce Samba whenever you make a config change for it to take effect.

HTH,
Jeff


PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Peter Brimacombe
Frequent Advisor

Re: samba

Thank you for your help Jeff

I am attaching latest smb.conf file

bottom line there is a significant difference between A.01.07 and A.01.08

There is one very large subnet -subnet mask 255.255.240, out of hundreds of PCs on the subnet, I have only a half-a-dozen users. I don't need to respond to all the broadcasts on the net - I only need to server the half-a-dozen users.

I don't know what else to try.
Peter Brimacombe
Frequent Advisor

Re: samba

I will try again to attach the smb.conf file
Peter Brimacombe
Frequent Advisor

Re: samba

hmm, never tried to add an attachment, here goes again
Jeff Schussele
Honored Contributor

Re: samba

Hi Peter,

Yep, I think the subnet is part of the problem - change that to 255.255.255.0

I'd also take the next step to only allow the hosts you NEED to serve.

Use, in the [global] section

hosts allow = host1,host2,etc

and list the users' hostnames there. That should limit Samba to only those hosts.
If any new users need access then you'll just add to this list.


HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Jeff Schussele
Honored Contributor

Re: samba

Peter,

You can also specify hosts by IP if you have trouble resolving hostnames.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Peter Brimacombe
Frequent Advisor

Re: samba

I can't change the subnet mask - it really is 255.255.240.0

I tried the hosts allow - it worked but nmbd still consumes alot of cpu cycles

the users are very sensitive to cpu consumation so I just won't run Samba

Thanks for your help Jeff.
Peter Brimacombe
Frequent Advisor

Re: samba

HP support got me the older version of SAMBA (A.01.07), I installed it and it is running and using less than 1% of the cpu.

Our network here is poorly designed so the SAMBA is getting alot of broadcasts.
Jeff Schussele
Honored Contributor

Re: samba

Hi Peter,

Glad to hear you got those cycles back.
Sorry to hear it involved a "downgrade".
I'm filing that one away for future reference.
Thanks for the info.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!