CIFS on OpenVMS 8.3 Alpha

[eNet]

I'm trying to get CIFS running on an Alpha with OpenVMS 8.3. I've tried both the 1.0 and the 1.1 CIFS distributions.

First problem is I can't find the CRTL on the ECO ftp site. There is an ACRTL, but I'm thinking that is not the same. So if anyone can help me find the CRTL needed for CIFS and OpenVMS 8.3, I think that may be a a big bit part of the problem...

So, here's my symptom...

It installs ok. It starts up ok, but I can not get it to authenticate against the PDC or use guest.

Most of the utilities in the samba$root:[bin.alpha] folder crash when I try to run them. That's why I think this may be the CRTL problem.

I just need to share one folder that is read/write to everyone from my Windows workstations.

So, I setup SMB.CONF to make this a member server. I can browse and see the Alpha machine's Samba... banner from a Windows XP workstation when browse through network neighborhood.

When I click on it, it prompts me for a login name and password but I can't go anywhere past that.

I don't want the user to have to authenticate each time, so a guest access with one folder that is read/writeable would be perfect.

Or if I can get it to authenticate against the Windows 2003 based PDC, that would be fine as well.

Can anyone provide some insight in how to setup smb.conf to do this? And can someone point me in the direction of the correct CRTL for 8.3?

Any help would be greatly appreciated.

Thanks!

[Steven Schweda]

> First problem is I can't find the CRTL on
> the ECO ftp site. There is an ACRTL, but
> I'm thinking that is not the same.

Not the same as _what_? Which "an ACRTL" are
you looking at? Where? (My psychic powers
are weak.)

> Most of the utilities in the
> samba$root:[bin.alpha] folder crash when I
> try to run them.

Define "crash". Describe "try to run them".

> And can someone point me in the direction
> of the correct CRTL for 8.3?

I'd expect the product documentation to list
the product's requirements. In general, I'd
expect the latest UPDATE kit to deal with
most known problems.

[EdgarZamora_1]

The latest Alpha C RTL is VMS83A_ACRTL-V0400. You can download it individually or download the latest update kit, VMS83A_UPDATE-V0700, which also includes the RTL.

[eNet]

Steven:

> Not the same as _what_? Which "an ACRTL"
> are you looking at? Where? (My psychic
> powers are weak.)

The ACRTL may not be the same as the CRTL ECO the instructions refer to.

The ACRTL ECO that I installed is VMS83A_ACRTL-V0400.ZIPEXE from ftp://ftp.itrc.hp.com/openvms_patches/alpha/V8.3/



> Define "crash". Describe "try to run them".

crash definition:

$ run samba$smbstatus
%SYSTEM-F, access violation, reason mask=00, virtual address=0000000000000000, P
C=00000000001C6CCC, PS=0000001B
%TRACE-F, symbolic stack dump follows
image module routine line rel PC abs PC
SAMBA$SHR 0 0000000000174CCC 00000000001C6CCC
SAMBA$SHR 0 00000000002625C8 00000000002B45C8
SAMBA$SHR 0 000000000031F438 0000000000371438
SAMBA$SHR 0 000000000019A10C 00000000001EC10C
SAMBA$SHR 0 0000000000261E6C 00000000002B3E6C
SAMBA$SHR 0 00000000003095CC 000000000035B5CC
SAMBA$SMBSTATUS 0 00000000000300D4 00000000000300D4
SAMBA$SMBSTATUS 0 000000000003006C 000000000003006C
SAMBA$SMBSTATUS 0 0000000000030394 0000000000030394
0 FFFFFFFF80385CE4 FFFFFFFF80385CE4
%TRACE-I, end of TRACE stack dump
$



> I'd expect the product documentation to
> list the product's requirements. In
> general, I'd expect the latest UPDATE kit > to deal with most known problems.

And you are correct, the documentation does. It says that it requires OpenVMS 8.2 or 8.3 and the latest CRTL ECO.

[eNet]

Edgar:

Thanks for your reply. I do have both of those kits installed, so if that is the latest CRTL ECO, then I'm good on the CRTL ECO requirement.

