From: malmberg@eisner.decus.org
Sent: Wednesday, November 15, 2000 4:39 PM
To: Info-VAX@Mvb.Saic.Com
Subject: Re: SAMBA and VMS

Abstract:

SAMBA is a suite of programs that allow interoperability
with Microsoft file sharing networks.

It consists of a file serving program, a NETBIOS name
serving program, and a command line uitility that allows
a VMS session to read and write files to typically a
Windows file share.  And several other utility programs.

Samba is freeware and covered under the Gnu General Public
License.

In article <8uupel$fuea$1@nntp6.u.washington.edu>,
"Jim Grossnickle" <me@vrwc.org> writes:
> I am trying to find a version of SAMBA that will accept
> encrypted passwords from windows NT and windows 2000
> workstations.

You can try http://eisner.decus.org/~malmberg/samba/ which
also needs http://eisner.decus.org/~malmberg/frontport/

I built and tested these on OpenVMS ALPHA 7.2 and
OpenVMS VAX 7.1.

It is SAMBA 2.0.6.  Windows 2000 may work with it for you
or may need a patch from the SAMBA UNIX site
http://www.samba.org/

The version of SAMBA that fixes a known problem with it
interoperating with Windows 2000 is 2.0.7.

Be aware that no one has given me any feedback since I
announced the kits being posted earlier in the month.

Because this build is almost completely using the UNIX
source code unchanged, it may not take any effort to
update it to SAMBA 2.0.7.

Because I am in the process of relocating, my personal
VMS systems have now been shut off.

> I have two VMS servers one version 6.2 (multinet v 4.2)
> and one version 7.2 (multinet v 4.3).

VAX or Alpha?

I do not know if the binaries at the site will link on OpenVMS 6.2.

I do not know if the source will compile on OpenVMS 6.2 if the
link does not work.

There is nothing supposed to be in the kits to prevent this.
I simply did not have the facilities to test builds on older
versions of VMS than VAX 7.1 and ALPHA 7.2.

Any changes needed should be trivial though.

I also have not tested it on Multinet, and merely copied
what the older version of SAMBA for VMS did.

If you choose to recompile, I would recommend DEC C 6.0 or
higher.

> Previously I have been able to serve files to NT 4.0 by
> making a change to the registry that allowed non-encrypted
> passwords (as required by SAMBA).

> But with windows 2000 and new installs of NT on more
> critical computers I do not want to do that any longer.
> Any help with a SAMBA version number, or configuration
> would be appreciated.

For SAMBA 2.0.6, to use encrypted passwords, you must use
the SMBPASSWD utility to create a database that contains
the encrypted password for each user.

You also must have a guest account on the VMS system.

SAMBA 2.0.6 for VMS also implements Oplocks, and because it
is essentially the UNIX code base, most other features.

I have mainly tested the file serving, and the SMBCLIENT's
ability to transfer files, along with it's ability to send
win-popup messages to Windows systems.

Incoming net send commands directed to a SAMBA VMS server
are converted to Opcom messages by a command file.

Please read the enclosed instructions carefully.  Using the
new oplock features may impact performance.

You may also wish to search the archives of comp.os.vms on
http://www.deja.com for other hints.  I posted one recently
about changing the default to SAMBA to tell it to treat the
lanman file specification as being case sensitive.

This eliminates some processing on SAMBA's part to simulate
a case insensitive file system on a case sensitive one and
VMS always will treat the file name as case insensitive.

And a few programs compiled and linked, but I did not do
any testing on.

One of these is SWAT.  It allows an web browser to
change the SAMBA configuration file.  I have not tested it,
but there is a chance that it will work.

Good Luck
-John
wb8tyw@qsl.network
malmberg@eisner.decus.organization