Bug 4893 - AUthentication failure
Summary: AUthentication failure
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: samba
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-09-03 20:38 UTC by ldrake
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-09-03 21:34:23 UTC

Attachments (Terms of Use)

Description ldrake 1999-09-03 20:38:46 UTC
smbmount as released with REdHat 6.0 failes to authenticate
with NT Domain Controllers. Upon using the 'domain
controller =' specification in smb.conf, upon use, smbmount
reports "ignoring unknown directive 'domain controller'

This did function properly with the REdHat 5.2 distribution.

I have attempted downloading your security patch with no
positive results. The problem persists. At first, I thought
this was due to the fact that I had selected to "upgrade" my
installation from 5.2 to 6.0... Then I made backup tarballs
of all pertinent data directories and started off clean
(Reworked all drive partitions and did a full install) This
proved that the "upgrade" path was not a fault as the
problem persisted.

The hardware is a Dell Optiplex 590. 32 MB RAM, 1GB Hard
Disk, embedded S3 Video controller, 3C509 Ethernet adapter,
generic PS/2 mouse and keyboard. Nothing out of the
ordinary... Creative 4x CD-Rom is about the only added in
item to the unit.

There are no other operating systems on the machine.

I am also running the Apache web server as an intranet
server behind our firewall and proxy machines (NT).

Comment 1 Bill Nottingham 1999-09-03 21:34:59 UTC
Read the man page:

       domain controller (G)

              This is a DEPRECATED parameter. It is currently not
              used  within the Samba source and should be removed
              from all current smb.conf files. It is left  behind
              for compatibility reasons.

Try setting 'security=domain'.

Note You need to log in before you can comment on or make changes to this bug.