PDA

View Full Version : domain controller could not be contacted using samba 3 with solaris 10


leo1
July 27th, 2006, 16:40
Hi, when I try to connect with a Windows XP Professional workstation to my domain (My Computer->Computer Name ...), I keep getting the error message "A domain controller for the domain ... could not be contacted". This attempt leaves no traces in the samba logs.
I have applied the recommended WinXP registry tweaks. I am pretty shure that I have typed the domain name right. nmdb is running on the samba server.Strange enough, I can connect to the samba server if I enter its IP directly in I have add the samba server's IP address to the wins entry in the network configuration and reboot afterwards. I also switched on "enable netbios over TCP/IP".
My smb.conf look like:

#======================= Global Settings
[global]
smb passwd file = /etc/sfw/smbpasswd
map to guest = bad user
encrypt passwords = yes
netbios name = imdfs
default = netlogon
domain admin group = root @adm,+students,+accademic,fragidis,mardiris
client code page = 737
character set = iso8859-7

# workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4
workgroup = IMD
# server string is the equivalent of the NT Description field
server string = IMD File Server
# 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 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
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
debug timestamp = yes
log file = /var/log/samba/x%U-%m.log
log level = 3
# Put a capping on the size of the log files (in Kb).
max log size = 9216
# 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:/etc/sfw/smbpasswd
# 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/sfw/lib/smb.conf.%m
# Most people will find that this option gives better performance.
# See the chapter 'Samba performance issues' in the Samba HOWTO Collection
# and the manual pages for details.
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE 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.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 = 33
# 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\profile (file://\\%L\Profiles\%U\profile)
# 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 = 10.1.15.252
# 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 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
;add user script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false -M %u
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
path = /export/home/%U
browseable = yes
writable = yes
valid users = %S
create mode = 0600
directory mode = 0700

# Un-comment the following and create the netlogon directory for Domain Logons
[netlogon]
comment = Network Logon Service
path = /usr/sfw/lib/netlogon
guest ok = yes
writable = no
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 = /export/home
browseable = yes
guest ok = yes
writable = 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 = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes


I have no idea what else to try....
Help please!

Alex Railean
July 28th, 2006, 09:20
Hmm, I need to get a better picture:
- does this happen with every Windows XP computer on the network?
- has this been happening all the time, or after a certain action?
- which version of Logon are you using?
- are you absolutely sure that the network connection itself is functional?

leo1
July 28th, 2006, 09:58
Alex thank for your reply! This happens for all computers of the labs and at all times. I am pretty sure that my network connection is fine because from the same computer that I am trying to declare into the domain I can easily explrore my files to the server through windows file manager using servers name or its ip address.
Previously I was using Samba 2 and my server was a Reb Hat Linux 9. Now I am using a sun server and Solaris 10 with Samba 3.0.10.
Thanks in advance..

Alex Railean
July 28th, 2006, 10:06
Which version of Logon do you use?

leo1
July 28th, 2006, 10:41
What do you mean by that and how can I find out tyhe version of log on I use?

Alex Railean
August 1st, 2006, 12:16
I asked about your version of Logon - a tool that replaces the standard Windows logon procedure with a secure one. Our company develops this program and I assumed that your question was about Logon not working properly in your environment, but it seems that your question referrs to a general setup.


Hmm, if so, then I guess you should use a network sniffer and listen to the dialog between the client and the server. See whether the client sends the required commands to the server. If the sniffer reveals that there is no traffic between the client and the server, the problem is in the connection. If they do communicate with each other, examine the contents of the packets and see if the request is formed properly. If everything is fine, then it's definitely a problem on the server (it receives the request but handles it incorrectly).

I am not a *NIX guru, so I can't provide any other tips at the moment.