Howto: Fix Windows share browsing issues

[glave]

Done.

[dmizer]

In pengo, one problem may be this line "wins support = true". Please remove that as it doesn't do what you think it does. Please see: man smb.conf for more information on why.

Also in pengo, comment or delete this line: "/var/lib/samba -s /bin/false %u"

In joust, you'll need to add two lines.
1) name resolve order = lmhosts host wins bcast
2) netbios name = JOUST

I think there are other problems as well, but before doing too much editing I'd like to learn a bit more about why you configured these they way you did, since they're quite different. What are you wanting to do with these shares?

[glave]

Pengo is working now and can browse. Pengo was the main focus, but I'll double check all steps on Joust and post results.


The wild difference in the 2 are pretty simple, Joust was 100% hand written, and Pengo was originally from webmin. Joust isn't actually sharing or mounting anything at all, and only has samba running purely for the purpose of populating itself into the workgroup when browsing it. No real purpose other than an easy to see 'head count' when I browse shares.

Pengo will have shares soon enough, and will be mounting some other shares. Its config file is overly complicated(as I see now) so I will be trimming it down soon enough.

[dmizer]

Pengo is working now and can browse.

Fantastic. I'll look forward to hearing about Joust now.

[glave]

Joust is now working as well. I hadn't completed the nsswitch.conf step on Joust.

Kudos on the help, its much appreciated. Is there a single underlying change in Jaunty that caused this to happen? I know absolutely that under Hardy and Ibex I didn't have these issues.

[dmizer]

Joust is now working as well. I hadn't completed the nsswitch.conf step on Joust.

Kudos on the help, its much appreciated. Is there a single underlying change in Jaunty that caused this to happen? I know absolutely that under Hardy and Ibex I didn't have these issues.

Glad it's working!

The first post in this thread is the accumulated knowledge of suffering through it myself, as well as helping people with this problem for almost 3 years now, so ... no, it's not a recent development. You've just been lucky I think.

Here's one from 2007 for example: http://ubuntuforums.org/showthread.php?t=483352

[lavinog]

mdns4_minimal would be used if you had a local DNS server.

I thought the mdns was for the avahi daemon (which used to be installed by default). It allowed name resolution in the .local domain
I could be wrong though, but it is what I always thought.

[dmizer]

I thought the mdns was for the avahi daemon (which used to be installed by default). It allowed name resolution in the .local domain
I could be wrong though, but it is what I always thought.

You're quite right. It's for zero conf networking: http://en.wikipedia.org/wiki/Zeroconf

I stand corrected.

[fantom1979]

Dmizer,

I was having the same problem, but after following the steps in your first post, everything is working great now. I am a Ubuntu noob and I just wanted to say thanks for putting that info together.

[TheMussulman]

Thanks dmizer
My ubuntu works correctly now!!