Any other thoughts?

Thanks!

[EdgarZamora_1]

Please post your SMB.CONF file.

[eNet]

I've tried various combinations of parameters. My current config is:


$ type smb.conf
[global]
server string = Samba %v running on %h (OpenVMS)
netbios name = %h
security = domain
workgroup = CMPS
local master = no
password server = 192.168.1.5
passdb backend = tdbsam
domain master = no
guest account = SAMBA$GUEST
guest only = no
domain logons = no
log file = /samba$root/var/log_%h.%m
create mode = 0755
load printers = no
printing = OpenVMS

[pccommon]
comment = PCCOMMON Folder
path = /samba$root/pccommon
browseable = yes
available = yes
public = yes
writeable = yes
read only = no
create mode = 0755
guest ok = yes
$

[Kris Clippeleyr]

Hi,
Regarding the CRTL ECO kits...
The ones mentioned in the CIFS V1.1 documentation are stil NOT available (I'm also waiting for them). Therefor I still haven't installed the V1.1 kit, and still working with a patched V1.0 kit (on OpenVMS I64 only, not on Alpha).
Regarding the issue of prompting for a password...
Did the Alpha "join the domain" correctly?
I.e. did the command

NET RPC JOIN "-S" "-U%"

succeed?
(where NET := $SAMBA$ROOT:[BIN.ALPHA]SAMBA$NET.EXE ; should be an "administrator" account known to the PDC).

It also might help to stop Samba on the Alpha, clear out the SAMBA$ROOT:[VAR] directory (and subdirectories), join the domain, and start Samba.

Hope this helps,
Kris (aka Qkcl)

[Robert Atkinson]

I recently (couple of weeks ago) installed and configured SAMBA on our test node :-

------------------------------------ ----------- ----------- --- -----------
PRODUCT KIT TYPE OPERATION VAL DATE
------------------------------------ ----------- ----------- --- -----------
HP AXPVMS SAMBA V1.1 Full LP Install Val 20-OCT-2008
DEC AXPVMS VMS83A_ACMELDAP V2.0 Patch Install Val 20-OCT-2008
DEC AXPVMS VMS83A_ACRTL V4.0 Patch Install Val 20-OCT-2008
DEC AXPVMS VMS83A_UPDATE V7.0 Patch Install Val 20-OCT-2008
DEC AXPVMS VMS83A_PCSI V2.0 Patch Install Val 20-OCT-2008


This is an Alpha ES40 running 8.3 to a Windows 2K3 PDC.

It took a bit of fiddling, especially creating the directory shares, but it does seem to be stable.

Rob.

[Robert Atkinson]

Config file :-

# Samba config file created using SWAT
# from 192.168.241.205 (192.168.241.205)
# Date: 2008/10/20 16:49:44

[global]
workgroup = UKVISTA
server string = Samba %v running on %h (OpenVMS)
security = DOMAIN
username map = /samba$root/lib/username.map
log file = /samba$root/var/log_%h.%m
load printers = No
os level = 65
preferred master = No
domain master = No
admin users = cifsadmin
create mask = 0755

[homes]
comment = Home Directories
read only = No
create mask = 0750
vms ods5 volume = Yes

[raa]
comment = RAA Home Directory
path = /dga150/hg
read only = No
create mask = 0750
vms ods5 volume = Yes

[test1]
comment = Test Directory
path = $1$dga150:[hg]
vms ods5 volume = Yes
create mask = 0750
read only = No

[Willem Grooters]

That rings a bell. IIRC, SMB.conf chould contain a line

os level = 65

to note a VMS system, and that line seems missing in your definition

[EdgarZamora_1]

Here is my working SMB.CONF file. I only have one share and it's used for transferring log files.

I noticed I don't have the "os level = 65" as others have mentioned, but the config still works. I have windows and linux boxes dumping logs into the share.

CLCC1> ty smb.conf
[global]
server string = Samba %v running on %h (OpenVMS)
netbios name = %h
security = user
passdb backend = tdbsam
domain master = no
guest account = SAMBA$GUEST
domain logons = no
log file = /samba$root/var/log_%h.%m
create mode = 0755
load printers = no
printing = OpenVMS

[homes]
comment = Home Directories
browseable = no
read only = no
create mode = 0750

[samba_xfer]
browsable = yes
writeable = yes
public = no
valid users = samba_xfer
vfs objects = varvfc
path = /sys$users/samba_xfer


Do you have your host account created, identifiers granted, and also an entry into the tdbsam created (using pdbedit)?

[Richard Jordan]

CIFS V1.0 had a problem with using some log levels (the SMB.CONF setting that determines the verbosity of command and logfile output that would cause some programs to accvio. I do not know if that was fixed in V1.1.

Some commands let you set the log level (debug) on the command line; you might try adding a

-d2

qualifier to see if that is the problem. If it is, try putting this line in your SMB.CONF

log level = 2

and restart, see if it makes a difference. I believe the default is '3' which had problems, and if my memory is correct '4' also had the same issue. Values 0-2 and 5-10 worked ok.

[eNet]

William,

I just tried the OS LEVEL = 65 and that did not resolve it.


Edgar,

PDBEDIT is one of the utilities that is giving me the ACCVIO crash when I tried to do a "pdbedit -a testuser". I do have the account created using the template.

So, my current obstacle is trying to figure out what is causing the ACCVIO. I do have the testuser account created in UAF with the samba template settings, but not with PDBEDIT. So that's the one I'm trying to figure out right now.


Richard,

I currently have the log level at 10 so I'm getting all kinds of debug info. I'll try a couple of different log levels to see if I can generate a different response.


Thanks for the help everyone! It is greatly appreciated!

[EdgarZamora_1]

What account are you using to run the utilities? Is there a matching rights identifier for it? Post your UAF entry if you can. I found this tidbit which might be causing your problem:

4.8 CIFS Utilities Crash

Executing HP CIFS utilities such as PDBEDIT from a user
account that does not match the Rights Identifier results
in a crash.

Workaround:

There is no workaround. HP will address this problem in a
future release of CIFS.

[EdgarZamora_1]

Bingo! Problem duplicated...

CLCC1> mc authorize
UAF> remove/id ezamora
%UAF-I-RDBREMMSGU, identifier EZAMORA value [000200,003642] removed from rights
database
UAF> Exit
%UAF-I-NOMODS, no modifications made to system authorization file
%UAF-I-NAFNOMODS, no modifications made to network proxy database
%UAF-I-RDBDONEMSG, rights database modified
CLCC1> set host 0

CLCC1 - Test System

Username: ezamora
Password:



Last interactive login on Thursday, 6-NOV-2008 07:38:34.88
Last non-interactive login on Wednesday, 5-NOV-2008 08:10:10.34
%GNU_STARTUP-I-SETTING_UP, setting up Emacs version 21.2
CLCC1> @samba$root:[bin]samba$define_commands
CLCC1> pdbedit "-L"
getgid: getpwuid() failed, errno: 0
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000000
0000, PC=00000000001D96BC, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
SAMBA$SHR 0 00000000001876BC 00000000001D96BC
SAMBA$SHR 0 000000000022B764 000000000027D764
SAMBA$SHR 0 0000000000492BA4 00000000004E4BA4
SAMBA$SHR 0 00000000004934B4 00000000004E54B4
SAMBA$SHR 0 00000000001D7804 0000000000229804
SAMBA$SHR 0 00000000001DDAE8 000000000022FAE8
SAMBA$SHR 0 00000000001ECF24 000000000023EF24
SAMBA$SHR 0 00000000001D3E9C 0000000000225E9C
SAMBA$PDBEDIT 0 00000000000300D4 00000000000300D4
SAMBA$PDBEDIT 0 000000000003006C 000000000003006C
SAMBA$PDBEDIT 0 00000000000303A4 00000000000303A4
0 FFFFFFFF80385CE4 FFFFFFFF80385CE4
%TRACE-I-END, end of TRACE stack dump
CLCC1>