HI
I,ve just noticed this morning that the network browsing is not stable. like samba server is not accessible, users can not see the login screen in 1st attempt. i am wondering what could be the reason.
[global]
workgroup = WORKGROUP
netbios name = BCH-Fileshare
name resolve order = bcast host lmhosts wins
server string = “”
printcap name = cups
cups options = raw
use client driver = yes
map to guest = Bad User
local master = yes
preferred master = yes
os level = 65
usershare allow guests = Yes
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
Share disabled by YaST
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
Share disabled by YaST
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
Share disabled by YaST
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775
[test]
path = /test
read only = no
valid users = timothy
You should put your NIC in the external zone so your workstation get’s full firewall protection. Then you allow services “sanba server”, “netbios server”. And also the connection tracking module located at Yast –> firewall –> broadcast –> 192…0/24. See the screenshots at this location: SuSEfirewall2: HowTo Firewall a Suse / openSUSE Workstation for LAN Network Traffic
>
> HI
> I,ve just noticed this morning that the network browsing is not stable.
> like samba server is not accessible, users can not see the login screen
> in 1st attempt. i am wondering what could be the reason.
>
<snip>
>
>
davesal;
This could be anything from bad hardware to a configuration problem. I would
try to get a bit more information on the problem. For testing purpose only;
add to your /etc/samba/smb.conf the parameter:
log level = 1
You can now find some fairly detailed log information in:
/var/log/samba/log.nmbd and
/var/log/samba/log.smbd
To get even more information increase the log level to 3. The higher the
number the more is logged, but after about 3 the logs are so long it is hard
to find anything useful, just too much stuff to sort out.
I suspect either it is hardware or you have two machines fighting over who is
the master browser. But that is just a conjecture.
Once you have everything sorted out be sure to remove the “log level”
parameter.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
>
> i checked it with log level=1 the thing i found is this
>
> SAMBA NAME SERVER BCH-FILESHARE IS NOW A LOCAL MASTER BROWSER FOR
> WORKGROUP WORKGROUP ON SUBNET 10.4.97.215
>
> but it didn,t say anything about Preferred Master, or is it the same as
> above command
>
>
davesal;
The workgroup computers hold an election to determine who should be the master
browser. Setting Preferred Master only gives Samba a slight edge in the
election. It appears that your Samba server won the election which is what
you want. Just watch to see if when the network is giving you problems there
is an indication that Samba is no longer the local Master Browser or that
some other machine keeps calling for an election.
Have you checked your cables/switches etc.? Is the problem more likely to
occur when one particular machine is booted?
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
**[2009/05/01 10:58:53, 0] nmbd/nmbd_incomingdgrams.c:process_local_master_announce(308)
process_local_master_announce: Server DC6WD341 at IP 10.4.97.91 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
[2009/05/01 10:58:53, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(148)
*****:
Samba name server BCH-FILESHARE has stopped being a local master browser for workgroup WORKGROUP on subnet 10.4.97.215
>
> well i didn’t boot any machine but i got this
>
> [2009/05/01 10:58:53, 0]
> NMBD/NMBD_INCOMINGDGRAMS.C:PROCESS_LOCAL_MASTER_ANNOUNCE(308)
> PROCESS_LOCAL_MASTER_ANNOUNCE: SERVER DC6WD341 AT IP 10.4.97.91 IS
> ANNOUNCING ITSELF AS A LOCAL MASTER BROWSER FOR WORKGROUP WORKGROUP AND
> WE THINK WE ARE MASTER. FORCING ELECTION.
> [2009/05/01 10:58:53, 0]
> NMBD/NMBD_BECOME_LMB.C:UNBECOME_LOCAL_MASTER_SUCCESS(148)
> *****:
>
> SAMBA NAME SERVER BCH-FILESHARE HAS STOPPED BEING A LOCAL MASTER
> BROWSER FOR WORKGROUP WORKGROUP ON SUBNET 10.4.97.215
>
> *****
> [2009/05/01 10:59:12, 0]
> NMBD/NMBD_BECOME_LMB.C:BECOME_LOCAL_MASTER_STAGE2(395)
> *****
>
> SAMBA NAME SERVER BCH-FILESHARE IS NOW A LOCAL MASTER BROWSER FOR
> WORKGROUP WORKGROUP ON SUBNET 10.4.97.215
>
>
> so it hold an election again at 10:59:12. Is this normal. or some other
> system is keep calling this election
>
> Please reply soon
>
davesal;
No and this is the root of your problem, two machines fighting.
If the client is a Windows machine you can use regedit ->
HKEY_LOCAL_MACHINE\System\current control set\services\browser\parameters and
set the preferred master to FALSE ( I do not recall the exact name of the key
but it is obvious when you get there).
If the client is another Linux machine do not set preferred master or elevate
the os level.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green