From: John E. Malmberg [wb8tyw@qsl.net]
Sent: Wednesday, August 02, 2000 11:36 PM
To: Info-VAX@Mvb.Saic.Com
Subject: Re: Can't map to drive with SAMBA

I am also posting it to the SAMBA-VMS mailing list.

The traffic on the SAMBA-VMS mailing list is typically less than 10 messages
a week, so having it manually mirrored to comp.os.vms or
info-vax@mvb.saic.com.remove_spambot_tag should not cause a noticeable
increase in comp.os.vms traffic, and most of the people that think they are
on the SAMBA-VMS list are also on comp.os.vms.

As a reminder, the SAMBA-VMS list server is currently not functioning well
and is in the process of being replaced.  Until that happens, you can not
assume that a post to the SAMBA-VMS list will reach anyone.

To view any responses to the SAMBA-VMS list, they are currently being
archived at http://samba.cadcamlab.org/lists .

In these archives, I found that Gus Bingham has an apparently unanswered
question that seems to be identical to yours.


Now I am running an experimental 2.0.6 version of SAMBA-VMS with encrypted
password support.

I could connect from Windows 95 systems with no problem, but IIRC: I was
getting a similar message from Windows NT clients.

The fix turned in my case was indicated from increasing the debug log level.

Windows NT in my case was requiring a valid guest account to be configured.
For some reason it was connecting as guest first, before logging in as the
user.  If you do not have a guest account configured in your SYSUAF file, it
would fail.

I initially did not have a GUEST account created, as it could be considered
a security issue.  I do not know why SAMBA-VMS needs it, and a Windows NT
server does not.


Also SAMBA-VMS requires that the logical name TMP in the process table be
defined to point to a directory that the any account will have write access
to.  The SAMBA startup files should be doing this already, but if you have
tightened up security on that directory, then the login of the guest account
may fail.

Note that TMP must be in the PROCESS table and any other logical names that
it may point to must be either in the SYSTEM or PROCESS tables.

When SAMBA changes to run under the GUEST or other USER account,

I do not know if this will help you, or may be someone else can give more
tips.

If it does fix your problem, let me know so that I can add it to the FAQ.

You can try enabling a higher debug level for the server process to see if
it will give you some more information.

-John
wb8tyw@qsl.network


"Drew Shelton" <drew@sematech.organization> wrote in message
news:01JSHSEL2246001UZR@SEMATECH.Org...
> I just installed Samba 2.0.3 on OpenVMS Alpha 7.2-1 and
> TCPware 5.4-3.  I'm trying to map from my NT PC to my
> VMS directory.  I get this message on the PC:
>
>         The account is not authorized to login from this station.
>
> My username on my PC is the same as my username on VMS,
> and I'm also using that name for my Samba home.  Here is
> some of my SMB.CONF file:
>
>    security = user
>
> [sheltond]
>     path = /USERS$DISK/SHELTOND
>     valid users = sheltond
>     writeable = true
>
> I've tried it with and without "hosts allow" and "valid users".
> I've also set my PC to use plain text passwords using the file
> NT4_PLAINPASSWORD.REG that was provided with the
> Samba distribution.  TESTPARM complains about the
> permissions on the lock directory, but I understand that's
> a bogus message.
>
> SMBCLIENT connects just fine.  What am I doing wrong?
>
> Forgive me for posting this here.  I tried to subscribe to
> SAMBA-VMS, but I've received no acknowledgement.
>
> Thanks,
> Drew