Displaying 20 results from an estimated 2000 matches similar to: "PAM sending wrong username to Winbind"
2004 Dec 28
1
PAM sending wrong username to Winbind (fwd)
Hi All,
I have tried logging into ftp using my NT username and password and it
works. It is only SSH which has this problem.
http://216.109.117.135/search/cache?p=pam+NOUSER&ei=UTF-8&fl=0&u=www.publicsource.apple.com/darwinsource/10.0.4/OpenSSH-9/openssh/auth2.c&w=pam+nouser&d=E6EA31C37E&icp=1&.intl=us
The above link gave me this hint. Found it while looking for
2005 May 31
0
windbind stopped working
I recently upgraded my PDC's and BDC's to 3.0.14a but my member servers
are still running 3.0.10. Today users complained that the couldn't
logon to the member server. When I try to run a wbinfo -u I get:
Error looking up domain users
Here's the log.windbindd:
2005/05/31 11:06:26, 4] param/loadparm.c:lp_load(3933)
pm_process() returned Yes
[2005/05/31 11:06:26, 3]
2005 Apr 19
0
Winbind and Samba/LDAP PDC
Hi Samba Users,
I am currently in the process of migrating from an NT4 Domain to a
Samba/LDAP Domain.
I am already running a number of samba servers which are domain member
servers in the existing domain. They retrieve their account information
from the NT4 PDC using winbind.
So far i have completed the NT4 to Samba/LDAP migration as described in
chapter 9 of Samba by Example up to the point
2004 Sep 22
0
samba 3.0.7 cannot join NT4 domain
I looked into the docs and searched thru the Net.
Googling for "NT_STATUS_PIPE_NOT_AVAILABLE"
yields rather large list of questions about
this situatins, but no working hints so far.
I believe my samba installation is done very carefully
(entirely unlike "grab rpm and be happy" style)
and I can try to find out what's going on.
Let me describe what do I have so far:
My
2004 Jan 07
1
Can't connect from Windows
I am setting up my first 3.0.1 installation. I am using Slackware 9.1, I am
trying to connect to a Windows 2000 Server. I do not need active directory
support (as far as I know). The server's function is a file server. So
Users need seamless authentication... of course. I do not have LDAP
installed. It's a plain server besides the 3ware RAID.
I compiled and installed samba 3.0.1,
2005 Jan 24
0
winbind debugging help.. act 2
Folks,
Not even a peep. Did I ask the wrong question or am I on the wrong
list? I don't mind pointers to more information....
I own both the recent books on Samba 3 and they are very good, but I seem
to be missing something.
Anyways...
Thanks and hope to hear from you soon,
Michael J Barber
WPTZ/WNNE
Computer Services Administrator
p 518-561-5555 x563
m 518-572-6639
f 518-561-5940
2005 Jan 21
0
winbind debugging help..
smb.conf (relavent section)
[global]
workgroup = WPTZ
security = DOMAIN
map to guest = Bad User
password server = WPTZSRV1, WPTZ-BDC
username map = /etc/samba/smbusers
log level = 2
syslog = 3
time server = Yes
printcap cache time = 750
printcap name = cups
logon path = \\%L\profiles\.msprofile
logon
2004 Sep 23
0
3.0.7 net join to NT4 domain - silently fails?
I've got no responce to my mail with subject
'samba 3.0.7 cannot join NT4 domain', so I dug deeper.
I also read carefully these docs:
swat/help/Samba-HOWTO-Collection/domain-member.html
swat/help/Samba-HOWTO-Collection/winbind.html
This is what I observe:
1.I srtart from clean state:
PDC has no HUNTER machine account (chkd with L0phtcrack)
HUNTER has empty var/{lock,private}
samba
2004 Aug 15
1
Winbindd startup kerberos fail
I'm trying to learn about the interactions between SAMBA and Win2k
DCs.??The eventual goal is to have a Win2k server with ADS working with
a FreeBSD SAMBA server.??I've?used?the?setup?from
http://oslabs.mikro-net.com/fbsd_samba.html and many other articles as
the basis for what I've done so far. Winbind seems to work and I can
show users and gropus using wbinfo although I see some
2004 Jul 20
1
Log shows NT4 for an ADS domain
I'm trying to learn about the interactions between SAMBA and win2k DCs. The
eventual goal is to have a Win2k server with ADS working with a freeBSD
SAMBA server. I've used the setup from
http://oslabs.mikro-net.com/fbsd_samba.html as the basis for what I've done
so far. Winbind seems to work and I can show users and groups using wbinfo
although I see some things in the logs that I
2004 Aug 06
0
samba & winbind with AD 2K auth problem
Hi
I cannot make winbind work correctly. My problem is that my AD users &
groupes are not authenticated on my samba box. I made it work correctly on my
samba 2.2x, an dfrom my understanding, each time a AD user is connected, a Unix
account is created, nad winbind synhronize both accounts.
It looks like the user script "/usr/sbin/useradd -s /bin/false %u" doesn't work,
and my
2005 Mar 29
2
Problem with wbinfo
Hello,
I'm using a Samba client to access a Samba Server. The "smbclient
tool" is ok, both at the client as at the server. I'm having trouble
with the "wbinfo" command (winbind service) at the client, as you can
see below.
Can anybody help me?
Thanks!!!
=Problem==============================
Samba Server: samba-3.0.10-1.fc2
Samba Client: Version 3.0.0-14.3E
2004 May 21
0
winbind issues with AD domain trust
I'm setting up Samba in an environment with 2 Active Directory domains setup
with a one way trust (DOMAINA -> DOMAINB). Samba is in DOMAINA. From
looking at the logs (see below) it appears that winbind is having troubles
getting the credentials for the domain controller in DOMAINB.
I can get tickets, using kinit, for accounts in both domains. I can join
DOMAINA just fine. Running
2005 Jan 23
1
Winbind without netbios
Hi there,
Im using for long time winbind + squid for my proxy server and it has
been working very good... No problems at all.
Some months ago, I decided to get rid of Netbios protocol and start to
use only dns for name resolution on my domain. That's when my problem
begin.
All my windows servers and workstations are doing fine without netbios
but I cant get winbind to work without
2005 Mar 15
1
SMB signing broken? 3.0.7 -> 3.0.8
Hi all.
I originally suspected this problem was with netbios (which I have
disabled by default) and Jerry has helped me out a bit with but I've
been doing some more digging and I think the problem lies back further
than I expected.
I was trying to upgrade from 3.0.7 to 3.0.11 so I've recompiled all
versions back from 3.0.11 and the problem first occured in 3.0.8. The
issue is with
2005 Jun 24
0
Winbind NT domain authentication
Hi list,
Sorry for the cros-post, I'm not sure which list is better for
me as I got a question related to samba, configuration, FreeBSD.
I'm trying to configure NT authentication on FreeBSD 5.4 with
Samba 3.0.12 (installed form the ports collection).
I've folowed the Samba 3 howto I've managed the following :
wbinfo -g returns correctly the domain groups
wbinfo -u returns all
2005 Jun 24
0
Winbind NT domain authentication
Hi list,
Sorry for the cros-post, I'm not sure which list is better for
me as I got a question related to samba, configuration, FreeBSD.
I'm trying to configure NT authentication on FreeBSD 5.4 with
Samba 3.0.12 (installed form the ports collection).
I've folowed the Samba 3 howto I've managed the following :
wbinfo -g returns correctly the domain groups
wbinfo -u returns all
2015 Apr 03
0
Member server - winbind unable to resolve users/groups
Greetings, Rowland Penny!
>>>>>>> I'm trying to get the former PDC back into domain after performing a
>>>>>> classic
>>>>>>> migration.
>>>>>>> AD DC is running fine... if you can call it that.
>>>>>>> I've edited the smb.conf and nsswitch.conf as suggested in Wiki article,
2005 Jul 27
2
wbinfo can't list users
Hi,
I'm running debian sarge with kernel 2.6.8-2-sparc64. I'm trying
to use winbind to connect to a Windows 2000 server. I can use
"net rpc join" to join the domain, but "wbinfo -u" returns an
error. The trusted domains listed doesn't include the domain.
Please see below:
cladms003:~# net rpc join -U Administrator
Password:
Joined domain CYBERLAB.
cladms003:~#
2015 Apr 04
0
Member server - winbind unable to resolve users/groups
Greetings, Rowland Penny!
>>>>>>>>> I'm trying to get the former PDC back into domain after performing a
>>>>>>>> classic
>>>>>>>>> migration.
>>>>>>>>> AD DC is running fine... if you can call it that.
>>>>>>>>> I've edited the smb.conf and nsswitch.conf as