Samba - How easy is it to configure?

[JonR]

I've only been using Linux for six months but threads about Samba problems always seem to attract a large readership.

So I fell to wondering, how easy is it to get Samba to do what you want?

[Jman]

I had few problems, but I wasn't setting samba up as a server, only as a client in a Windows network.

There is the nifty web based swat administration tool available.

[Algernon]

Samba works Ok as a fileserver besides the issues in password asking in share mode...

I have not been able to solve the print server problem.
Fedora works Ok with my Canon LBP-4u but I have not been print anything else besides plain text from my Win-98Se box.
Since the cable actually reaches to my Win box I have just attached it to that directly for now. Hopefully I can place both boxes to some closet soon.

edit:
This turned out to being a Windows problem...the poor thing needed postscript drivers (free from adobe) to be able to communicate to Cups. Now I have print-, www- and fileserver all in the same box.

-M

[engwnbie]

I have configured and had Samba working in all modes. I have had no trouble configuring my network. I have Win 2K, XP, FC2, Mdk10 all working together just fine. Have had trouble getting to print on my Win XP shared printer, one day I will try harder to fix that. There are many ways to config Samba eg GUI or Text mode they all worked fine for me. There are many good how to around, at fedoranews.org, fedoraforum.org, there is even a great pdf file in the Samba directory showing different ways to configure. Just can't give up trying to learn, it's all good.

[thepoch]

Samba wasn't really a problem for me to configure. Only the bug in 3.0.3 preventing "security=share" working got me. Had to post several times in fedora-list before someone replied with a link to samba.org's bugzilla report. I've noted that there is a problem with FC1's 3.0.4 samba update as well, as our server has some user-specific read-write permissions. It wouldn't work with 3.0.4, but it works very well with 3.0.2 and the originally shipped 3.0.0 with FC1.

Oh, and there's still a bug in system-config-samba that removes the "workgroup" name in smb.conf when you use the gui to configure. I haven't bugzilla'd it as no one else has confirmed that the bug exists.

[Algernon]

Samba wasn't really a problem for me to configure. Only the bug in 3.0.3 preventing "security=share" working got me. Had to post several times in fedora-list before someone replied with a link to samba.org's bugzilla report. I've noted that there is a problem with FC1's 3.0.4 samba update as well, as our server has some user-specific read-write permissions. It wouldn't work with 3.0.4, but it works very well with 3.0.2 and the originally shipped 3.0.0 with FC1.

Oh, and there's still a bug in system-config-samba that removes the "workgroup" name in smb.conf when you use the gui to configure. I haven't bugzilla'd it as no one else has confirmed that the bug exists.

I can confirm this to be a problem with FC2 default installation. Had me going for a while
before I noticed what was going on.

-M

[ghaefb]

I only use smbmount for transfering data between win/linux. That's all I need

[ghenry]

Hard core Samba:

http://samba.idealx.org/smbldap-howto.en.html

Going through it over this week.

[i686]

I can usually get samba up and running straight away 95% of the time but the other 5% takes some tweaking and fine tuning..

i686

[iontyre]

I must be an idiot. I have had IMMENSE problems with samba, including the fact that FC2 does not install SWAT no matter what options you select during the install. I finally found it on the fourth install cd and manually installed it. Got two books out of the library on Linux system administration and finally got my win boxes to see the samba server. The samba side still seems to have problems seeing the win boxes though, at least in finding the shares. It shows the boxes exist, but throws an error when trying to display the shares.

[ghenry]

You're learning though, and you will never forget this ;)

[ricc]

I can have my Samba server running, but the problem is, users unable to access the shared file, eventhough I've done the config.. wut else I've to check?

[sk8er]

samba is very easy. what are u having problems with?

[ricc]

You know wut, I'm a newbie to Linux.. a very new fella... tats why I dunno how to set it..
I'm able to see the Linux server from my Windows workstation, but unable to access to the server. I did add myself as a user in the Linuz server and I did login using the same username into the Windows workstation.

Can anyone suggest me the solution?