Dear Brian and all
Thankyou for your fast enlightment
Brian H. Nelson wrote:
Bino Oetomo wrote:
And ... voila ... the user can access (read-write) into the shares ...
But it'll means that the user can also "execute" somethings inside
directory ... right ?
Why we need the "execute" bit in di
Bino Oetomo wrote:
And ... voila ... the user can access (read-write) into the shares ...
But it'll means that the user can also "execute" somethings inside
directory ... right ?
Why we need the "execute" bit in directory permission just to let the
user to "read and write only" ?
That is
Dear Serg and All
Сергей wrote:
Hello, Bino!
I use webmin to do the samba PDC configuration
IMHO, insuffisient
Agree ...
I did some direct edit to conf file
[warehouse]
comment = Files of warehouse
writeable = yes
path = /hdd2/samba/groupfiles/warehouse
w
On Tue, Jan 5, 2010 at 08:04, Gaiseric Vandal wrote:
> It didn't work for me on Sun with Samba 3.0.37 either. I was under the
> impression (quite possibly wrong) that for Win 7 support you would need
> Samba 3.3.x or 3.4.x anyway. I have been testing the sunfreeware.com
> version of samba 3
Greetings,
I have been attempting an existing Samba domain member server that is
running Samba 3.2.15 to 3.3.9 (or 3.4.3) but in either case my AD users
end up being unknown to the server.
I am using the idmap rid on the member server - no changes allowed to AD
server, AD server not managed
You may also want to look into setting up avahi to advertise your CUPS printer.
Avahi is the Linux implementation of the Bonjour advertising protocol; Bonjour
is for Apple what UPnP is for Windows.
> -Original Message-
> From: samba-boun...@lists.samba.org [mailto:samba-
> boun...@lists.
>From everything I've read and experienced, version 3.3.4 was the earliest
Samba version that was demonstrated to be able to support Windows 7 (with
the proper registry entries).
Blessings,
David
On Jan 5, 2010 10:04 AM, "Gaiseric Vandal"
wrote:
It didn't work for me on Sun with Samba 3.0.37 e
It didn't work for me on Sun with Samba 3.0.37 either.I was under
the impression (quite possibly wrong) that for Win 7 support you would
need Samba 3.3.x or 3.4.x anyway.I have been testing the
sunfreeware.com version of samba 3.4.x (full zfs support seems to be
missing) and compiling
On Tue, Jan 05, 2010 at 01:38:18PM +0100, Christophe Baegert wrote:
> IPP never worked on my Macbook using OS X 10.4, which works well with Samba.
Odd, given I remember Mac OS X 10.1 automatically detecting the IPP
broadcasts by cups (which cups was set to share printers with the network,
which it
When the Samba4 for gets released this year, how is DNS to be setup, is
there any special requirements, will samba setup dns for you when using
active directory?
How does that whole part work? I have seen that kerberos will be built
in.
Also I have to say, I saw the Samba Team Blog 3 and I re
Hello.
I have set up a shared samba server for two organisations.
Using hosts allow I can permit access to a share from a certain IP network,
however, the share is browseable still for everybody. How can I prevent
that, is that possible?
Regards,
Patrik Hall
--
To unsubscribe from this list go
Hi,
Le 05/01/2010 13:03, Jean-Jacques Moulis a écrit :
In your case I wouldn't use smb for printing.
both OSX and windows (at least recent ones) can print directly to a CUPS
server.
IPP never worked on my Macbook using OS X 10.4, which works well with Samba.
But I didn't try it on the Windows
Daniel Müller schrieb:
> Hello,
> with pdbedit -L on my MemberServer (Samba) I could not list the domain
> users and groups!
> With pdbedit -L it is only working on my PDC(Samba)
I assume then this is - at least at the moment - "normal" behaviour of
pdbedit. Perhaps someone else on this list can te
On Tue, 05 Jan 2010 12:03:38 +0100 Christophe Baegert
wrote:
CB> Hi,
CB> On a linux server with CUPS, I installed Samba to share it with windows
CB> computers.
CB> I managed to share it with my Macbook on MacOS 10.4, with this address : |
CB> smb://login:passw...@name _of_server/name_of_printer
Hi,
On a linux server with CUPS, I installed Samba to share it with windows
computers.
I managed to share it with my Macbook on MacOS 10.4, with this address : |
smb://login:passw...@name _of_server/name_of_printer|
So I think my server is well configured.
BUT I don't even see my network on
Get following errors compiling samba4 master-branch in vmware
virtualmachine :
---
/usr/bin/ld: i386:x86-64 architecture of input file
`../client/umount.cifs.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `../client/mtab.o' is
incompatible with i386
16 matches
Mail list logo
