You should be able to find the server in W2K's server manager and confirm
that it is a trusted member of the Domain.
It sounds like smbd isn't linking to the acl libs-have you run ldd to see if
you are linking to libacl.so.1?
My recent problem was similar and I found that I wasn't compiling against
the acl libs.
Make sure you have the line (Max said you should have this
before --with-msdfs)
--with-acl-support in debian/rules,
Plus you have to
vi debian/config.cache
--> replace
"ac_cv_header_sys_acl_h=${ac_cv_header_sys_acl_h=no}"
with "ac_cv_header_sys_acl_h=${ac_cv_header_sys_acl_h=yes}"
Good luck-it's well worth it once it works!
Tom Hallewell
Radio Free Asia
Washington DC, USA
>
> Hmm.
>
> I don't have a third machine to be a W2k client here (the real setup
> will have several hundred, both 2k and NT4, but I'm testing at
present).
> Hence I have two machines:
>
> * a W2k server which is acting as PDC
> * a Samba server which is authenticating to the PDC but providing file
> services
>
> and I'm reusing the W2k server as a client - ie. trying to access files
> on the Samba server from the W2k box.
>
> As far as I can tell the Samba machine has already joined - password
> authentication doesn't work if it doesn't join.
>
> --
> ANDREW FUREY <andrew@terminus.net.au> - Sysadmin/developer for
Terminus.
> Providing online networks of Australian lawyers (http://www.ilaw.com.au)
> and Linux experts (http://www.linuxconsultants.com.au) for instant help!
> Disclaimer: http://www.terminus.net.au/disclaimer.html. GCS L+++ P++ t++
>