search for: wepin

Hi all, I am very new to the wonderful world of Samba (I have to keep telling my assistant that its not a south american dance...) and require a little assistance. I have downloaded the latest version of Samba, together with all of the documentation. I have managed to sucessfully untar the files but I am having difficulty compiling the files. I am using SCO Unix and when I type in the

Hello, I've recently installed Samba on a S.u.S.E. computer, and I am wondering what the best way to edit and manipulate the smb.conf file is. could anybody help me out??

...r the best, you can remove all rules with: ipchains -F You will still be left with policies, which hopefully will be permissive. If not, study man ipchains. Joel On Fri, Jul 05, 2002 at 03:54:36PM -0600, Donald D. Henson wrote: > (Note the change of e-mail address. Please use <linuxtest@wepin.com>) > > I must admit that I'm getting a bit frustrated here. After finally > locating the DIAGNOSIS.txt file, I did as you suggested and started > running through the tests. Sure enough, Test # 2 failed and told me > there are two possibilities: 1) DNS or /etc/hosts file is...

(SuSE Pro 9.3, Samba 3.0.13-1.1) I have a Samba server set up on a Linux machine. I have four shares set up, not counting all those system things (homes, profiless, etc). When I access the shares from a Windows machine, the four shares show up like they're supposed to, in addition to the system things. However, when I access the shares from a Linux machine, two of the four shares do not

I'm a Samba newbie also so please bear with me. I installed Samba 2.x under SuSE 9.0. It worked well for my simple setup (home network with one Linux fileserver, one WindowsXP desktop, and one WindowsXP laptop all connected via a 10/100 ethernet). When I upgraded to SuSE 9.1, I was automatically upgraded to Samba 3.x. This still worked with my original settings but something would go

(SuSE Pro 9.3, Samba 3.0.13-1.1) (I posted this earlier but didn't get much response so I'm trying again with a different subject line.) I have a Samba server set up on a Linux machine. I have four shares set up, not counting all those system things (homes, profiles, etc). When I access the shares from a Windows machine, the four shares show up like they're supposed to, in

(SuSE Linux Pro 9.2, Samba 3.0.9) I have a simple network, 10/100 Ethernet, consisting of a Linux file server/workstation, a WindowsXP workstation, and a laptop dual-booted for Linux and WindowsXP. I have several Samba shares, defined using YaST, on the file server. The problem is: When I access the Samba shares using the laptop WindowsXP, all shares show up and I am able to access them in