On Sunday 02 January 2005 09:51 pm, elefino wrote:
To share files, directories and devices (CD, DVD, etc.) on both Linux machines (i.e., in two directions), I need to run SAMBA server on both machines, and SAMBA client on both machines as well, is that right?
Yes. A servert can offer stuff for sharing. A client can get a share.
When I configure in YaST, I need to declare the workgroup (default is "TUX-NET"). Should SAMBA server on the second machine be assigned the same workgroup? Or is that a conflict? Should one be serving to (say) TUX-NET1 and the other to TUX-NET2? I'll use an actual name of my own choosing, but should it be one workgroup name for both servers, or a different workgroup for each?
Same name for both. It's kind of like saying "We all belong to the same family". I put all my machines into the same workgroup, Windows, amba severs, and samba clients.
Also, on a newly installed SuSE 9.2 system, is there any reason why YaST should not be completely sufficient to get SAMBA working? That is, is there any possible setup parameter for SAMBA that would need me to edit the files directly? I haven't even considered printing yet; just file/directory shares, so this config must be about as simple as it gets for SAMBA, right?
My samba needs right now are pretty simple and yast has done the job. In the past I have used webmin and back when I used RH 6.x, I used swat. As far as printing, it's pretty easy. If you want to use a printer on a windows box, you can set it up in yast. If you want to off a printer from a linux box and you use cups, I think suse (or maybe samba in general) defaults to offering all cups printers. I am far from an expert in samba, so I can't offer a lot of help, but reading and trying can usually get you a solution. Good luck! Doug