-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Partyka wrote:
Hmm, I have never heard of that can you tell me more
about how, or provide a link that would explain?
I do use the username map (root DOMAIN/administrator).
Is that the common?
User rights where introduced in 3.0.11 and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Beschorner Daniel wrote:
We have a lot of
[2006/01/04 18:44:40, 0] smbd/open.c:open_file_ntcreate(1355)
Trying to delay for oplocks twice
What Samba version? If it's 3.0.21, please test 3.0.21a
cheers, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Beschorner Daniel wrote:
Sorry, the second problem just seems to be related to an offline printer:
#0 0x2b3e76d4 in waitpid () from /lib64/tls/libc.so.6
#1 0x005963c0 in smbrun ()
#2 0x0058a8e1 in print_run_command
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabio wrote:
Hi!
Today I installed samba 3.0.21 on debian sarge. I see this error in syslog:
Jan 4 18:07:27 2T-Samba smbd[8352]: [2006/01/04 18:07:27, 1]
libads/ldap.c:ads_connect(292)
Jan 4 18:07:27 2T-Samba smbd[8352]: Failed to get ldap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Montenegro, Michael H (Michael) wrote:
I have created a mapusers.bash script (listed below) for
mapping Active Directory handles to unix logins. This
script is currently working as documented. I would like
some insight into how and when this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Albe wrote:
Well, when i first installed samba without POSIX ACLs,
it simply showed the classical rwx permissions of the
owner, group and others as the corresponding permissions
in the allow column of the security panel.
I would suggest to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Partyka wrote:
Here is are the permissions mapped to administrator:
[EMAIL PROTECTED] ~]# net rpc rights list -Uadministrator%password
SeMachineAccountPrivilege Add machines to domain
SePrintOperatorPrivilege Manage printers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Effenberger wrote:
thanks a lot for taking this over!
We have a [EMAIL PROTECTED] alias (but no real
mailing list). Messages sent there get to a group of
persons who want to contribute to the development of
the SQL module.
Jerry,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip Jirsák wrote:
OK, bugzilla is probably the best place for discussion
about several pdb*sql modules problems - it is public, so
everyone can find if someone else works on some problem
or tested it and so on.
Bugzilla is good for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Partyka wrote:
[EMAIL PROTECTED] ~]# net rpc rights grant MRPARTYKA/Administrator
SeMachineAccountPrivilege -Uadministrator%password
Failed to grant privileges for MRPARTYKA/administrator
(NT_STATUS_NO_SUCH_PRIVILEGE)
Did you add 'enable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Francis Strickland wrote:
Hi,
Our smb.conf specifies share level logging with:
log file = /var/log/samba/%S.log
This results in a log file named %S.log. I would expect something like
sharename.log. Can anyone explain this? I have not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Farkas Levente wrote:
why don't accept the template primary group (the same error is in
{smbd,nmbd}.log)?
This was part of the 'winbind enable local accounts' which has
long been removed.
and the passdb expand explicit is NOT set in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Farkas Levente wrote:
hi,
we try to configure samba 3.0.21a _without_ printing service, but it
seems samba still try to connect to the print server.
load printers = No
disable spoolss = Yes
show add printer wizard = No
from the logs:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
zorg wrote:
for example
pdbedit -a -m -u zigo
give me this error
cn=zigo$,ou=Systems,dc=domain,dc=int with: Object class violation object
class 'sambaSamAccount' requires attribute 'sambaSID'
in the ldap log i can see that the attribute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Farkas Levente wrote:
imho it'd be nice if load printers = No and disable spoolss = Yes
automaticaly set this option.
'load printers = no' with no printable service I could see, but
disable spoolss really implies no RPC printing and does not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Farkas Levente wrote:
This was part of the 'winbind enable local accounts'
which has long been removed.
but nowhere documented what's more it's included in
the changelog and the how to upgrade docs. and was it
replaced with something or ...?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christopher Peter Welsh wrote:
It seems to be happening with other net command variations (ie.
net group, net user). Net time works ok.
Looks like a either a problem with the LDAP libs or how we are calling
them on 64-bit platforms. Could you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerard wrote:
I am attempting to save files from MS Word into a directory located on a
FreeBSD 5.4 machine running Samba. For some reason, the files are always
saved with permission 766 rather than 666, which is what I want them
saved as.
set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Taylor wrote:
I have Samba as a PDC w/ openLDAP backend. Everything works great. I
have a question on how sub-groups work. For instance, my Domain
Users group will have a SID of
S-1-5-21-2213288279-2770996180-1086272762-513
What if I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
King, Rogie wrote:
Hi there,
Simple question. I currently have security = server mode
working for my samba installation on a freebsd unix box where
I work. I am wondering if I can use a dual mode
of security. For example, I want to be able
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Venu Siddamshetty wrote:
Hi,
We are facing problems while configuring SAMBA ADS on Sun Solaris
system. After installation and configuration we found that there is no
ADS support on the version samba-3.0.21a-1-noads-sunos5.9-sparc.pkg.gz.
Do you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Beast wrote:
When setting printing=bsd on my samba, client wont
able to resolve the server.
In windows client, it says The specified network name is no longer
available.
Using smbclient:
[samba]# smbclient -L svr4 -Uuser
Password:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam D. Morley wrote:
I would be surprised to see it, for a number of reasons:
- Solaris doesn't have MIT/Heimdal Kerberos. It has SEAM, aka Sun
Kerberos. I don't know if this matters, but ...
- Solaris doesn't have OpenLDAP. It has Sun LDAP.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam D. Morley wrote:
Wow. Does this mean a new version would be released
whenever there is a vulnerability in the kerb libs,
openldap libs, or Samba? Or only for Samba?
If I can ever get the time to get things in place, the build
is scripted.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
scot eckel wrote:
Hi all,
I came into a problem with the following situation.
One Windows 2k3 server which joined into a AD, and when I
tried to copy some files the owner ship of which contails
both domain user/group sid and local user/group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
scot eckel wrote:
Thanks for your reply. Yes, 'force unknow acl user' option
helps to bypass the unknown acl info when we need to
copy acl with files. But it just simply dropped the
unknown acl user/group. So is there any workround
available?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Collen Blijenberg wrote:
Ok found the problem,
Seems that the Mysql_passwd backend is still not working.! (did worked
in prev. versions!!)
the thing that went wrong is that, pdb_sql wrote a machine name in ALL
the fields of nt_fullname. (and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles McLaughlin wrote:
I have the same problem and would really like to here from
anyone with a fix.
There were some fixes post 3.0.9. Do you still have this bug in
3.0.20 or later? Works fine for me.
cheers, jerry
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Campbell wrote:
When trying to use the smbclient with kerberos the smbclient asks for
cifs/[EMAIL PROTECTED] when it should be asking for
cifs/[EMAIL PROTECTED] Is there a way I can fix that?
Mark,
Is the true realm name really lower cased?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
taso wrote:
What Samba files (other than smb.conf) do I need to edit/delete to
remove all
trace of a printer? I'm trying to get a handle on why smbd (3.0.21a) is
SIGSEGV-ing
and I want to start with a clean sheet.
remove all driver files in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Norris, Brent wrote:
The first problem is the really major one: I have two Fedora Core 4
machines with all updates connected to the Windows AD. They seem to be
working fine when people try to get access to the shares that they have. I
was told
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Davidson wrote:
I am running Samba on a FC2 X86_64 machine and I have one directory that
needs to be accessible by two different groups (each group has its own
folder) of people.
My recommendation is to use posix acls.
cheers. jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomasz Chmielewski wrote:
What is the easiest way to allow normal users to install
printers (which are available through a Samba server)?
There's an XP policy that will allow Users to connect
to printers and have the driver installed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luu Minh Khoa wrote:
Hi !!
I have an error in functions file. When I start SAMBA, it showed an
error below
Starting SMB services: /etc/init.d/functions: line 83: 3379
Aborted $nice $*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Davidson wrote:
I would really like to avoid jumping to acls right
now. Is there not another way?
They are *reallY* useful though. And designed for
this exact problem :-)
You could of course, have two shares pointing at the
same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Miki Monguilod wrote:
Hi!
Yesterday we finally get the stack trace of Samba. Here you have:
Program received signal SIGSEGV, Segmentation fault.
0xfefd4f6c in _free_unlocked () from /lib//libc.so.1
(gdb) bt
#0 0xfefd4f6c in _free_unlocked ()
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Samba User wrote:
Does anyone know when the brocken helpfiles are going to be fixed?
Or maybe where I can copy them to make them work?
I am running 3.0.21a and the Changelog states that it should be fixed,
however I don't see it that way...
What
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Remy Zandwijk wrote:
Before upgrading to Samba 3.0.21a, we were running Samba
3.0.14a. On the Domain Member Server, when selecting
the security-tab of a file or folder, the users were
listed as users of the domain. Settings ACL's worked
very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Olaf Jörk wrote:
rpcclient $ enumprinters
:
flags:[0x80]
name:[\\pslag\kyo_adv]
description:[\\pslag\kyo_adv,Kyocera Mita FS-3820N
KX,Kyocera-Testdrucker]
comment:[Kyocera-Testdrucker]
:
So I think, the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jürgen Hoffmann wrote:
1. Although Printing a Test Page with Cups prints from
the right Paper Feed, printing a Test Page from the Windows
Client prints it from the default feeder.
My suggestion is not to mix cups and Windows drivers on
the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomasz Chmielewski wrote:
There's an XP policy that will allow Users to connect
to printers and have the driver installed automatically.
Run gpedit.msc on an XP client and you'll see what I mean.
It's not very handy to do so with Samba and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joris De Pooter wrote:
Jan 12 10:11:37 bernie smbd[28408]: Unable to cancel job 47201 -
client-error-not-authorized
I'll try to update my samba 3.0.14a-r2 to a newer release...
Samba does use a username/password to access the cups
server.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Nielsen wrote:
Adam:
What version of Samba are you running?
I'm running 3.0.21rc2 - so from what Jerry was saying,
it looks like you may need to upgrade for this to work.
It was a long time ago that the fixes were checked in.
Maybe even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Zielinski wrote:
1st, the add_printer_hook is called by a update_printer function.
This function is called really frequently.
Using an add printer command and not commenting this line out of the
samba code slowed down everything in a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Geoffrey Scott wrote:
Hi all.
I was wondering if anyone had a successful exampel of using the add
printer command with cups so that the windows print migrator could be
utilised. Seeing as Jerry as spent time on this it would be a shame not to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Geoffrey Scott wrote:
I was wondering if anyone had a successful example of using
the add printer command with cups so that the windows
print migrator could be utilized. Seeing as Jerry as spent
time on this it would be a shame not to know how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Fladischer wrote:
hi!
can someone tell me the latest samba release with
a functional net rpc vampire tool?i tested it with
the newest samba release 3.0.21a and there it wouldn't work!
There's a patch in bugzilla to fix this for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Remy Zandwijk wrote:
I found out that I need to use 'fake' 'idmap uid' and 'idmap
gid' to get it to work. Is that a winbind bug? In
Should be fine without either an idmap uid/gid range. Are
you saying that winbindd will not start without these?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Grabner wrote:
Hi,
some times users have problems to access shares. Some time later it
works.
I see smbd childs panic. Version 3.0.20b or 3.0.21a on Debian sarge +
Openldap 2.3.13.
This is either a bug in nss_ldap or the OpenLDAP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gururajan Ramachandran wrote:
Fetching DOMAIN database
Failed to fetch domain database: NT_STATUS_NOT_SUPPORTED
Perhaps DOMAINNAME is a Windows 2000 native mode domain?
Are you trying to join as a BDC?
As you can see, it joined domain fine.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomasz Chmielewski wrote:
It won't work - there is no such setting (to allow printer
installation), even when I load the XP adm files.
(Or I'm looking in a wrong place).
You have to write your own adm file. You can set any registry
setting via
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Campbell wrote:
Yup. it is xxx.psu.edu. It works shen accessing a windows domain
becaue the domain is XXX.PSU.EDU but our MIT K5 realm is xxx.psu.edu.
What calling arguments are you using with smbclient?
And what are the krb5 related options
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Geoffrey Scott wrote:
Um, I really do appreciate the background info and
pointers. but i was hoping you might be kind enough to post
your add printer script so that i can get up and running
quickly. Please please, please, please... It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomasz Chmielewski wrote:
You have to write your own adm file. You can set any registry
setting via an NT4 policy file.
The problem is, I don't really know which registry setting
I have to set to allow users to set up printers.
Hence my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian wrote:
After upgrading Samba from 2.2.8a to 3.0.10, we find that users
whose Unix login does not match their NT login need to have their
users.map entry changed to include their NT domain name.
e.g.:
grybo = grybowski
had to be changed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Geoffrey Scott wrote:
On my ADS member server it doesn't show any members of GUESTSHIRE\domain
users:x:5513: using getent group
Is this normal behavior? If not any ideas how do I fix it?
Windows won't return that group without using ranged
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 12 Jan 2006, Ben wrote:
I have a samba server using ldap for authentication. All the client
machines are Win XP Pro machines. I am not using domain logons
(although, I tested them and samba is set up for them), but
security=user. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pablo Milano wrote:
As far as I saw, since some microsoft patch for AD, winbind client from
samba 3.0.14 (and prior versions) does not work properly for getting users
and groups from Active Directory. This problem was solved in 3.0.20. I saw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
simo wrote:
On Fri, 2006-01-13 at 09:28 +0100, Andreas Fladischer wrote:
hi!
i have a question about net rpc and the rights!
is it possible to grant rights to a group and not only to users?
i use samba 3.0.20a with ldap!
Yes, it should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Zielinski wrote
:
I just tried out to add a port on two MS systems and it *looks* like it
could work with SPOOLSS calls. Unfortunatly some of the packets are not
decoded by Ethereal.
Looks like this:
-- EnumMonitors
-- Response: ...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Franz Strebel wrote:
I ran into some problems last night upgrading from 3.0.20b
to 3.0.21a. I did my usual build from source, but when I
ran it, winbindd would die on me.
So I invoked it with -d10 -F and watched the progress on the
console.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesse Spangenberger wrote:
Actually, this is not a bug but a security measure I do believe. Win2k and
WinXP will not connect to the same server multiple time using different user
logon information (actually, sorta pointless if you set up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Allison wrote:
Yes, we'll look at this. Can't tell you when we'll have it fixed though -
but ensuring MS server apps work against a Samba PDC is a particular
hobby-horse of mine.
Thanks for the trace, that should help.
Alexander Bokovoy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alex Moen wrote:
===
[2006/01/16 09:32:12, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 10 in pid 12203 (3.0.21a)
Please read the Trouble-Shooting section of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
taso wrote:
How many winbindd processes should be running?
3.0.20 you should see 2 normally.
- 3.0.20 you should see one for each trusted domain + 1 for the joined
domain (+- one for idmap IIRC).
cheers, jerry
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan Johnson wrote:
I was wondering if there are any plans for future Samba
workshops?
We try to maintain a calendar of developer appearances at
http://news.samba.org.
cheers, jerry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Antonius Aji wrote:
You're right ... it is becoming common problem in 3.0.21a
In one of the message: it says that there is a patch to solve this
problem in bugzilla repository. I am still searching that patch in
bugzilla. If it is not found, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Danilo Moretto wrote:
Greetings,
I have this problem, i cant print from 2 w xp client over the
net in the samba server, Version 3.0.14a-Debian, cupsys 1.1.20final+rc.
working as pdc role. this is the log.smbd:
[2006/01/16 12:02:20,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Matthews wrote:
hi there,
i'm trying to configure samba so that of my winbind users are
added to the same group. can someone tell me how to do that?
You'll need to hack nss_winbind.so for this. That's the way
people have done it in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Nielsen wrote:
- why get I a strange display on security option ?
Samba has always behaved like this for me, but I'm not exactly sure
why. If you scroll down you'll notice that 'Special Permissions' is
ticked, which is Windows' way of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Gordon wrote:
Using telnet/rsh/ssh is not an option for us. We need
to understand why the rpc protocol with NetApp does not
work, and if possible, try to fix it.
I think Derrell fixed this in the latest SAMBA_3_0 libsmbclient
code. So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 18 Jan 2006, Peter Gordon wrote:
I have just downloaded the latest version of Samba:
svn co svn://svnanon.samba.org/samba/branches/SAMBA_3_0 samba-3_0
and have built, compiled and installed it.
I installed it in /sw/SAMBA_3_0
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mikael M. Hansen wrote:
i
I have a problem with a samba-3.0.21a (as a PDC), when I use rpcclient
to set the driver for a printer. I receive the following error (log
level 12 for relevant parts rpc*, printerdrivers,tdb attached):
rpc_api_pipe:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cron, Charles wrote:
When I try to join the Samba servers to the new upgraded AD mixed mode
domain (net ads join -U Administrator),
machines on the WAN fail with the error:
ads_connect: ASN.1 encoding ended unexpectedly
That error message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cron, Charles wrote:
I realize that, its just that all is ok in the datacenter,
all is ok with the old domain, and so many other packages
depend on the installed version of krb5, dont know how I would
manage the upgrade without replacing all the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Nielsen wrote:
So the these ACEs show in the initial page of the security tab
FARSCAPE\jerry (Full Control)
FARSCAPE\users (ReadExec)
Everyone (ReadExec)
They do? If this was appearing on my set up, on the initial page of
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Zagerholm wrote:
Hi list,
I think my question is better suited to this list than the normal.
I wonder if it is possible to disable connection caching?
I've noticed that a successful connection is cached until the process
(pid) is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Nielsen wrote:
password server = vmdc1.domain.local
AFAIK this option is only required for security = DOMAIN - if you're
using security = ADS then when you join the domain Samba/winbind will
find out which server to use for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joost Runsink wrote:
Hi all,
Today our domain went down. When looking in the log it appears that a
windowsXPpro machine won the election. The domain controller has an
OSlevel of 65 (3.0.14a).
Restarting the smb process (/etc/init.d) resolved
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jason bigler wrote:
with the winbind NSS support = sfu does this use the
UID and GID within ADS for Samba authentication or
does it remap the UID and GID locally?
'idmap backend = ad' uses the uid and gid information
from active directory. The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Gerfen wrote:
Ok, well what version of samba impliments the winbind nss support?
I don't remember exactly. Check the release notes but it
was 3.0.20 IIRC.
cheers, jerry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jamie Crawford wrote:
These are already open. I'm pretty sure that NT4/2003 PDC's make a
DCE/RPC over TCP connection to pull down the 1b entries from the wins
server. I have done packet captures on test NT4 wins server to see how
PDC's pull
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Gerfen wrote:
Hmm, I am running Samba 3.0.20a-3.1.2-SUSE and when I run a testparm I
am getting this:
Load smb config files from /etc/samba/smb.conf
Unknown parameter encountered: winbind nss support
Ignoring unknown parameter winbind nss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
YW Law wrote:
| Hi Robert, thanks for your reply, but this SMBDownloader is a Windows
| executable using presumably Windows API. Does Samba (on non-Windows of
| course) offer equivalent functionality?
smbget will resume IIRC. It's not built by default
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Esh, Andrew wrote:
| Getting timeouts trying to go to: http://websvn.samba.org/
|
I didn't get any timeouts but did have a problem with the
berkeley db backend. Could have been related. Fixed now.
Thanks for the heads up.
cheers, jerry
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Notice to all bugzilla.samba.org users:
There was a small hickup in the bugzilla server that resulted
in some data loss. If you added information to an existing
bug report or filed a new report between 8am (GMT-8) on June
24 and 7am (GMT-8), June 25,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
|
|
|
| Our Samba print server seems to slowly degrade, and
| get more and more errors over time, until it starts
| recieving tdb fetch failed messages, fatal errors,
| and getting INTERNAL PANIC's and dumping core etc
...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 18 Jun 2004 [EMAIL PROTECTED] wrote:
Excuse my ignorance please, and the simple nature of this
questions...but would someone explain to me the difference between the
create mode and force create mode parameters in the smb.conf file?
When
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 22 Jun 2004, Richard Bonomo wrote:
If you configure with the --enable-cups option, but do not have the
cups-devel package installed (in addition to simply cups), the binaries
eventually produced simply will not work with CUPS, but the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 25 Jun 2004, Chris Hobbs wrote:
Chris Hobbs wrote:
Should I submit this to bugzilla? I'd hate to do that until I've
exhausted my options on the mailing list.
Well this turned out to be an empty threat -- turns out the general
public
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 23 Jun 2004, Jason Joines wrote:
I've been using Samba 2.x authenticating UNIX and Samba users to
OpenLDAP 2.0.x fro quite some time. Now I need to upgrade OpenLDAP to
2.2.x and Samba to 3.0.x. Although I've been using OpenLDAP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Bartlett wrote:
| If that's what caused the issue, then there is a bug
| (which I'm happy to look into and fix).
| The intention of the logic was that if the value was
| undefined in LDAP, the flags would be set to PDB_DEFAULT and it
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| Hi Jerry et al,
|
| the parsing of the 'username map' file seems to be
| broken in 3.0.5pre1 and a few earlier releases. The '!'
| at the beginning of a line is ignored. Something like
|
| !lp = lp
| !chbeyer = chbeyer
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
andreas oster wrote:
| I am using Version 3.0.2a of samba on Linux 2.4.18 (suse with
| self-compiled samba from tarball)
...
| Invalid handle (OTHER:25527:25530)
|
|
| just reread your posting, maybe this is a completely
| different problem you have,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Enrico Scholz wrote:
| Hello,
|
| I am using LDAP as passdb and idmap backends with Samba
| 3.0.3, and have a problem with the configuration of 'ldap admin
| dn'. Currently, I have to set the password for this DN
| with 'smbpasswd -w' (which works) and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Bonomo wrote:
| If you configure with the --enable-cups option,
| but do not have the cups-devel package installed
| (in addition to simply cups), the binaries
| eventually produced simply will not work with
| CUPS, but the configure and make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Could you both (and anyone else having 'username map'
problems in 3.0.4 or later) try this patch which hopefully
fixes the username map bug.
Thanks. Let me know how it goes.
cheers, jerry
| the parsing of the 'username map' file seems to be
| broken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 6 Jul 2004, Arno Seidel wrote:
my wish for 4.0 is a deeper integration of ldap. maybe in that way, that
share configurations could be stored direct in a ldap-entry.
This is slated for 3.2
cheers, jerry
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 6 Jul 2004, Hamish wrote:
Hello all
Is there a way to make printers show up on a samba server for windows
clients without restarting smbd and nmbd?
The 'printcap cache time' option will be in 3.0.5 to handle this.
cheers, jerry
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arno Seidel wrote:
| Hi,
|
| and where can i find some rudimentary documentation for it??
There is none currently nor would I recommend getting used
its current implmentation as i can pretty much guarantee that
it will change before release.
cheers,
1101 - 1200 of 4276 matches
Mail list logo
