Alexander Tamm wrote:
> Hi,
>
> We recently upgraded from 3.0.2a to 3.0.7 and are having problems with
> using shares. Our Win2K-clients must use the dns-name of the
> samba-server to use the shares
> eg. \\smbserv.domain.com\share
> instead of
> \\smbserv\share
> Otherwise the user is asked for username and password, but is refused
> access, regardless of whether the password is right or wrong. However,
> if a wrong password is given several times, the user is locked out
> from the AD. (PDC is a Win2K-server.)
>
> The NT-boxen, OTOH must use the form \\smbserv\share.
>
> Any advice on where to start looking for errors?
>
> Regards,
> Alex
It sounds like you are probably using the kerberos integration and
encountering the same problem that many people have been reporting since
upgrading to anything above 3.0.4. I imagine that this also works if
you access shares via ip address. I am not aware of any progress being
made in regard to isolating the cause of this problem. Some people have
reported that by downgrading samba releases they get back functionality,
others have reported that downgrading doesn't help at all. The only
similarities seem to be:
1. Samba/Kerberos integrated in an AD environment with a win2k DC
(we're all well aware of win2k3 issues)
2. Everything was functional until upgrading samba releases.
3. Kerberos problems exactly like what is encountered in win2k3
environments when the linux server is using an incompatible/outdated MIT
kerberos package.
Out of curiousity what linux platform are you running on?
Christian