CIFS Server: problem with 'wbinfo -u' and 'wbinfo -g' command

[SYSTEM ADMINISTRATOR_7]

Hello,
I have the following configuration
- HP-UX 11.11
- HP CIFS Server A.02.01.02
- /etc/opt/samba/smb.conf in attach

When I issue the "wbinfo -t" and "wbinfo -p" they work, while with "wbinfo -u" (to get the list of users) and "wbinfo -g" the following error has returned:
"error looking up domain users / groups"
"wbinfo -m" doesn't work, too and the error message is "Could not list trusted domains"
However, Samba works and users can access to the unix share.
Any idea?
Thanks in advance

Fabio

[Alessandro Pilati]

Can you post you nsswitch.conf file ?

[Steven E. Protter]

# Security mode. Use 'ads' for configuring with W2K domain and
# use Kerberos as authentication protocol.
security = ADS

What procedure did you use to Integrate with ADS?

I am wondering if that procedure is complete.

There may be helpful information in the Samba log defined in your smb.conf file.

SEP

[SYSTEM ADMINISTRATOR_7]

Here is /etc/nsswitch.conf file you required.

hosts: files [NOTFOUND=continue UNAVAIL=continue] dns [NOTFOUND=return UNAVAIL=continue TRYAGAIN=return]
passwd: compat winbind
shadow: compat
group: compat winbind

services: db files
protocols: db files
rpc: db files
ethers: db files
netmasks: files
netgroup: files
bootparams: files

automount: files
aliases: files

[SYSTEM ADMINISTRATOR_7]

The procedure to connect to ADS was:
- creation of /etc/krb5.conf file (here in attach)
- kinit (result ok)
- net ads join -U administrator%password (result ok)

No problem at all

Fabio

[Geoff Wild]

Check out the settings I used in my smb.conf file from this thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=949365

Rgds...Geoff

[SYSTEM ADMINISTRATOR_7]

I have tried with your settings but with no success. :(

[Geoff Wild]

Hmnnn...try stop/start samba:

stopsmb -w

startsmb -w

Rgds...Geoff

[SYSTEM ADMINISTRATOR_7]

I restarted samba processes many times, but it doesn't change anything.
Our active directory has many users and many domains.
Could it be a timeout problem?
Perhaps "wbinfo -u" command lists users and fails due to too much time require to complete the operation.