-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 9 Jan 2004, Michael Keightley wrote:
It is fixed in 3.0.2pre1. Also changing to security = domain and
running net join in 3.0.1 fixed it. I've attached the log file anyway
for security = server with 3.0.1. Do you recommend using security
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 9 Jan 2004, Pence, Alan wrote:
Does anyone know how to check the samba setting of smb signing?
There is a data write error that can happen with the signing, and I'd
like to check my samba servers.
See the various signbing parameters in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 9 Jan 2004, Bret Jordan wrote:
The problem appears to be that pdbedit will allow you to set the RID at
account creation so long as it is a normal user account, if it is a
machine account it will not.
if you file a bug report we will work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 9 Jan 2004, Andrew Bartlett wrote:
hmmm...have you considered try security = domain ? it could also be an
issue in your configuration with SMB signing.
I broke that so many times over the course of my NTLM2 changes it became
quite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 9 Jan 2004, Gilberto Nunes wrote:
Hi everybody
I get it the follow error:
The System can not log on.
Between parentheses (C001).
What the means of this, please?
This is the hex code for NT_STATUS_UNSUCCESSFUL. You'll need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 9 Jan 2004, Pence, Alan wrote:
Thanks Jerry,
I checked the forgotten manual (actually three of them), and looked
through the man page (for 2.2.8a) for smb.conf but didn't find
information on smb signing that looked to be the right
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 10 Jan 2004, John H Terpstra wrote:
On Sat, 10 Jan 2004 [EMAIL PROTECTED] wrote:
I am getting the following error when trying to connect to
http://localhost:901
500 Server Error
chdir failed - the server is not configured
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Schuster wrote:
Is there any setting / patch / anything we can do to make samba use
symbolic links correctly?
It's probably the windows application removing the original file and
creating a new one. Check level 10 samba logs to verify this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
If there's a better way to do it, let me know -- I couldn't find anything
so I rolled my own and I'd like to offer back the solution to anyone else
who needs it. I'm aware that perhaps in the future Samba will
use an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 15 Jan 2004, Fran Fabrizio wrote:
In the course of debugging my still-unsolved smbclient tar starts
throwing SMB signature errors after 750MB of data or so error, I came
across this apparent inconsistency...
From the smb.conf man
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt McParland wrote:
| I saw the same symptoms using Samba 3.0.1 and a
| Win2k ADS.
|
| Entering the IP address in Start - Run works, but
| browsing NN or entering the FQDN would not. That brings
| up the shares on the Samba server but still can't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 15 Jan 2004, David Bear wrote:
we have two machines/users that experience extremely long wait times
when printing documents to samba servers. Both machines are Windows
XP. We have also noted that both were running personal firewalls, one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a release candidate snapshot of the Samba 3.0.2 code
base and should be considered for testing only. A release
candidate (RC) means that we are close to the final, stable
release and is provided for Quality Assurance (QA) purposes.
This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 20 Jan 2004, FRANCOISE Jacques wrote:
hello,
I have the same problem, did you find a solution?
Enable encrypted passwords on the Samba server.
cheers, jerry
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 19 Jan 2004, Nathan Brown wrote:
I have tried that. That was one of the first preliminary things I did.
That isnt the problem. Its with windows 2000, where you have to type in
a username and password to join a domain, and its not accepting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 16 Jan 2004, Paul Coray wrote:
Dear all
We've been running sucessfully a 2.2.8a Fileserver, member of our NT
domain, authentication with winbind, on a Solaris box. As I've
experienced stability issues with winbind and some minor problems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 19 Jan 2004, Collen wrote:
G'day.. just haveing the straingest problem..
I'd upgraded to the 302rc1 version. i configed it to be an pdc controller,
with wins to manage our local domain..
only when browsing the domain list.
it gives error(s)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 8 Jan 2004, Jeffrey M. Hardy wrote:
We have a Samba box set up as our primary campus print server, running
CUPS 1.1.19 and Samba 3.3.0. Our primary interface for adding printers
is the Add Printer Wizard. I am finding very slow response
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 12 Jan 2004 [EMAIL PROTECTED] wrote:
I have a directory on Unix exposed as a Samba share. All the filenames
are greater than 8.3 format. When I go to this directory from a DOS
prompt and do 'del *.*', I get a bunch of errors 'Unable to find
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 12 Jan 2004, Jason Jeremias wrote:
I upgraded from Samba 2.2.8a to Samba 3.0.1, since doing I'm having
problems with my SQL Server and applications running on Windows 2000.
When a users (running a windows 98 client) attempts to query the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 20 Jan 2004, Ric Tibbetts wrote:
I just installed Samba 3.0.2 pre1 on a Solaris 9 server.
smbd/nmbd/winbindd all start ok. But when it first starts, if I try
wbinfo -u, it hangs. As does getent passwd. This will continue for
the first couple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 20 Jan 2004, Unix Service (ANTS) wrote:
Why is the linux box now calling a different function to the solaris
host - is it because the linux host has already created the user and
has it cached some where ( if so, how can I delete the cache
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 15 Jan 2004, Beast wrote:
But I need some clarification from samba team (Jerry?) whether we can
use this filter without breaking any other functions or not, because
they must be has strong reason using default filter.
My opinion is that the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 16 Jan 2004, Karel Kulhavy wrote:
usrmgr.exe administration works for me.
However, sometimes it is necessary to reopen the domain up to couple
of times until the administration starts working.
Allegedly also it's not necessary to press
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua Beall wrote:
Hi All,
When I try to do cat message.txt | smbclient -M machinename or
smbclient -M machinename, I get:
added interface ip=192.168.0.100 bcast=192.168.0.255 nmask=255.255.255.0
snip all other interfaces; about 25 more
Got a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alex de Vaal wrote:
Summarization of the bug in Samba 3.0.2pre1:
It seems that an ADS group is not valid or detected anymore to access a
samba share, in case only an ADS group is used a valid user on a Samba
share, because Kerberos is reporting:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Beast wrote:
If I did not set ldap filter then according man page
(smb.conf) it will be:
Default: ldap filter = ((uid=%u)(objectclass=sambaAccount))
The ldap filter parameter is irrelavant in some searches (such as the
idmap backend ldap searches
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Collen wrote:
G'day.. just haveing the straingest problem..
I'd upgraded to the 302rc1 version. i configed it to be an pdc
controller, with wins to manage our local domain..
only when browsing the domain list.
it gives error(s) once in a while..
An
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Coray wrote:
Fact is, on my still running production systen (Samba
2.2.8a on Solaris 9, Sparc) this works great. Each User
in our NT-PDC Domainuser database will get a home and
a backupdirectory, when he connects to the Samba box
for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 14 Jan 2004, Peter Wu wrote:
Hello,
I installed samba 3.01 on my Gentoo Linux box. Recently, I find a strange
problem that after I manipulate the shares on the samba server, which is
my Linux box, from my Windows XP Pro workstation, the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 21 Jan 2004, S D wrote:
I am trying to compile samba 3.0.1. I get the following
error when I run the make. Thanks for any suggestions.
You're on Solaris right ?
include/includes.h:830:18: popt.h: No such file or directory
*** Error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Bartlett wrote:
Naturally, this just means you need to give nss_ldap the same ldap base
DN to search under as samba is using. Naturally, if nss_ldap only looks
under ou=people, then it's not going to work, but I set my base dn to
just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Bork wrote:
Hi,
smbd eats a lot of cpu time and there is this error in the log:
[2004/01/21 23:30:00, 0] lib/util_str.c:string_sub(1221)
ERROR: string overflow by 6 in string_sub(%m, 73)
21:53:20 up 15 min, 2 users, load average: 2.37,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unix Service (ANTS) wrote:
(1) everything I'd read about samba + winbind implied that
the nsswitch.conf was only necessary if you wanted other
unix services ( i.e. not samba ) to use winbind
Nope. the nss interface is required by smbd as wel.
(2)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John H. wrote:
| net groupmap modify ntgroup=Domain Admins unixgroup=504
|
|
| net: ../../../libraries/liblber/decode.c:644: ber_scanf:
| Assertion `((ber)-ber_opts.lbo_valid==0x2)' failed.
|
| I was told this may be specific to ldap setup
| with samba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Beast wrote:
| Sorry for asking, when will 3.0.2 released? I've plan to use
| 3.0.2 on production and now I'm under tight schedule :-(
Soon. We have to do an RC2 this week and then maybe 3.0.2
final next week.
cheers, jerry
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John H. wrote:
| net-3.2 groupmap modify ntgroup=Domain Admins unixgroup=ntadmin
| -s /etc/samba/smb.ldap
| ldapsam_update_group_mapping_entry: failed to
| modify group 504 error: attribute 'sambaSID' not
| allowed (Object class violation)
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 26 Jan 2004, John H. wrote:
i thought i had, but apparently not, so i did that and this is what i
have now(as you can see, there are two entries)
net groupmap list -s /etc/samba/smb.ldap
Power Users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 23 Jan 2004, Ganguly, Sapan wrote:
One thing has changed since I installed 3.0.2rc1, before I could do the
following -
id -a windowuser
And I would get a list of all the windows groups that windows user is a
member of, but now it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 24 Jan 2004, Andrew Bartlett wrote:
Various changes to our NTLMSSP support, used to authenticate us to the
server.
This was actually an schannel bug in smbd (worked in winbindd).
It has been fixed in 3.0.2rc1 (verified by several
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 23 Jan 2004, Alex de Vaal wrote:
I actually read the WHATSNEW of 3.0.2pre1, but it wasn't that obvious
for me that I had to disable winbind use default domain = yes in my
configuration. My samba setup was working with 3.0.0-2 and the only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Allison wrote:
| On Tue, Jan 27, 2004 at 12:44:34PM -0500, Karl DeBisschop wrote:
|
|I'm being told that when winbindd is used to connect a Linux client to
|an NT PDC, that encrypted passwords cannot be used in transport. In
|other words that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Kordish wrote:
|
| Do any of the latest versions of Samba
| interoperate with WinFS found in Microsoft future OS
| called Longhorn ?
My understanding of WinFS is that it will be a new protocol
with a new client network redirector. I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here's an update for those of you struggling to get Samba
working in an AD domain environment.
~ Summary: in securirty = ads, clients can browse to the
~Samba member server via IP but not by name (either netbios
~or DNS). Kinit and wbinfo -t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John H Terpstra wrote:
| The current Samba-HOWTO-Collection.pdf
| Section 7.4.2 says:
Sorry. I wrote part of the message thinking it was the
default enctypes lines but it was the permitted enctypes
lines. And it is the out of date MS interop guide
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Arguello wrote:
| Hi.
|
| Giuseppe
|
| Ok, when i login in Windows 2000 as Administrador of the machine (not as
| a member of the Windows 2k domain) everything works fine, if i use the
| command net use * \\server\share, this command works
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Arguello wrote:
| [EMAIL PROTECTED] root]# klist tickets
| klist: No credentials cache found
| (ticket cache FILE:tickets)
smbd doesn't use a keytab yet. Its all done in memory.
| [libdefaults]
| ticket_lifetime = 24000
| default_realm =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alfie Noakes wrote:
|
| If I use a domain name as an entry for hosts allow in
| SMB.CONF, will it cause a huge amount of DNS lookups, or just a
| couple when a new connection is made?
Should just be one for the connecting machine (a reverse lookup)
and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Collen Blijenberg (MLHJ) wrote:
| just noticed the following problem..
|
| after running samba 302rc1(as pdc) for a few day's.
| old SMBD pid's are left in the procces tree..
| eating memory and cpu time, causing linux to overload and not function
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julia wrote:
| When I run the 'make install' after a successful 'make' I get
| some error at the end. Is this a bug?. This is samba-3.0.0,
| and Solaris 9 Sparc. Thanks
|
| # make install
|
| Installing bin/recycle.so as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| I upgraded from Samba3.0.1 to Samba3.0.2rc1 and got now following
| problems:
|
| LaserJet printers 6MP (sorry, we have no other LaserJet
| printermodels) now couse the application to crash. With
| Samba3.0.1 there was no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ole Nord wrote:
| We have newly installed ADSL/speedTouch 510 modem. After the installation,
| we are getting problems with out Win2K machines. On out NT workstation
| everything is OK, but on the Win2K we are getting following error,
|
| The semaphore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a release candidate snapshot of the Samba 3.0.2 code
base and should be considered for testing only. A release
candidate (RC) means that we are close to the final, stable
release and is provided for Quality Assurance (QA) purposes.
This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Gray wrote:
| I've read in the documentation that Samba does not use ports
| like Win2k. So how does Samba know where to find a network
| printer if it has it's own IP address (stand-alone printer)?
Samba is a spooliong system that hands the job
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| Hi Jerry et al,
|
| I'm using the 3.0.1 release in 'ADS' mode with ~450 print queues and ~150
| users (getting migrated right now, will be ~3.000 in the end). In general
| everything works fine apart from some smaller driver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micha Zapanik wrote:
| Hi
|
|
| I saw your post about bug in Samba 3.0.1:
|
| Quote:
|
| A lot of people have complained about unreliable connections to W2K
| and XP machines. The folowing patch solved the problems for us. I have
| no idea why it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
MH - Entwicklung wrote:
| Hello out there,
|
| can anybody tell me how to generate a new DOMAIN SID for a
| SAMBA 3 Server. I cloned a server and want to give it
| a new SID automatically.
remove secrets.tdb (and possibly the sambaDomain object in
LDAP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 4 Feb 2004 [EMAIL PROTECTED] wrote:
I'm attempting to set up a 2-way NT4-style trust between samba 3.0.1-2
(from source rpm on redhat 7.2) and Windows 2003 running active directory.
The AD server (SANDMAN) trust of my Samba domain works
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jerry Haltom wrote:
|
| Could a corrupt .tdb of any sort be causing this? It
| is touching a variable named pdb (maybe printer db?),
| but I'm not sure what that is.
It could I guess, but I agree with Jeremy. That's a
strange place to crash. How many
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan Friess wrote:
| I have ACLs working with both setfacl and smbcacls. I can
| view ACLs and change permissions of users already in the ACL of a file
| on the server using a Windows XP client. However, when I try to add
| a user, after giving
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig White wrote:
|
| If samba3 is installed as PDC, do i net to create machine
| trust account for this PDC?
|
| wouldn't seem to be necessary - it is actually automatically
| done if you join an existing domain and migrate with the net
| rpc vampire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Russell wrote:
| Well, it turns out that we ran out of available uids when we
| ran wbinfo -u. The number of trusted domains and users was VERY
| large. I'm guessing the new user just didn't get assigned a uid
| in the range because they weren't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Beast wrote:
|
| removing secrets.tdb ldap Sambadomain doesn't help.
| Samba then simply has no SID at all.
| As it creates one during install there should be some
| tool to recreate it.
Trust me.
~ stop smbd, nmbd, winbindd
~ rm secrets.tdb and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Did you read comment #11 in
~ https://bugzilla.samba.org/show_bug.cgi?id=395
Looks like a bug in Solaris patch 112960 (r03)
Sojka Reinhard wrote:
| we are running several test installations of Samba 3 on Solaris 8 and
| Solaris 9. On Solaris 9,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 9 Feb 2004, Will Saxon wrote:
I have some more information concerning my print management speed issues
from last week. In a level 10 log, I see several 'print cache expired
for queue printername' whenever I try to open the Printers folder.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 9 Feb 2004, Jed Tarungo wrote:
Function address 0x6062e728 caused a protection fault. (exception code
0xc005) Some or all propery page(s) may not be displayed.
This was fixed in 3.0.1 IRC.
cheers, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 9 Feb 2004, Nishant Sharma wrote:
On comparing the LDAP attributes of the users whose passwd I had reset
and of those I didn't, I observed that when the value of the following
three attributes are set to '0'(zero) for a user, he was not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Ritchie wrote:
|
| How do i get samba to accept a self signed certificate
| from my ldap server?
You need the openldap client libs to accept the cert.
See the howto at
http://www.openldap.org/pub/ksoper/OpenLDAP_TLS_howto.html
cheers, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karel Kulhavý wrote:
| bash-2.05b$ gpg --verify samba-3.0.2.tar.asc samba-3.0.2.tar.gz
Make sure you uncompress the file first.
(See http://samba.org/samba/download.html)
- --
cheers, jerry
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Heupink, Mourik Jan C. wrote:
| Using force user etc in smb.conf is not an option (afaik)
| because that only applies to a top level directory, and not to
| deeper directories, right..? (please do correct me if i'm
| wrong here already)
force user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bryan White wrote:
| I have upgraded my Fedora Core 1 file server from
| the distribution supplied 3.0.0 RPMS to the Fedora/Samba 3.0.2
| RPMS I found on the Samba Web Site.
| This was all working before the upgrade.
I goofed the RPMS. my build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William Enestvedt wrote:
| I'm going to download Samba 3.0.2 and compile it, and
| I'm curious what, if any, recommendations you have for
| a compiler. I initially tried to use Sun's Forte compiler
| when I cewt up 3.0.1, but that was a dead end. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manfred Odenstein wrote:
| I've tried to install the printer drivers for clients
| (win9x/2000/xp) via the APW (add printer wizard), but
| I've failed with access denied. If I changed the
| filesystem permissions in the [print$]-path in the way
| that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
amrito wrote:
| Basic effect:
| when attaching a network drive, the system asked for a password and
| afterwards rejected the service with a message like
| 'invalid user or password'
Is the last change time on the password set to 0 by chance?
Please
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinke Bonte wrote:
| decode_pw_buffer: incorrect password length
fixed in 3.0.2 (or install sp3 or later on the 2k client).
cheers, jerry
- --
Hewlett-Packard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 12 Feb 2004, Lewis Shobbrook wrote:
Heads up,
These should fix the cups problems reported on the list
yesterday. See http://samba.org/samba/ftp/Binary_Packages/
Where the deb's also effected?
All printers are shared here,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karel Kulhavý wrote:
| Is this a bug in pdbedit? What kind of debugging
| information should I provide to help with debugging pdbedit?
We're going to have a release fairly quickly to address this
(and a few other things). Stay tuned. Should be in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karel Kulhavý wrote:
| I have deleted the whole samba tree (rm -r /usr/local/samba)
| and reinstalled samba-3.0.2 with '-g' compiler flag switched on
| with make install and now pdbedit -L works.
|
| Fortunately I have saved the old tree
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Spencer wrote:
| I am looking at my computer accounts that were created using
| smbldap-useradd.pl -w workstationname. And I see the following
| objectClasses:
| top
| inetOrgPerson
| posixAccount
| sambaSamAccount
|
| I understand I need one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Heads up,
These should fix the cups problems reported on the
list yesterday. See http://samba.org/samba/ftp/Binary_Packages/
cheers, jerry
- --
Hewlett-Packard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Spencer wrote:
| I understand using inetOrgPerson for my user accounts, but for the
| computer accounts seems a little strange.
|
| Its not going to break anything changing from inetOrgPerson to
| sambaSidEntry will it? Solely for the computer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Wenzel wrote:
| I use Samba 3.0.2rc2 on Suse 9.0 (heimdal 0.6-68) as a
| Domainmember for File -and Printservices (about 100 Users).
| The Linuxbox ist added to the ADS, the User are mapped
| through winbindd. Everything works..
|
| The I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ww m-pubsyssamba wrote:
| Hi All,
|
| can anyone tell me the logic behind which DC winbind will
| bind to in a 2000/3 AD domain? Is this in anyway linked to the DC
| listed in krb5.conf or does winbind understand W2K sites (defined
| groups of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karel Kulhavý wrote:
| Hello
|
| How do I subscribe to samba-docs mailing list? The list is listed at
| http://samba.kn.vutbr.cz/samba/archives.html
| however it is not listed on the subscription page at
| http://lists.samba.org/mailman/
| judging by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Flowers, Chocolate, a weekend at the beach, and Samba 3.0.2a.
Samba 3.0.2a is a minor patch release for the 3.0.2 code base
to address, in particular, a problem when using pdbedit to
sanitize (--force-initialized-passwords) Samba's tdbsam
backend.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 13 Feb 2004, [iso-8859-2] Karel Kulhavý wrote:
There is something that looks like a deadlink on Samba website.
http://samba.kn.vutbr.cz/samba/archives.html contains
a href=http://lists.samba.org/pipermail/samba-docs/;docs/a which
is an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
darrel wrote:
| I can not connect to my linux box from my Mac. I get a 'Could not
| connect to the server because the name or password is not correct' error.
|
| I'm not sure where to check to even see what username/pwd samba is using.
|
| If I open up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John H Terpstra wrote:
| On Wed, 18 Feb 2004, TeeCee wrote:
|
|
|Hi! :o)
|
|I've got an Debian linux running on an Alpha machine.I had a Celeron
|II before, with Samba 2.2.6. I've made the change to Samba 3.0.0 and
|then I've just upgraded to 3.0.2a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jérôme Fenal wrote:
| The idea would be to add support to smbldap-tools for an
| uidpool in the directory. One more LDAP search to find the
| next uidNumber, but many many less than doing incremental
| searches to find the hole to fill, and moreover
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
wrote:
| wb_getgrgid: failed to locate gid == 1000
This is winbindd looking in its local list of group.
The failure message is normal in your case. The problem
is somewhere else. Probably an interaction with pam_unix
in /etc/pam.d/telnet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jordan Thompson wrote:
| Can't print from client computers:
|
| I tailed the /var/log/samba/log.phong (note phong is a windoze
| client) and got:
| [2004/02/10 12:10:20, 0] tdb/tdbutil.c:tdb_log(531)
| tdb(/var/cache/samba/printing.tdb): rec_free_read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Günther wrote:
|
| is it possible to use encrypt passwords=yes in the
| main server configuration and encrypt passwords=no
| in the virtual server configuration?
Yup. Done it. If you have win2k or later clients and
using Samba 3.0, you will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nanou691 wrote:
| Hello,
|
| We have *samba 3.0.2a* server running winbindd and
| security=ads in smb.conf.
|
| The authentication of ads users works fine.
| However, our environment requires using *both Domain
| and Local* users at the same time.
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alon Shalita wrote:
| Hello.
|
| In our samba configuration, the lock directory is located
| on an NFS mount. It seems that for some reason this
| causes many problems:
We don't support storing the lock directory on an NFS mount.
cheers, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Day wrote:
| Does anyone have a suggesion on what to try next?
| Can anyone verify that they've successfully built Samba
| 3.0.2 on Solaris 8 or 9?
Make sure that /usr/usb is not in your path.
cheers, jerry
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 2 Mar 2004, Mike Samba wrote:
I have been using Samba as a print server successfully for quite some
time. I have one issue that I can't seem to solve. We use a crappy
piece of accounting software that requires the printer be set up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 26 Feb 2004, Spam wrote:
Is there any way to keep file streams over Samba shares? I realize
that Linux filesystems does not have something similar. However one
way Samba could do it is to use additional files (hidden to users).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapin(c) wrote:
Hi all,
I encounter a problem when I try to connect a Samba3
server as a BDC on a ASU HP/9000 PDC server.
If you could send me a level 10 debug log and a raw network capture
file of the failure (off list), I'll try to take a look.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bjoern Jacke wrote:
Is there any way to keep file streams over Samba shares? I realize
that Linux filesystems does not have something similar. However one
way Samba could do it is to use additional files (hidden to users).
It could also be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dmitry Monakhov wrote:
I have the same problem using samba 3.0.2a SUN Solaris-9 SUN One
Directory Server 5.2
Supplementary groups are recognized quite correct under unix shell
environment, but samba can recognize them only from /etc/group file
401 - 500 of 4276 matches
Mail list logo
