I have tried everything I can think of to get this Samba share working. I originally used the KDE built-in GUI in my Centos 5 distro to configure smb.conf, but that wasn't working so I dove into the command line. Here is my smb.conf file:

[global]

workgroup=funkytown
server string = Welcome to Funkytown

netbios name=asudermaserver

interfaces = eth0 lo
#hosts allow = 127. 192.168.12. 192.168.13.

log file = /var/log/samba/%m.log
max log size = 50
security = user
passdb backend = tdbsam


#============================ Share Definitions ===========================

[homes]
comment = Home Directories
browseable = no
writable = yes
; valid users = %S
; valid users = MYDOMAIN\%S

[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
; guest ok = no
; writable = No
printable = yes


[fileserve]
path = /fileserve
writeable = yes
browseable = yes
valid users = andy




When I try to access the share from windows (map network drive //asudermaserver/fileserve with the correct username and password) I get a Network Path could not be found error. Also, the share is visible in my network connections under the workgroup FUNKYTOWN

Alright, I figured it out. I disabled IPtables and it worked fine.

What version of Samba was it, and what version of Windows was it linking to? I'm trying to get SuSE 10's Samba 3.0.24 to connect to Windows Sever 2008, and as long as I don't put the server into a domain, it works, but only when I map drives. Just plain browsing doesn't work. And as soon as the server is set up in a domain, it doesn't work at all. I know Samba 3.2.x works with Server 2008, but I'm on the prowl for a simpler solution, as it'll take a while to update Samba on that box.

I'm not sure what version of Samba that was. That machine isn't running anymore. I was using CentOS 5.2 and connecting to XP Pro. I was never really able to browse my smb share either, just able to map the drive. I didn't really have any need to browse to the share.

iptables is your workstation firewall. You really don't want to leave home without it...

By default, windows file sharing is disabled on purpose. Those protocols
are often the source/cause of malicious mischief. When you open this door, make sure to limit access to your own network LAN.

~~~ 0;-Dan

Huge books and hundreds of pages have been written about windows network browsing -- "network places" not web browser. Not only do the several windows variants 95/98/Me/NT/.../XP/Home/Vista have their own individual dance, but the dance seems to change based on which variants you try to make play together. Sigh. You can use the SAMBA configuration to enable most of the variants.

Good luck,
~~~ 0;-Dan

I suppose I wasn't clear when I used the term "browse." I was referring to network browsing via what used to be called "Network Neighborhood" and what Windows XP refers to as "My Network Places."

I appreciate the advice. As I stated above, that box isn't running anymore. I didn't really like the way I had it set up (It was rather insecure, partly due to the iptables being disabled). I am running a new box and will be configuring samba a little bit differently.