We have two systems with dual NICs that run samba 2.2.5 with winbind, and
neither of them is announcing the system's primary IP address correctly to
the WINS server. The systems show up in the wins database with the
secondary IP address (which is the private network we use for the
heartbeat/meta
I had samba working on an old Sun Enterprise server using a JBOD that was
managed with veritas volume manager (legacy stuff that had long outlived
it's usefulness). Management arbitrarily decided to replace the aging
Solaris server with a native Windows server without talking to me. I instead
I was told to go download tdbdump and tdbtool, but I wasn't able to get
them to compile, and it's been sitting on the backburner. I don't recall
what web page serves the source (sorry). Let me know if you have any luck.
Karen Wieprecht
-Original Message-
From: Lynch,
You've already built the libnss_winbind.so files ... Please check the
following
0. This may not have been necessary, but in our /etc/hosts table, we made
an alias for the domain controller that is the name of our domain
10.0.10.11 dc.something.edu ntdomainname
1.In
Is there any special reason that so many people are sending messages to the
list using entrust?
Curious,
Karen Wieprecht
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Did you make sure localhost resolves? Also, depending on your
/etc/resolv.conf, you may have to fully qualify the host's name including
the DNS domain. I seem to rember having problems with this, and some
combination of using localhost or hostname.domain.edu or using the actual IP
address of
I am assuming that you have guest ok = yes, and that guest is the nobody
account. It sounds like your name lookups are not searching winbind, do
you have winbind in your nsswitch.conf file for password and group? Have
you restarted your nameservice lookups (automatic on solaris, nsadmin
I have an SGI cluster (two servers share same physical disk space). I made
the username map live in clustered space and made the
~samba/locks/winbind_idmap.tdb also live in the cluster space via a symbolic
link on both servers. Bother server run samba using the same smb.conf
settings (different
Did you try adding machinename\username to your list of valid users and/or
your write list as appropriate?
Karen Wieprecht
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Title: Message
This
may be an obvious question, but we had to add the machine to the domain
with winbind and samba not running, I am assuming that you have
started samba and winbind before trying the wbinfo tests?
Karen Wieprecht
Why not? It does not affect whether or not my NT user gets matched to a
UNIX UID and GID (username.map does that part for me), but for files
created by users with no corresponding UNIX account, it makes the domain
username show up on an ls -l minus the domain prefix so I can see who owns
the
We have had better luck adding the machine account on the NT domain
controller, then joining the domain with the smbpasswd command rather than
trying to do the whole thing from the smbpasswd command. You could try
deleting the machine account, deleting your secrets.tdb file, and starting
that
Title: Message
1.
What version of samba? You should be trying 2.2.5 or 2.2 6 for one
of the more stable winbind releases.
2. Are
you running NIS? Try changing the winbind separator to _
(underscore)
3..
Did you put winbind in your nsswitch.conf file? If so, did you force
the system to
I had the same configure problem, ended up downloading a pre-built version
from the SGI freeware site, but thought I'd try again after I had applied
some patch updates ... Oddly enough, after the patch updates, my samba
configure no longer gave me those errors. I wish I could tell you which
Title: Message
You
can do the following:
0.
Stop winbind and samba
1.
Delete the hosts machine account (on the NT domain controller),
verify that the machine account deletion has propagated to any backup domain
controllers
2.
Remove the secrets.tdb file (or MACHINE.SID if you are
... I was going
to play with adding other UNIX groups to the write list to see if I could
fix this problem.
Hope this answers your question.
-Original Message-
From: Jennifer Fountain [mailto:JFountain;rbinc.com]
Sent: Friday, October 25, 2002 5:22 PM
To: 'Wieprecht, Karen M.'
Subject
Sorry, I don't know any more, hopefully one of the samba gurus might have
an explanation for the behavior.
Karen Wieprecht
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Title: Message
use
the username.map file capabilities
-Original Message-From: SALOME Alexandre
[mailto:[EMAIL PROTECTED]] Sent: Friday, October 25,
2002 11:17 AMTo: Samba@Lists. Samba. Org (E-mail)Cc:
SAMBA KarineSubject: [Samba] utilizing smbpasswd with two user
1. Run ~samba/bin/wbinfo -u and make sure you are actually talking to your
domain controller
2. Do you have winbind entries in your nsswitch.conf file? Have you made
your system re-read this info (the command is nsadmin restart on irix,
don't know about other platforms).
3. The windows box
Samba 2.2.5
security = domain with winbind
Also Using a username map for users with a corresponding UNIX account.
Username.map:
Karen = WALNETNT_karen
(unix) (nt)
Causes karen to come onto the samba share with UID and GID matching that
used on the UNIX side.
This lets karen (nt) write
Samba 2.2.5, security = domain, using winbind and a username map for users
with a corresponding UNIX account.
Interesting thing: once I got my username map working and the NT users are
getting their correct UNIX UID when they access the shared area from the PC,
they are no longer being
Title: Solution for winbind problem: incorrect password or unknown username
We had winbind running great, but suddenly we were getting this GUI that said:
Incorrect password or unknown Username for :
\\hostname
Connect as: (rectangle to enter username )
Password: (rectangle to enter
I'm testing Samba 2.2.5 with winbind. I can successfully authenticate
domain users who do and don't have corresponding UNIX accounts as well as
domain users who do have a UNIX account. Files created from PC side by
usera show up in UNIX ls -l as owned by usera so I thought the automatic
username
Andrew,
I was having the same problem with getting groups to work, so I
tried your solution, but can't get it to work either.
1. I set up a read only share, made sure I didn't have write access.
2. I added
write list = WALNETNT_karen
and verified that I now had
I'm not sure what happe4ned to the --with-nis option either, but it seems
to work just fine. Perhaps they made it part of the default set? We use nis
and winbind, and NT users with matching UN(IX accounts get assigned the UID
and GID I have in NIS.
Karen Wieprecht
-Original
separator we were using. Changing it
to underscore fixed us up. Let me know if this does the job
for you as well.
Karen
-Original Message-
From: Nir Soffer [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 11:58 AM
To: Wieprecht, Karen M.; [EMAIL PROTECTED]; [EMAIL
I note some distinctions here:
The tools you had trouble with were NT tools, and the problem didn't exist
with all of them. NT is not case sensitive, and so developers of the
various tools and utilities probably handle character case differently. I'm
betting that it's the utility you are
We use samba 2.2.5 in security=domain with winbind running. NT users who
don't have corresponding UNIX accounts are assigned a UID on the fly based
on the range specified in the smb.conf file.
Are there any recommendations for keeping that file backed up or synced up
with another system's
I can't seem to get anyone to respond to this so I'm asking again ...
It seems that the rest of the world is able to get past the configure step
in samba 2.2.5, but I get an error (I didn't have this problem when I
compiled samba 2.2.2 or 2.2.3a, so it leaves me rather stumped).
./configure
Samba team,
I posted the following message on May 30 to comp.protocols.smb, but no one
has responded to the posting as of yet, so I thought I'd try this email
list.
We are testing winbind and security=domain to authenticate NT users on
our UNIX box in samba (v2.2.3a). Winbind is working
We are testing winbind and security=domain to authenticate NT users on our
UNIX box in samba (v2.2.3a). Winbind is working correctly. Wbinfo shows
users as domainname+username (we are using + as the separator), however,
the NT usernames aren't automatically mapping to their corresponding UNIX
31 matches
Mail list logo
