I'm lookin for help in getting CIFS 1.1 successfully deployed
in a domain trust relationship with an existing Windows PDC emulator
and Windows XP SP3 workstations.
We don't want SAMBA to use the DEFAULT account,
but evidence suggests it is doing just that
and causing my shares access problem:
Extract from samba$smbd_startup.log
$ smbd := $samba$exe:samba$smbd.exe
$
$ SET PROC/DUMP
$ smbd
%SYSTEM-F-USERDISABLED, account is disabled
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
SAMBA$SHR 0 000000000018AF18 00000000001DCF18
SAMBA$SHR 0 0000000000230224 0000000000282224
SAMBA$SHR 0 0000000000499364 00000000004EB364
SAMBA$SHR 0 0000000000499E24 00000000004EBE24
SAMBA$SHR 0 0000000000349484 000000000039B484
SAMBA$SHR 0 0000000000292974 00000000002E4974
SAMBA$SHR 0 0000000000293DA8 00000000002E5DA8
SAMBA$SHR 0 00000000002BB1B4 000000000030D1B4
SAMBA$SHR 0 000000000022E048 0000000000280048
SAMBA$SHR 0 000000000022E490 0000000000280490
SAMBA$SHR 0 000000000022FB48 0000000000281B48
SAMBA$SHR 0 000000000021CB28 000000000026EB28
SAMBA$SMBD 0 00000000000300D4 00000000000300D4
SAMBA$SMBD 0 000000000003006C 000000000003006C
SAMBA$SMBD 0 00000000000303A4 00000000000303A4
0 FFFFFFFF8037DCE4 FFFFFFFF8037DCE4
%TRACE-I-END, end of TRACE stack dump
SAMBA$SMBD job terminated at 25-MAR-2009 13:39:05.12
changing the DEFAULT account to /FLAG=NODISUSER changes the failure to:
$ SET PROC/DUMP
$ smbd
%SYSTEM-F-OPCCUS, opcode reserved to customer fault at PC=FFFFFFFF80FA1A04, PS=0
000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
DECC$SHR_EV56 0 0000000000109A04 FFFFFFFF80FA1A04
SAMBA$SHR 0 0000000000431594 0000000000483594
SAMBA$SHR 0 000000000022FF1C 0000000000281F1C
SAMBA$SHR 0 0000000000499364 00000000004EB364
SAMBA$SHR 0 0000000000499E24 00000000004EBE24
SAMBA$SHR 0 0000000000349484 000000000039B484
SAMBA$SHR 0 0000000000292974 00000000002E4974
SAMBA$SHR 0 0000000000293DA8 00000000002E5DA8
SAMBA$SHR 0 00000000002BB1B4 000000000030D1B4
SAMBA$SHR 0 000000000022E048 0000000000280048
SAMBA$SHR 0 000000000022E490 0000000000280490
SAMBA$SHR 0 000000000022FB48 0000000000281B48
SAMBA$SHR 0 000000000021CB28 000000000026EB28
SAMBA$SMBD 0 00000000000300D4 00000000000300D4
SAMBA$SMBD 0 000000000003006C 000000000003006C
SAMBA$SMBD 0 00000000000303A4 00000000000303A4
0 FFFFFFFF8037DCE4 FFFFFFFF8037DCE4
%TRACE-I-END, end of TRACE stack dump
SAMBA$SMBD job terminated at 25-MAR-2009 15:03:59.50
\\
Product/patch details:
CIFS 1.1 distribution
V/A 8.3 with VMS83A_ACRTL V5.0 and Update V8 applied
TCPIP 5.6 ECO 3
CIFS 1.1 / Samba 3.0.28A test SMB.CONF file:
# Global parameters
[global]
server string = Samba %v running on %h (OpenVMS)
workgroup = WILMA
netbios name = %h
security = DOMAIN
encrypt passwords = Yes
# update encrypted = Yes
name resolve order = lmhosts host wins bcast
# passdb backend = tdbsam
#
# JYC recommended addition
#
# password server = W2K3AD
Password server = *
log file = /samba$log/log.%m
printcap name = /sys$manager/ucx$printcap.dat
guest account = DYMAX
create mask = 0777
print command = print %f/queue=%p/delete/passall/name="""""%s"""""
lprm command = delete/entry=%j
map archive = No
printing = OpenVMS
log level = 10
[S]
comment = Application shared tree and operating system
path = /dym$disk/000000
read only = No
create mask = 0775
guest ok = Yes
[printers]
comment = All Printers
path = /dym$disk/smb_scr
create mask = 0700
guest ok = Yes
printable = Yes
browseable = No
{end}
I'm presuming that I have successfully created a trust relationship
between the SAMBA 3.0.28A test node (DYMC) and the PDC based on this test
on the test node:
$ @samba$root:[bin]samba$define_commands
$ net rpc testjoin
Join to 'WILMA' is OK
Workstation access from RR account is failing to access the test
SAMBA share configured on the test node.
Succeeds from same workstation, same account, same domain and
production Samba node.
Workstation network browse to the test share returns:
My Computer =>
Network Places =>
Entire Network =>
Microsoft Windows Network =>
Wilma =>
Samba 3.0.28a running on Dymc =>
"\\Dymc is not accessible.
You might now have permission to use this network resource.
Contact the administrator of this server to find out if you have access permissions.
The specified network name is no longer available."
$ net usersidlist
returns the following detail for the RR account:
WILMA\rr
S-1-5-21-52566010-122973185-317593308-1412
S-1-1-0
S-1-5-2
S-1-5-11
RR account exists on DYMC:: node
RR account has aligned password on Domain, production and test SAMBA nodes.
DYMC::SYS$SYSDEVICE: is DSA0:
DSa0:[000000] protection is (RWED,RWED,RE,RE)
DSA0:[DYMAX] (RWE,RWE,RWE,RE)
\\
I am successfully using JYC SAMBA 2.2.8-20050817
on a V/A 8.3 w/patches, TCPIP 5.6 ECO 3 in the same environment.
SAMBA 2.2.8 SMB.CONF file:
# Global parameters
[global]
workgroup = WILMA
netbios name = DYMA
security = DOMAIN
encrypt passwords = Yes
update encrypted = Yes
#
# JYC recommended addition
#
Password server = *
log file = /samba_log/log.%m
# deadtime = 10
#
# try reduce re-access time to share after first
# and subsequent timeout
#
# deadtime = 480
deadtime = 4320
printcap name = /sys$manager/ucx$printcap.dat
default service = default
guest account = DYMAX
create mask = 0777
print command = print %f/queue=%p/delete/passall/name="""""%s"""""
lprm command = delete/entry=%j
map archive = No
share modes = No
# max xmit = 8192 #tried with no effect on sigon problem
#
# JYC recommendation (override stat cache = yes default)
#
stat cache = no
[Q]
comment = DYMA ODS-5 data store
path = /$1$DKC200/000000
read only = No
create mask = 0775
guest ok = Yes
share modes = Yes
[R]
comment = select user data
path = /DSA1/000000
read only = No
create mask = 0775
guest ok = Yes
share modes = Yes
[S]
comment = Application shared tree and operating system
path = /dym$disk/000000
read only = No
create mask = 0775
guest ok = Yes
share modes = Yes
[printers]
comment = All Printers
path = /dym$disk/smb_scr
create mask = 0700
guest ok = Yes
printable = Yes
browseable = No
{end}
