samba - Sep 2006 - Samba Winbind Error

I am attempting to setup a RHEL4 client to authenticate against a Windows 2003
R2 Active Directory Domain Controller. I am following the Samba HowTo Chapter 24
on Winbind, and everything works until I try to list out users from the AD.
Here's what I get:
   
  # /usr/bin/wbinfo -u
  Error looking up domain users
   
  I can, however list out groups in this fashion:
   
  # /usr/bin/wbinfo -g
  BUILTIN\System Operators
  BUILTIN\Replicators
  .
  .
  .
   
  What I'm trying to accomplish is to have a Linux client authenticate to a
Windows Server 2003 R2 Active Directory Domain Controller (not using a
"scout" account for anonymous lookups) so that this user can access
shared files on the Windows server.  The user is then identified as himself for
the purposes of file access auditing in the Security Event Log.  I don't
want to make any changes to the AD, although modifying the AD schema for Unix
attributes using the new R2 tools would be ok (if needed).
   
  Thanks,
  Ned


Skaggs Consulting, Inc.
St. Charles, MO 63301
636-940-9478
 		
---------------------------------
Do you Yahoo!?
 Get on board. You're invited to try the new Yahoo! Mail.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/05/2006 06:28 PM, Randy Skaggs escreveu:
> I am attempting to setup a RHEL4 client to authenticate against 
> a Windows 2003 R2 Active Directory Domain Controller. I am
> following the Samba HowTo Chapter 24 on Winbind, and everything
> works until I try to list out users from the AD. Here's what I
> get:
>    
>   # /usr/bin/wbinfo -u
>   Error looking up domain users
>    
>   I can, however list out groups in this fashion:
>    
>   # /usr/bin/wbinfo -g
>   BUILTIN\System Operators
>   BUILTIN\Replicators
>   .
>   .
>   .
>    
>   What I'm trying to accomplish is to have a Linux client 
> authenticate to a Windows Server 2003 R2 Active Directory
> Domain Controller (not using a "scout" account for
> anonymous lookups) so that this user can access shared
> files on the Windows server.  The user is then identified
> as himself for the purposes of file access auditing in
> the Security Event Log.  I don't want to make any changes
> to the AD, although modifying the AD schema for Unix
> attributes using the new R2 tools would be ok (if needed).
>    
>   Thanks,
>   Ned
	Can you run testparm to check what happens?

	And can you send the smb.conf so we could have a look to
it? If there are any logs, they would be *very* useful, try to
increase the loglevel/debuglevel.

	Kind regards,

- --
Felipe Augusto van de Wiel <felipe@paranacidade.org.br>
Coordenadoria de Tecnologia da Informa??o (CTI) - SEDU/PARANACIDADE
http://www.paranacidade.org.br/           Phone: (+55 41 3350 3300)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFFBqb9Cj65ZxU4gPQRAm+5AJ0Qw5NKr2UZF4tkvMZwatNRrSqqOwCgjZnz
eE6IOv/zjBhursfznlQWZwk=39gQ
-----END PGP SIGNATURE-----