Re: [suse-security] Problem with Windows Network Neighborhood and Linux

[Robbert Eggermont <R.Eggermont@xxxxxxxxxxxxxx>]

remote wrote:
> For a few days now,  I have noticed that my users had trouble
> using the Windows Network Neighborhood. It would not show which other
> machines were available. The situation deteriorated until now, I get an
> error message saying that I cannot access the Neighborhood at all. The funny
> thing is, if I use Windows to search for a specific computer, it will find
> it and I can access the computer´s shared directories.

Sounds like your browse master is not working correctly, probably it is
blocking requests. Have you recently installed a new windows (XP)
machine with the builtlin firewall enabled?

If you a linux box running 24/7, install samba on it an make it browse
master. Again, watch the firewall settings.

smb.conf browser settings:
# --- Browser Control Options ---

# Please _read_ BROWSING.txt and set the next four parameters according
# to your network setup. The defaults are specified below (commented
# out.) It's important that you read BROWSING.txt so you don't break
# browsing in your network!

# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
   local master = yes

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
   os level = 255

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
   domain master = yes

# Preferred Master causes Samba to force a local browser election on
# startup and gives it a slightly higher chance of winning the election
;   preferred master = yes

# --- End of Browser Control Options ---

Robbert

-- 
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here