Shares not available under SAMBA

[geekraver]

I have set up my server with a bunch of shares and set my workgroup on the server to match my local network (WHEELER).

I cannot see \\hda from my remote machines, and if I open up the network place on the server itself, while HDA shows up I cannot open it. I get an error dialog "Unable to mount location - Failed to retrieve share list from server".

In the Samba logs I see:

dump workgroup on subnet UNICAST_SUBNET: netmask= 192.168.1.3: WORKGROUP(1) current master browser = UNKNOWN HDA 40819a23 (wheeler.local)
[2010/08/02 20:24:59, 0] nmbd/nmbd.c:854(main) nmbd version 3.4.8-59.fc12 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2010/08/02 20:24:59, 0] nmbd/asyncdns.c:155(start_async_dns) started asyncdns process 2060
[2010/08/02 20:25:23, 0] nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
*****

Samba name server HDA is now a local master browser for workgroup WHEELER on subnet 192.168.1.3

*****
[2010/08/02 20:25:23, 0] nmbd/nmbd_browsesync.c:350(find_domain_master_name_que
ry_fail)
find_domain_master_name_query_fail:
Unable to find the Domain Master Browser name WHEELER<1b> for the workgroup WHEELER.
Unable to sync browse lists in this workgroup.


Anyone know what is wrong?

Note: before I set the workgroup to WHEELER, I could open some shares from a remote machine, but other shares would not open (e.g. Videos worked but Movies didn't, even though all shares are set to be read/write by everyone). Not sure if that is related or a separate issue.

[geekraver]

I do notice that in the generated smb.conf, there is a "preferred master = yes" setting but no "local master = yes" setting. Could that be the issue?

[geekraver]

I still have the problem when accessing the HDA shares from the server itself, but I found that I can access them fine from a different PC now after a reboot. But only from one PC; other PCs can see the set of shares but either time out or give permission denied errors. And even with -d 10 on smbd there is nothing in the logs.

I'm at enough of a loss now that I am about ready to go back to WHS, which "just worked", even if it means copying 3TB of data back

What frustrates me the most is I installed Amahi about two years ago when it was very new, and it worked great then. It's all fscked now, although I suspect its the crappy Fedora OS that is most at fault.