_*To jgdiablo*_:-
If you have the only Samba / OS X computer on your subnet, then I guess you could try editing your '/etc/smb.conf' config-file, by adding the following settings at the bottom so that they override any prior ones:
\[global\]
domain master = no
local master = yes
preferred master = yes
os level = 65
(Note: These settings are lifted straight from '[The Official Samba 3.2.x HOWTO and Reference Guide > Chapter 10. Network Browsing > Example 10.2. Local master browser smb.conf|http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrow sing.html#lmbexample]'. Also, just a reminder that, to edit this protected config-file, you'll normally need to use escalated privileges, e.g. via 'sudo', to run as root either a command-line editor or GUI editor.)
_*To all*_:-
In addition to the "local master browser" option, just another reminder that there are also other things you could try if you're having firewall-related problems (as also discussed in earlier posts)... For instance, if your subnet's computers are using their own firewalls (for internal-traffic filtering),
and all the usual NetBIOS / SMB ports (TCP 139 & 445, UDP 137-138 & possibly others) have already been opened up, but your Macs are still not seeing any networked Windows PCs' names, you could try opening up UDP port 1900 (SSDP / MS-mDNS) on your +Windows PCs'+ firewalls. Also, double-check that your Macs' firewalls (if they're 2-way port-based such as the built-in 'ipfw' via a WaterRoof front-end) do accept incoming UDP traffic with
source NetBIOS / SMB ports, not just destination ones.
{I realized the possible importance of SSDP "local-DNS" broadcast queries the hard way, after recently upgrading to a new Mac which came with OS X 10.6.0 (now updated to 10.6.2). At first I couldn't get any of my household's networked XP PCs to show up in the new Finder's Network browser or its Sharing sidebar-section. Also, the 'findsmb' util couldn't see any of the PCs' names. However, I
could still connect via raw IP-addresses just as I always used to on my trusty old PM G4 (MDD) under Tiger, so I knew that my particular case was just an SMB name-resolution issue. I ended up analyzing a 3rd-party firewall's log on one of the networked PCs, where the SSDP incoming traffic immediately stood out. I'm not sure whether Samba is directly issuing the SSDP queries, or some other service's client is doing that and Samba is just (usually?) able to access the resulting local-DNS records. Or then again, the SSDP traffic could turn out to just be sheer coincidence after all! So far, the PCs' visibility has survived some reboots of both Mac and PCs, so I guess I'll keep my fingers crossed. ;-)}
Anyway, good luck to everyone,
--P