Displaying 20 results from an estimated 30000 matches similar to: "samba-3.0.20rc1 winbind Windows 2003 SP1 ADS wbinfo all"
2005 Aug 01
2
samba-3.0.20rc1 winbind Windows 2003 SP1 ADS wbinfo all fine, but getent passsd or group does not work...
Hi,
I've joined a Suse 9.1 Pro linux computer to a Windows 2003 SP1 ADS using:
# kinit Administrator@DOMAIN
# net ads join
The computer account is created on the DC and wbinfo (-t -u -g) all
work. Then I try getent passwd or getent group and nothing.
This is with:
#grep winbind /etc/nsswitch.conf
passwd: compat winbind
group: compat winbind
# ps -ef | grep -E
2004 Apr 13
1
wbinfo -a is failing
I have been reading the FAQ and the online samba how to's and been googeling to find out why wbinfo is failing on me.
I am tryitng to use wbinfo -a domainname\\username%password to authenticate to my MS AD domain but what is happening is every time I try I get the following output.
plaintext password authentication failed
error code was NT_STATUS_NO_LOGON_SERVERS (0xc000005e)
error messsage
2010 Nov 14
1
winbind - wbinfo problem
Hi Guys,
I have configured SAMBA with Windows 2003 AD. But "#wbinfo -u" and
"#wbinfo -g" does not list the users
1. Domain joined successfully.
# net rpc testjoin -U Administrator
Join to 'DOMAIN' is OK
2. wbinfo -a works ( User authentication )
# wbinfo -a 'DOMAIN\user'
Enter DOMAIN\user's password:
plaintext password authentication succeeded
Enter
2005 Oct 31
1
Not all users correctly winbind-ing on Server 2003 SP1 with 3.0.20b
Hi all
This one has me baffled - leading me to beleive it could be a bug
similar to https://bugzilla.samba.org/show_bug.cgi?id=2695
I am running samba 3.0.20b on debian unstable and am having problems
with some users not resolving properly using winbind.
wbinfo -u shows all users on the system, no problem
wbinfo -a user%password works for any user
getent passwd shows most but not all users
2010 Nov 19
1
winbind - wbinfo problem - SOLVED
Hi John,
The same smb and winbind configuration ( same SUSE box ) works good other
Windows AD servers.
"#wbinfo -u" and "#wbinfo -g" returns the users and groups respectively.
Thanks for your great help !!!
what is the difference between "#net rpc" and "#net ads" ?..if you have
time, give some explanation..
Regards,
Vivek
On Mon, Nov 15, 2010 at 6:56
2002 Jun 13
1
"wbinfo -a" problem, plaintext password is not allowed
I'm still having problems with winbind:
wbinfo -u --> Error looking up domain users
So I read a post about wbinfo -a, I tried it but I still can't get the domain's user list because the pdc doesn't allow plaintext passwords:
wbinfo -a user%passwd
plaintext password authentication failed
error code was NT_STATUS_INVALID_PARAMETER (0xc000000d)
Could not authenticate user
2010 Apr 29
1
wbinfo -a fails plaintext auth; passes challenge/response
Once again, I am trying to add a machine to my Win2003 AD (that has
Services for Unix installed). I am using Xubuntu 9.10, and samba 3.4.0.
I set up Kerberos, and am getting a ticket. I have successfully joined
the domain.
# net ads join -U administrator
Enter administrator's password:
Using short domain name -- DACRIB
Joined 'DUAL-BOOTER' to realm 'DaCrib.local'
wbinfo -u
2005 May 01
1
wbinfo -n and wbinfo -s are broken with win2003 SP1
Hi All,
I upgraded my windows 2003 enterprise server to sp1 and having problems with winbindd/wbinfo.
I am using samba 3.0.6 and joined as ADS
wbinfo -u
wbinfo -g
wbinfo -p
wbinfo -t
work like a Swiss watch
However
wbinfo -n ephi
wbinfo -s .....
DO NOT WORK.
Is the latest SAMBA release (3.0.15pre2 and up) cover those issues (-n and -s)
If we joined as DOMAIN (NT4 style)
2007 Dec 12
2
Vista SP1-rc1 appears to break against Samba-3.0.27a
We've got nicely ADS integrated Samba-3.0.27a servers that are working
fine with Win2000 through to standard Vista.
However, we are starting to test RC1 of Vista SP1 and discovered that
once applied, that workstation cannot connect to Samba server shares -
unless the share is open - i.e. no "valid user" style settings. The
moment one is defined, Vista fails to connect and pops up an
2008 Feb 16
1
wbinfo -a not working
Hello,
I'm trying to connect my Debian 4 samba box to my Windows 2003Server Active
Directory.
I successfully joined the domain, with net ads join. Wireshark captures a
lot of packets going over the wire, and I get the message "joined the domain
successfully". In my AD, under 'computers', the samba box appeared. So that
all works.
Asking a kerberos ticket for a user with
2004 Oct 05
1
wbinfo -a always failing with NT_STATUS_WRONG_PASSWORD
Hello!
Please help! I have been googling and experimenting for the past few
days, but I can't get user authentications to work with my AD domain.
Fedora Core 2 running Samba 3.0.7-2.FC2
Windows Server 2003 Standard Edition
After much fuss, I was able to get it to join the domain (had to
disable client signing).
"wbinfo -u" and "wbinfo -g" both work fine, and I can see
2005 Feb 24
3
SLES9+winbind+NT PDC unable to access home shares
I'm running Samba 3.0.9 on SLES9 as a domain member with an NT4 PDC, using
winbind to authorise domain users.
I have set up a general share for all users which works fine and is
accessible by all users but I am unable to set up the home shares correctly.
When attempting to connect via smbclient I get the following:-
tree connect failed: NT_STATUS_ACCESS_DENIED
What does this mean and where
2020 Jul 10
5
wbinfo -u / getent passwd not working
Hello,
i try to setup a linux laptop for homeoffice with login for ad users.
The last few days it work like expected.
today wbinfo -u return no user, getent passwd <username> also.
wbinfo -a "SAMDOM\user"
Enter SAMDOM\user's password:
plaintext password authentication succeeded
Enter SAMDOM\user's password:
challenge/response password authentication succeeded
wbinfo -D
2002 Jul 25
1
password authentication failing for winbind
I originally posted this issue with the heading "winbind: challenge/response
password authentication failed". I was using the redhat 7.3 samba 2.2.3 rpm
then. I've upgraded to 2.2.5, but all that's changed is the return message.
wbinfo -a VENUS0+tassadar%torque
used to get me:
plaintext password authentication succeeded
challenge/response password authentication failed
2001 Sep 19
6
Winbind authentication
Hi everyone,
First of all, could you please CC me, I am not (yet) subscribed to this
list.
Now my problem:
I created a test setup at my office that uses winbind to authenticate linux
users to a Windows NT server (they log in with DOMAIN+username), as described
in the winbindd manpage. I followed their setup completely.
(at my work I am using RedHat 7.1 and the winbindd daemon found in the
2010 May 07
1
Winbind to a Samba 3.4 server
I thought I had setup winbind correctly as I can login to my ubuntu
9.04 machine with domain users, but I am trying to get ntlm working
with squid, and while testing winbind I get the following error.
sudo wbinfo -a MBAG\\user%passwd
plaintext password authentication failed
Could not authenticate user MBAG\user%passwd with plaintext password
challenge/response password authentication failed
error
2010 Aug 17
1
NT_STATUS_INVALID_HANDLE with wbinfo -a
I've been stuck on this one for days and can't seem to find anything
referencing the same problem; help would be greatly appreciated. I have a
functioning Samba 3.5.4-63 installation acting as a PDC - users can log in
from Windows 7 machines without problems etc. etc.
The issue is with using wbinfo -a to authenticate users (without going into
too much detail, I'm trying to use the
2010 Nov 14
1
wbinfo problem
Hi Guys,
I have configured SAMBA with Windows 2003 AD. But "#wbinfo -u" and
"#wbinfo -g" does not list the users
1. Domain joined successfully.
# net rpc testjoin -U Administrator
Join to 'DOMAIN' is OK
2. wbinfo -a works ( User authentication )
# wbinfo -a 'DOMAIN\user'
Enter DOMAIN\user's password:
plaintext password authentication succeeded
Enter
2005 Sep 20
1
Subject: Samba / Windows server 2003 SP1 conflict
Hi,
Try that in smb.conf , global section
Client schannel = no
Server schannel = auto
For me that works...
Kind regards martin schreiber
2011 Apr 10
2
PAM winbind authentication problem NT domain
I have Samba Version 3.5.8-74.fc13 (Fedora 13) set up as the PDC for an NT
domain.
I have several Windows XP Pro and Windows 7 Ultimate workstations as
domain members and everything is working fine. Domain users can log-in
at the workstations, access shares on the Samba server and the other
workstations, etc.
I am in the process of adding Samba Version 3.5.8-76.fc14 (Fedora 14) as an
additional