[Samba] Re: XP Pro Autheticate to Samba 3.0 PDC fails: "Access is
denied"
Erich Enke
twilit77 at fastmail.fm
Thu Oct 30 23:59:17 GMT 2003
Oh glorious day! I've figured it out.
For those interested, when joining a samba PDC for the first time from
XP, you must login with the root account. I had tried this before, but
it didn't work because I didn't have a machine account for the machine I
was logging in from (at that time). Note that the root _samba_ account
shouldn't have the same passwd as the root _linux_ account.
Cheers,
epte
On Thu, 30 Oct 2003 15:45:03 -0600, "Erich Enke" <twilit77 at fastmail.fm>
said:
> I've read the docs. I've bought the book. I've searched the lists. For
> three days and still no joy. Please help. Here are the details:
>
> OS: Redhat 9.0 on a Dell Poweredge 2650
> Using stable samba 3.0 rpm downloaded straight from the site
> Configuring by any means necessary: webmin, swat, but right now, smb.conf
>
> I have set up a linux account for smbuser, added him to ntadmins group,
> net group mapped ntadmins to "Administrators", added the XP patch to set
> RequireSignOrSeal to 0, set the smbpasswd, enabled the smbpasswd account,
> restarted smb services, set up a NetLogon and Profiles share (with no
> logon script to make things easier), created a home directory for smbuser
> and such, added a machine account for the machine I am trying to connect
> from (alpha), created the linux user for that (alpha$), and then tried to
> add the XP computer (alpha) to the domain (TEC). It asks for username
> and passwd. I supply both for smbuser. It says "Access is denied".
>
> Next step. I turned up the logging level to 3 (2 didn't give anything
> useful). Here is the log:
>
> [2003/10/29 16:46:03, 2] auth/auth.c:check_ntlm_password(302)
> check_ntlm_password: authentication for user [smbuser] -> [smbuser] ->
> [smbuser] succeeded
> ...
> [2003/10/29 16:46:03, 2] lib/access.c:check_access(324)
> Allowed connection from (192.168.0.199)
> ...
> [2003/10/29 16:46:03, 2]
> rpc_server/srv_samr_nt.c:_samr_lookup_domain(2540)
> Returning domain sid for domain TEC ->
> S-1-5-21-1064686550-1196878949-2878807255
> [2003/10/29 16:46:03, 3] rpc_server/srv_pipe_hnd.c:free_pipe_context(544)
> free_pipe_context: destroying talloc pool of size 6
> [2003/10/29 16:46:03, 3] smbd/process.c:process_smb(890)
> Transaction 30 of length 164
> [2003/10/29 16:46:03, 3] smbd/process.c:switch_message(685)
> switch message SMBtrans (pid 19763)
> [2003/10/29 16:46:03, 3] smbd/ipc.c:reply_trans(514)
> trans <\PIPE\> data=76 params=0 setup=2
> [2003/10/29 16:46:03, 3] smbd/ipc.c:named_pipe(326)
> named pipe command on <> name
> [2003/10/29 16:46:03, 3] smbd/ipc.c:api_fd_reply(288)
> Got API command 0x26 on pipe "samr" (pnum 740b)free_pipe_context:
> destroying talloc pool of size 0
> [2003/10/29 16:46:03, 3] rpc_server/srv_pipe.c:api_rpcTNP(1495)
> api_rpcTNP: rpc command: SAMR_OPEN_DOMAIN
> [2003/10/29 16:46:03, 3] lib/util_seaccess.c:se_access_check(267)
> [2003/10/29 16:46:03, 3] lib/util_seaccess.c:se_access_check(268)
> se_access_check: user sid is
> S-1-5-21-1064686550-1196878949-2878807255-2004
> se_access_check: also S-1-5-21-1064686550-1196878949-2878807255-2005
> se_access_check: also S-1-1-0
> se_access_check: also S-1-5-2
> se_access_check: also S-1-5-11
> [2003/10/29 16:46:03, 2]
> rpc_server/srv_samr_nt.c:access_check_samr_object(93)
> _samr_open_domain: ACCESS DENIED (requested: 0x00000211)
>
>
> This was before I added smbuser to the ntadmins group. Now after:
>
> [2003/10/30 14:07:39, 2] auth/auth.c:check_ntlm_password(302)
> check_ntlm_password: authentication for user [smbuser] -> [smbuser] ->
> [smbuser] succeeded
> [2003/10/30 14:07:39, 2] lib/access.c:check_access(324)
> Allowed connection from (192.168.0.199)
> [2003/10/30 14:07:40, 2] smbd/server.c:exit_server(558)
> Closing connections
> [2003/10/30 14:07:40, 2] auth/auth.c:check_ntlm_password(302)
> check_ntlm_password: authentication for user [smbuser] -> [smbuser] ->
> [smbuser] succeeded
> [2003/10/30 14:07:40, 2] lib/access.c:check_access(324)
> Allowed connection from (192.168.0.199)
> [2003/10/30 14:07:40, 2]
> rpc_server/srv_samr_nt.c:_samr_lookup_domain(2540)
> Returning domain sid for domain TEC ->
> S-1-5-21-1064686550-1196878949-2878807255
> [2003/10/30 14:07:40, 2]
> rpc_server/srv_samr_nt.c:access_check_samr_function(115)
> _samr_set_userinfo2: ACCESS DENIED (granted: 0x000000b0; required:
> 0x00000024)
> [2003/10/30 14:07:40, 2] smbd/server.c:exit_server(558)
>
> Upon trying a manual net join from the server, with "net join pdc -U
> smbuser" I get:
>
> Create of workstation account failed
> Unable to join domain TEC.
>
> Possibly this could be because the server itself doesn't have a samba
> machine account??
>
> And finally, here's my smb.conf:
>
> # This is the main Samba configuration file. You should read the
> # smb.conf(5) manual page in order to understand the options listed
> # here. Samba has a huge number of configurable options (perhaps too
> # many!) most of which are not shown in this example
> #
> # Any line which starts with a ; (semi-colon) or a # (hash)
> # is a comment and is ignored. In this example we will use a #
> # for commentry and a ; for parts of the config file that you
> # may wish to enable
> #
> # NOTE: Whenever you modify this file you should run the command
> "testparm"
> # to check that you have not made any basic syntactic errors.
> #
> #======================= Global Settings
> =====================================
> [global]
>
> # Logging level controls how much information to log
> log level = 2
>
> # Windows server name
> netbios name = axios
>
> # workgroup = NT-Domain-Name or Workgroup-Name
> workgroup = TEC
>
> # Give clients the correct time
> time server = yes
>
> # server string is the equivalent of the NT Description field
> server string = The Executive Center File Server
>
> # This option is important for security. It allows you to restrict
> # connections to machines which are on your local network. The
> # following example restricts access to two C class networks and
> # the "loopback" interface. For more examples of the syntax see
> # the smb.conf man page
> hosts allow = 192.168.0. 127.
>
> # if you want to automatically load your printer list rather
> # than setting them up individually then you'll need this
> printcap name = /etc/printcap
> load printers = yes
>
> # It should not be necessary to spell out the print system type unless
> # yours is non-standard. Currently supported print systems include:
> # bsd, sysv, plp, lprng, aix, hpux, qnx
> ; printing = bsd
>
> # Uncomment this if you want a guest account, you must add this to
> /etc/passwd
> # otherwise the user "nobody" is used
> ; guest account = pcguest
> guest account = nobody
>
> # this tells Samba to use a separate log file for each machine
> # that connects
> log file = /var/log/samba/log.%m
>
> # Put a capping on the size of the log files (in Kb).
> max log size = 50
>
> # Security mode. Most people will want user level security. See
> # security_level.txt for details.
> security = user
> # Use password server option only with security = server
> ; password server = <NT-Server-Name>
>
> # Password Level allows matching of _n_ characters of the password for
> # all combinations of upper and lower case.
> ; password level = 8
> ; username level = 8
>
> # You may wish to use password encryption. Please read
> # ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
> # Do not enable this option unless you have read those documents
> encrypt passwords = yes
> smb passwd file = /etc/samba/smbpasswd
>
> # The following are needed to allow password changing from Windows to
> # update the Linux system password also.
> # NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
> # NOTE2: You do NOT need these to allow workstations to change only
> # the encrypted SMB passwords. They allow the Unix password
> # to be kept in sync with the SMB password.
> unix password sync = Yes
> passwd program = /usr/bin/passwd %u
> passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n
> *passwd:*all*authentication*tokens*updated*successfu
> lly*
>
> # Unix users can map to different SMB User names
> ; username map = /etc/samba/smbusers
>
> # Using the following line enables you to customise your configuration
> # on a per machine basis. The %m gets replaced with the netbios name
> # of the machine that is connecting
> ; include = /etc/samba/smb.conf.%m
>
> # Most people will find that this option gives better performance.
> # See speed.txt and the manual pages for details
> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
>
> # Configure Samba to use multiple interfaces
> # If you have multiple network interfaces then you must list them
> # here. See the man page for details.
> interfaces = 192.168.0.3/24
>
> # Configure remote browse list synchronisation here
> # request announcement to, or browse list sync from:
> # a specific host or from / to a whole subnet (see below)
> ; remote browse sync = 192.168.3.25 192.168.5.255
> # Cause this host to announce itself to local subnets here
> ; remote announce = 192.168.1.255 192.168.2.44
>
> # Browser Control Options:
> # set local master to no if you don't want Samba to become a master
> # browser on your network. Otherwise the normal election rules apply
> local master = yes
>
> # OS Level determines the precedence of this server in master browser
> # elections. The default value should be reasonable
> os level = 99
>
> # Domain Master specifies Samba to be the Domain Master Browser. This
> # allows Samba to collate browse lists between subnets. Don't use this
> # if you already have a Windows NT domain controller doing this job
> domain master = yes
>
> # Preferred Master causes Samba to force a local browser election on
> startup
> # and gives it a slightly higher chance of winning the election
> preferred master = yes
>
> # Enable this if you want Samba to be a domain logon server for
> # Windows95 workstations.
> domain logons = yes
>
> ;domain admin group = @wheel
>
> # if you enable domain logons then you may want a per-machine or
> # per user logon script
> # run a specific logon batch file per workstation (machine)
> ;logon script = %m.bat
> # run a specific logon batch file per username
> ;logon script = %U.bat
>
> logon drive = h:
> logon home = \\%L\%u\.win_profile\%m
>
> # Where to store roving profiles (only for Win95 and WinNT)
> # %L substitutes for this servers netbios name, %U is username
> # You must uncomment the [Profiles] share below
> logon path = \\%L\Profiles\%u\%m
> ;logon script = logon.bat
>
> # All NetBIOS names must be resolved to IP Addresses
> # 'Name Resolve Order' allows the named resolution mechanism to be
> specified
> # the default order is "host lmhosts wins bcast". "host" means use the
> unix
> # system gethostbyname() function call that will use either /etc/hosts OR
> # DNS or NIS depending on the settings of /etc/host.config,
> /etc/nsswitch.conf
> # and the /etc/resolv.conf file. "host" therefore is system configuration
> # dependant. This parameter is most often of use to prevent DNS lookups
> # in order to resolve NetBIOS names to IP Addresses. Use with care!
> # The example below excludes use of name resolution for machines that are
> NOT
> # on the local network segment
> # - OR - are not deliberately to be known via lmhosts or via WINS.
> ; name resolve order = wins lmhosts bcast
>
> # Windows Internet Name Serving Support Section:
> # WINS Support - Tells the NMBD component of Samba to enable it's WINS
> Server
> ; wins support = yes
>
> # WINS Server - Tells the NMBD components of Samba to be a WINS Client
> # Note: Samba can be either a WINS Server, or a WINS Client, but
> NOT both
> ; wins server = w.x.y.z
>
> # WINS Proxy - Tells Samba to answer name resolution queries on
> # behalf of a non WINS capable client, for this to work there must be
> # at least one WINS Server on the network. The default is NO.
> ; wins proxy = yes
>
> # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
> # via DNS nslookups. The built-in default for versions 1.9.17 is yes,
> # this has been changed in version 1.9.18 to no.
> dns proxy = no
>
> # Case Preservation can be handy - system default is _no_
> # NOTE: These can be set on a per share basis
> ; preserve case = no
> ; short preserve case = no
> # Default case is normally upper case for all DOS files
> ; default case = lower
> # Be very careful with case sensitivity - it can break things!
> ; case sensitive = no
>
> #============================ Share Definitions
> ==============================
> [homes]
> comment = Home Directories
> browseable = no
> writable = yes
>
> # Un-comment the following and create the netlogon directory for Domain
> Logons
> [netlogon]
> comment = Network Logon Service
> path = /home/netlogon
> guest ok = yes
> write list = smbuser
> share modes = no
>
>
> # Un-comment the following to provide a specific roving profile share
> # the default is to use the user's home directory
> [Profiles]
> path = /home/profiles
> browseable = no
> guest ok = yes
> writable = yes
> directory mask = 0700
> create mask = 0600
>
>
> # NOTE: If you have a BSD-style print system there is no need to
> # specifically define each individual printer
> [printers]
> comment = All Printers
> path = /var/spool/samba
> browseable = no
> # Set public = yes to allow user 'guest account' to print
> guest ok = no
> writable = no
> printable = yes
>
> # This one is useful for people to share files
> [tmp]
> comment = Temporary file space
> path = /tmp
> read only = no
> public = yes
> browseable = yes
>
> # A publicly accessible directory, but read only, except for people in
> # the "staff" group
> [public]
> comment = Public Stuff
> path = /home/samba
> public = yes
> read only = yes
> write list = @staff
> browseable = yes
>
> # Other examples.
> #
> # A private printer, usable only by fred. Spool data will be placed in
> fred's
> # home directory. Note that fred must have write access to the spool
> directory,
> # wherever it is.
> <snip rest of commented out examples>
>
> Please help. I've exhausted my resources. I'm never one to post to
> lists--I always find my answer online--but this one has me stumped. I
> can't even figure out how to diagnose the problem, so please: I need
> suggestions. I need to have this network running by tomorrow at the
> latest. I've set up samba networks before, but this one is being a royal
> pain.
>
> Thanks in advance,
> Erich Patrick T Enke (epte)
>
> --
> http://www.fastmail.fm - Same, same, but different
--
http://www.fastmail.fm - A no graphics, no pop-ups email service
More information about the samba
mailing list