-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm currently in the process of recovering a system and wanted to mention my
thoughts and process for feedback and, if necessary, corrections:
1) I had my original version of samba (2.2.8) compiled with:
./configure --with-fhs --prefix=/usr
I have a single group of users, some of whom can successfully add my samba
printer and some of whom can't. There should be no difference as they are
all part of the same group. The error message is as follows:
A policy is in effect on your computer which prevents you from connecting to
this
After reading through the documentation, I realized that as a part of the
migration process from Samba-2.2.X to Samba-3.0.0 I needed to convert
everyone in my smbadmin group (previously domain admin group = @smbadmin) to
the Domain Admins group w/rid=512. So, I issued the following command:
On Wednesday 15 October 2003 01:29 pm, you wrote:
On Wednesday 15 October 2003 16:20, Kaleb Pederson wrote:
What am I doing wrong? How come I'm an administrator without any
administrator permissions?
I think I had to restart Samba after doing this to make it effective.
Thanks Chris
I was previously using 2.2.8 and had 'domain admin group = @smbadmin' set
making anybody in the smbadmin group an administrator. However, with
samba-3.0 that went away. So, I set 'admin users = @smbadmin name1 name2...'
but it doesn't give my users administrative privilege. The logs seem to
I was wondering if there was a %{char} that would give me the windows
version or something equivalent so that Windows XP specific stuff
doesn't get stuck with Windows 2000 stuff.
Thanks for the help.
--Kaleb
PS: Please CC me as I'm not on the list.
--
To unsubscribe from this list go to the
Kyle Loree wrote:
use the %a tag for that.
Hmm... I looked through the docs and saw that but wasn't and still am
not sure that is what I want. It looks like it will probably work, but
what happens with the next version of Windows? I presume it also shows
up as unknown, at least for a period of
Yes, that's definitely coming from a different subnet.
iptables handles it just fine if configured well. I use something like:
-A INPUT # if coming from local subnet # -j localnet
-A INPUT # if coming from external source # -j badnet
-A badnet -p tcp -m tcp --dport 22 -j ACCEPT
-A badnet -j
I use Outlook/Outlook Express without problems under Windows 2000. I
didn't have to do any special configuration. Sounds like an XP feature?
--Kaleb
-Original Message-
From: [EMAIL PROTECTED] [mailto:samba-admin;lists.samba.org]
On Behalf Of Dimitrios Stergiou
Sent: Wednesday, October
On Wednesday 30 October 2002 12:53 pm, Andrew Bartlett wrote:
Kaleb Pederson wrote:
snip
And tcp 445, the new port that Win2k (and hence Samba 3.0) now uses.
(Netbiosless SMB/CIFS)
Andrew Bartlett
Doesn't it drop back to 139 (or one of the other ports) if it can't make a
connection
[usernamelocalhost source]# ./configure --with-fhs --prefix=/usr
--sysconfdir=/etc --with-privatedir=/etc/samba
--with-lockdir=/var/state/samba --localstatedir=/var --with-netatalk
--with-smbmount --with-pam --with-syslog --with-sambabook --with-utmp
--with-acl-support ~/myconfig.out 21
On Tue, 22 Oct 2002, Kaleb Pederson wrote:
RE: XFS and problems with -lattr and -lacl
snip
I don;t use XFS so take this with a grain of salt, but IIRC this is an
XFS
issue that was fixed in later XFS releases.
I'll grab the latest versions and see if it is still an issue. If so,
I'll post
I attribute this to a Windows 2000 bug. I have 30+ machines here, almost all
of which are windows 2000. Anytime they are trying to connect to a machine
as a different username, the password/username being used for the share do
not get correctly saved.
I have not, however, tried connecting
Actually, that opens up more than is needed:
tcp port 139 (could be 445 instead of you set samba to that)
udp port 137
udp port 138
--Kaleb
On Thursday 10 October 2002 06:35 am, you wrote:
On Thu, Oct 10, 2002 at 02:11:44PM +0200, Alexander Saers wrote:
Hello
Can anybody tell me what
PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Rongyao
Sent: Friday, June 14, 2002 9:36 AM
To: Kaleb Pederson; 'Mark Brosius'
Cc: [EMAIL PROTECTED]
Subject: RE: [Samba] ipchains question
Check www.samba.org under documentation for more
information on network neighbourhood. It explain port
137
I
would check out the following:
passwd chat = *New*UNIX*password* %n\n
*ReType*new*UNIX*password* %n\n
*passwd:*all*authentication*tokens*updated*successfully*
type
passwd as if you were to change your unix password manually, now make sure
theabove text matches up.
You
might find that
Under Linux, however, you can use the smbmount to do just what you want.
Once mounted, then you can treat it just like any other
directory/filesystem. I know it smbmount doesn't work under Mac OS X
and believe smbmount only supports Linux, but I'm not positive on that
point.
--Kaleb
I have one machine setup as a Samba PDC and a second samba machine that
I would like to be able to have authenticate through the first so that,
hopefully, I don't have to do any synching of passwd files. By what I
have read, it doesn't look like this is possible directly with samba?
To further
18 matches
Mail list logo