>
> > did you delete and recreate the machine account so the new server can
> > use it for when it joins?
>
> [Robert Mortimer]
>
> I was expecting it to auto create an account for the new NETBIOS name.
> I can rejoin my old BDC no problem under the same name and t
> did you delete and recreate the machine account so the new server can
> use it for when it joins?
[Robert Mortimer]
I was expecting it to auto create an account for the new NETBIOS name.
I can rejoin my old BDC no problem under the same name and the add machine
Script over writes t
I am having difficulty joining my new samba server to my domain.
I am replacing an old member server. I am using the same config file with a
new netbios name
I try 'net rpc join -S my-pdc -W my-domain -U root' and get the following
utils/net_rpc_join.c:net_rpc_join_newstyle(304)
error setting tr
> Hello,
>
> I am pretty sure this is described somewhere in the official docs, but
> anyway:
> Your approach #1 should work well. The [homes] section is accessible by
> clients using *either*
> \\\ or
> \\\homes
>
> No modifications to your example necessary.
You can Map a drive letter to the ho
> Andrew,
>
> I have a software which need the following package but I can't
> find it in
> Internet. Could you advice me where I can download it?
>
> samba-3.0.10-1.4E6.HSM.2.i386
> samba-common-3.0.10-1.3E.6.HSM.2
> samba-client-3.0.10-1.4E.6.HSM.2
1: I am assuming that this is an RPM depende
> Hi Gary
>
> First of all the permissions assigned from windows are actually Access
> control lists which are not supported by default
>
Windows/SAMBA can map ACLs to fine-grain windows permissions but it always
reads the UNIX permissions as well. The UNIX permissions are where it
encodes the win
> Robert Mortimer пишет:
> > Check the UNIX user permissions. Samba stores the windows read only
> > attribute here.
> > If the owner does not have write access than samba assumes the
> read only bit
> > is set.
> >
> I have write permissions on fs ( i.e. l
I have two directories that look the same but when a user edits a document
belonging to another user in one of them it sets the read-only flag. In the
other it does not.
I have the following in the main part of my smb.conf and in the share
create mode = 660
force create mode = 660
directory mode
I have two directories that look the same but when a user edits a document
belonging to another user in one of them it sets the read-only flag. In the
other it does not.
I have the following in the main part of my smb.conf
create mode = 660
force create mode = 660
directory mode = 770
read only =
TECTED]
> [mailto:[EMAIL PROTECTED]
> ]On Behalf Of Robert Mortimer
> Sent: 27 June 2006 16:07
> To: samba@lists.samba.org
> Subject: [Samba] Samba and DOS databases (oplock settings not getting
> sameresults as under NT4)
>
>
> Before you reply note I have read the op-loc
Before you reply note I have read the op-locks bit of the samba manual
We have a micro-focus Cobol (dos) database that ran on an old Novell server.
When we moved to NT4 performance bombed. We added the correct registry keys
to turn off op-locks on the NT4 server and all was OK for the next 6 years
No config details
No hardware specs
No log output
No description of the operating environment
No definition of slow.
Humm let me think?
If you ring up the garage and tell them your car is slow would you expect
them to have an answer without looking at it or maybe asking some more
questions (model
> Hello!
>
> I want to connect computers with windows xp (pro/home) to a one computer
> linux (with samba). I want to every user who want to use his/her account
> data may use any of the computers in the office and have theys personal
> data (in any pleace in the office) (domain or something, i don
Most Distro's come with a SAMBA binary. Is suggest that you start with that.
There are clear minimum config suggestions in the documentation (your distro
often has a default config (see /etc/samba/smb.conf).
Mac OS X should be able to use NFS so should not need SAMBA as this is a
Unix2Unix setup
> Hi,
>
> I am running samba 2.2.12 on Freebsd 4.3, on an
> internal network, with no firewall. I have a very
> simple smb.conf. Here are the relevant entries:
>
> [global]
>workgroup = Workgroup
>socket options = TCP_NODELAY
>printing = bsd
>guest account = nobody
>hosts
In the old NT4 model I think it was up to the client to decide who to send
the authentication request to. I also seem to remember the BDC was
preferred over the PDC as it was assumed the BDC would have less load.
In short I think the clients get to choose based on what they can see in
the network
he router
>
> >>> "Robert Mortimer" <[EMAIL PROTECTED]>
> 11:03:45 pm 27/03/2006 >>>
> Name resolution for windows machines is by WINS or Broadcast. Broadcast is
> not going to like the firewall. Wins could be configured if you
> look up the
> p
Name resolution for windows machines is by WINS or Broadcast. Broadcast is
not going to like the firewall. Wins could be configured if you look up the
ports to allow and run the SAMBA wins server on the linux machine. My only
question is what do you not trust on your local network (why the firewall
A windows machine will try the current logged on user's credentials against
any share thrown at it (often with-out domain or workgroup checks). It can
do this because only one active logged on user is permitted at any one time
and the SMB protocol is it's native protocol. Linux can have multiple ac
> Hello,
>
> Is it possible to store samba passwords in ldap without configuring
> samba as a PDC? All the documents/references I've come across are
> related to using LDAP as a samba PDC backend, not as just a db file
> replacement.
>
> Thanks,
LDAP is a heavyweight store for massive amounts of
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> ]On Behalf Of Markus Korth
> Sent: 17 March 2006 08:28
> To: samba@lists.samba.org
> Subject: Re: [Samba] SAMBA+LDAP in a Workgroup
>
>
> HiHo Tom!
>
> Tom Haerens wrote:
> > Hi,
> >
> > This may be a dumb questi
I have added ACL support to the file system on my FC3 server
In windows the security dialogue shows correct permissions
When I open a file in word it opens read only even though as part of the ACL
extended group membership I have write permissions (Unix main group is read
only)
Using the security d
22 matches
Mail list logo
