LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 10-23-2007, 11:41 PM   #1
Astol
Member
 
Registered: Aug 2007
Location: Perth, Australia
Distribution: RHEL 5 + 4.5, Fedora
Posts: 88

Rep: Reputation: 15
Samba PDC Login Problems


ok guys, i have posted before but to no avail. i have some updated info for you though. i know this is a long post, but please please help. i have been working on this for the last 2 weeks.

i have 2 Linux servers, the PDC is RHEL5 (we will call this server1), BDC 4.5 (server2).

here is some background info:

smb.conf from server1

Code:
# 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
#
# For a step to step guide on installing, configuring and using samba, 
# read the Samba-HOWTO-Collection. This may be obtained from:
#  http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
#
# Many working examples of smb.conf files can be found in the 
# Samba-Guide which is generated daily and can be downloaded from: 
#  http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# 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]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = blah

# server string is the equivalent of the NT Description field
   server string = server1

# Security mode. Defines in which mode Samba will operate. Possible 
# values are share, user, server, domain and ads. Most people will want 
# user level security. See the Samba-HOWTO-Collection for details.
   security = user

# 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.1. 192.168.2. 127.

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
;   load printers = yes

# you may wish to override the location of the printcap file
;   printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
;   printcap name = lpstat

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
;   printing = cups

# This option tells cups that the data has already been rasterized
;cups options = raw

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
  guest account = guest

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/%m.log

# Put a capping on the size of the log files (in Kb).
   max log size = 50

# Use password server option only with security = server
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *
;   password server = <NT-Server-Name>

# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
;   realm = MY_REALM

# Backend to store user information in. New installations should 
# use either tdbsam or ldapsam. smbpasswd is available for backwards 
# compatibility. tdbsam requires no further configuration.
;   passdb backend = tdbsam

# 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.
# Note: Consider carefully the location in the configuration file of
#       this line.  The included file is read at that point.
;   include = /usr/local/samba/lib/smb.conf.%m

# 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.12.2/24 192.168.13.2/24 

# 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 = 200

# 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

# 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

# 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

# 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 = no

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
   dns proxy = no 

# These scripts are used on a domain controller or stand-alone 
# machine to add or delete corresponding unix accounts
;  add user script = /usr/sbin/useradd %u
;  add group script = /usr/sbin/groupadd %g
;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
;  delete user script = /usr/sbin/userdel %u
;  delete user from group script = /usr/sbin/deluser %u %g
;  delete group script = /usr/sbin/groupdel %g

smb ports = 137 138 139 445
preserve case = yes
short preserve case = yes
case sensitive = no
deadtime = 15
keepalive = 1
socket options = TCP_NODELAY IPTOS_LOWDELAY
encrypt passwords = yes


#============================ Share Definitions ==============================
[homes]
   comment = Home Directories
   browseable = yes
   writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
 [netlogon]
   comment = Network Logon Service
   path = /etc/samba/netlogon
   guest ok = yes
   browsable = yes
   writable = yes
   

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
[Profiles]
    path = /etc/samba/profiles
    browseable = yes
    guest ok = yes
    writable = yes
    level2 oplocks = yes
    dos filetimes = yes

# NOTE: If you have a BSD-style print system there is no need to 
# specifically define each individual printer
;[printers]
;   comment = All Printers
;   path = /usr/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

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   writable = yes
;   printable = no
;   write list = @staff

# 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.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765
you will notice that i have opened up all the shares fully, this is so that i can be sure its not a share problem.

the directory listing of my /etc/samba:
Code:
[root@server1 samba]# ll
total 88
-rw-r--r-- 1 root root   20 May 12 01:09 lmhosts
-rw-r--r-- 1 root root   20 May 12 01:10 lmhosts.rpmnew
drwxrwxrwx 2 root root 4096 Oct 23 16:03 netlogon
drwxrwxrwx 2 root root 4096 Oct 23 16:03 profiles
-rw------- 1 root root 8192 Oct 19 09:19 schannel_store.tdb
-rw------- 1 root root 8192 Oct 19 08:55 secrets.tdb
-rw-r--r-- 1 root root 9989 Oct 24 11:58 smb.conf
-rw-r--r-- 1 root root 9991 Oct 24 11:53 smb.conf~
-rwxr--r-- 1 root root 4220 Oct 19 09:13 smb.conf.bak
-rw-r--r-- 1 root root 9957 Oct 23 15:20 smb.conf.bak1
-rw------- 1 root root  631 Oct 24 11:53 smbpasswd
-rw------- 1 root root  424 Oct 23 16:19 smbpasswd~
-rw-r--r-- 1 root root   97 Oct 23 13:31 smbusers
[root@server1 samba]#
again, i have given "Profiles" and "Netlogon" full 777 permissions.

Code:
[root@server1 samba]# smbclient -L //localhost/ -Uroot%rootpassword
Domain=[BLAH] OS=[Unix] Server=[Samba 3.0.23c-2.el5.2.0.2]

        Sharename       Type      Comment
        ---------       ----      -------
        homes           Disk      Home Directories
        netlogon        Disk      Network Logon Service
        Profiles        Disk      
        tmp             Disk      Temporary file space
        IPC$            IPC       IPC Service (serv01)
        root            Disk      Home Directories
Domain=[BLAH] OS=[Unix] Server=[Samba 3.0.23c-2.el5.2.0.2]

        Server               Comment
        ---------            -------
        PC1                  
        SERVER1               server1
        SERVER2               server2

        Workgroup            Master
        ---------            -------
        BLAH              SERVER1
