Check the posix permissions in the shares are set to allow the group nobody
(or whichever you are mapping as guest) to r/w.
Check the logs at level 3, am willing to bet there is a Chdir/Permission Denied
error somewhere...
Carlos
-Original Message-
From: [EMAIL PROTECTED] on behalf
Do a getent passwd. Do you get a list of the local *and* domain users?
Carlos
-Original Message-
From: [EMAIL PROTECTED] on behalf of Jason Greene
Sent: Wed 9/19/2007 9:03 AM
To: samba@lists.samba.org
Subject: [Samba] wbinfo
Hi,
I am trying to configure a RHEL-4 server with SAMBA.
Please check:
1 - that your nsswitch.conf file is correctly configured.
2 - use klist to verify the tokens are A ok, if not kinit to refresh.
3 - verify that the server joined the domain as a regular mcomputer and
not a DC.
4 - check that the DNS related things are all correct: windows DNS,
We had a Samba Version 3.0.23c-4 workgroup server on clarkconnect 4.1
(had to hunt for kbr5-workstation!) with a smbpasswd back-end that was
accessed from machines joined into an Active Directory Windows 2000
domain.
We switched the Samba server to be a domain member. We have done this
before so
-Original Message-
From: Ken Smith
Is there some obvious config setting that I have missed?
Hard to tell if you don't provide smb.conf
Carlos
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
I get similar errors when I have dummy shares (ie shares in smb.conf that point
to non-existent directories), check that too.
However if using as PDC, the most common situation is when the samba server is
not in the DNS/WINS for given machine.
If it is standalone, then make sure there is no
Translation: If you need help, sweat a little, and show us why we should.
Otherwise, RTFM.
Carlos
From: Felipe Augusto van de Wiel
This is not exactly a RTFM, but you will need to give
us more information if you really want help, smb.conf, logs
I assume the remote VPNs are full tunnels, and that you can ping any of the
computers in any of the networks from any of the networks.
You should create trust relationships among all of the domains, along with
permissions that allow logons and file access cross-domain - an important
omission
As a suggestion, do not publish your SIDs on the web. If any of us
wanted to, we would be able to hack into your network quite easily.
Carlos
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Gaiseric Vandal
Sent: Monday, May 21, 2007 1:59 PM
To:
I wonder, however, why port a networking system so completely tied-in to POSIX,
like SMB, to a non-POSIX OS? What is the need?
The experience (particularly with Samba3) has been that it is easier to
add a POSIX layer to the OS than to keep 'fixing' samba.
Yes. That also has the added advantage
Not built in.
As mentioned, this is impossible to do in Windows itself (unless you do
some pretty complicated Group Policy stuff in AD).
Carlos
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
xrado
Sent: Wednesday, April 18, 2007 11:52 AM
To:
drwxrws---+ 2 ralfgro ve6 2007-04-18 17:28 testdir
2770 [drwxrws--] permissions will force inherit at the file level
system, ignoring Samba. Set the directory to 0770 permissions, and new
items would be created with 660 as per smb.conf
Other thing is to insure that the main group for the
Smb.conf share settings?
carlos
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Travis Bullock
Sent: Wednesday, April 18, 2007 4:09 PM
To: samba
Subject: Re: [Samba] SAMBA Problem - Users take ownership
Can anyone help me with this? This is a serious
PROTECTED]
Sent: Wednesday, April 18, 2007 4:19 PM
To: Carlos Rivera-Jones
Cc: samba
Subject: Re: [Samba] SAMBA Problem - Users take ownership
smb.conf file:
[global]
security = domain
workgroup = AVMAX
netbios name = atlas
map to guest = Bad User
encrypt
14 matches
Mail list logo