[root@server1 samba]#
testparm:
Code:
[root@server1 samba]# testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[netlogon]"
Processing section "[Profiles]"
Processing section "[tmp]"
Loaded services file OK.
Server role: ROLE_DOMAIN_PDC
Press enter to see a dump of your service definitions

[global]
        workgroup = BLAH
        server string = server1
        guest account = guest
        log file = /var/log/samba/%m.log
        max log size = 50
        smb ports = 137 138 139 445
        deadtime = 15
        keepalive = 1
        socket options = TCP_NODELAY IPTOS_LOWDELAY
        logon path = \\%L\Profiles\%U
        domain logons = Yes
        os level = 200
        preferred master = Yes
        domain master = Yes
        dns proxy = No
        wins support = Yes
        hosts allow = 192.168.1., 192.168.2., 127.
        case sensitive = No

[homes]
        comment = Home Directories
        read only = No

[netlogon]
        comment = Network Logon Service
        path = /etc/samba/netlogon
        read only = No
        guest ok = Yes

[Profiles]
        path = /etc/samba/profiles
        read only = No
        guest ok = Yes

[tmp]
        comment = Temporary file space
        path = /tmp
        read only = No
        guest ok = Yes
[root@server1 samba]#
smbpasswd extract:
Code:
[root@server1 samba]# cat smbpasswd
administrator
root
vaiouser
pc1$
guest
[root@server1 samba]#
now of course, this has detail after the entries, but im not gonna post that.
FYI, PC1$ is a client (a laptop), with username vaiouser

passwd extract:
Code:
pc1$:x:503:503::/dev/null:/bin/false
vaiouser:x:504:504::/home/vaiouser:/bin/bash
NOTE: root also has a samba account


this is how i add machines (i do it manually, just out of habit. plus it seems the automatic one doesnt work all the time):
[code]
useradd -d /dev/null -s /bin/false machine\$
passwd machine\$
smbpasswd -a -m machine
{/code]

and add user:
Code:
useradd user
passwd user
smbpasswd -a user

NOW FOR THE ERRORS:

pc1$.log extract:
Code:
[2007/10/24 11:30:32, 0] rpc_server/srv_netlog_nt.c:_net_auth_2(478)
  _net_auth2: creds_server_check failed. Rejecting auth request from client PC1 machine account PC1$
error when logging into XP client
Code:
Windows cannot contact the domain. the domain controller is down or otherwise unavailable, or because your computer account was not found. please try again later. if this error continues, contact your administrator for assistance.
error from client's event viewer:
Code:
This computer could not authenticate with \\SERVER1, a Windows domain controller for domain BLAH, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator.
NOTE: the XP client is using WINS and is pointing to server1, i have been looking at various forums etc, which suggested turning off a bunch of local security policies and registry options, which i have done. if you need these, i can track them down, but it will be a pain.

i CAN ping the client from server1 and vice versa.

start > run > \\server1 (on client machine) asks for username and password (i supplied root credentials), and it gave me a list of shares available.

i DO have "print services for UNIX etc" enabled under add/remove windows components

i have tried removing and readding the client user and machine names

there is no IPTABLES or SELinux or any other firewall running on the server1

there is no external firewall program installed on client, and windows firewall is turned off as a service (administrative tools > services > windows firewall/ICS > disabled + stopped)

and no, not all of the info provided is accurate (i.e., the workgropu name, server names etc, but i have been careful in editing these.)

and here is a kitchen sink.

please help!!!

Last edited by Astol; 10-23-2007 at 11:46 PM. Reason: add more info
 
Old 12-26-2007, 07:29 PM   #2
paul_mat
Member
 
Registered: Nov 2004
Location: Townsville, Australia
Distribution: Fedora Core 5, CentOS 4, RHEL 4
Posts: 855

Rep: Reputation: 30
you might want to follow this how-to, it might be able to help you out.

http://www.opensourcehowto.org/how-t...plication.html
 
Old 12-26-2007, 07:56 PM   #3
jschiwal
LQ Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 682Reputation: 682Reputation: 682Reputation: 682Reputation: 682Reputation: 682
You should only run one wins server. Which XP client is this, XP home or XP pro? XP home can't log into domains. Using the /etc/samba/smbpasswd file for storing account information, you need to run smbpasswd to enter this user in the smbpasswd file and enter the password. The user needs to have a corresponding account on the Linux machine. With the [Profile] share that should be the case.

Either your samba installation or a samba-doc package will supply a couple very useful books "Samba 3 by Example" and "Samba 3 HOWTO and Reference Guide". The former will take you step by step through the process of setting up sample network configurations. The latter has a chapter setting up a standalone Domain controller which you may want to look at.

With two domain controllers, you need a way to migrate the account information from smbpasswd on one server to the other.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
samba PDC and linux client login teo Linux - Networking 1 09-06-2012 05:48 AM
login error on samba pdc ferradura Linux - Networking 1 09-27-2007 11:53 PM
SuSE 9.2 PDC login problem (SAMBA) sane Linux - Software 4 06-09-2005 06:31 PM
Canīt login on a domain setted up with samba 3 as pdc! emilioestevezz Linux - Networking 2 05-06-2004 04:04 AM
Non-Root login on Samba 3 PDC jmoutdoors Linux - Networking 0 10-30-2003 09:40 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 06:36 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration