Running Samba 2.0.6 on Alpha VMS

[Fachetti, Robert]

VMS Samba Users,

I am new to running Samba, but not to VMS. I have recently installed Samba
2.0.6 on my system (OpenVMS 7.1/UCX V4.2 - ECO 3) which appears to be
working properly only if I set "security = SHARE". If I set "security =
USER" and "encrypt passwords = yes"  then attempt to connect to a service
from my PC client (NT 4.0 networked with all the approriate bells and
whistles) I get the following error:

C:\>net use l: \\cpu93944\homes
The password is invalid for \\cpu93944\homes.

Type the password for \\cpu93944\homes:
System error 86 has occurred.

The specified network password is not correct.

Also, when "encrypt passwords = yes"  I cannot connect locally to any
service:

$ smbclient //cpu93944/homes "-U" fachetti%passwd
added interface ip=10.10.64.112 bcast=10.10.255.255 nmask=255.255.0.0
session setup failed: ERRSRV - ERRbadpw (Bad password - name/password pair
in a
Tree Connect or Session Setup are invalid.)

If I set "encrypt passwords = No"  then I can successfully connect locally:

$ smbclient //cpu93944/homes "-U" fachetti%passwd
added interface ip=xx.xx.xx.xxx bcast=10.10.255.255 nmask=255.255.0.0
Domain=[EHPLANT] OS=[Unix] Server=[Samba 2.0.6]

smb: \>

but still not from my PC:

C:\>net use l: \\cpu93944\homes
The password is invalid for \\cpu93944\homes.

Type the password for \\cpu93944\homes:
System error 1240 has occurred.

The account is not authorized to login from this station.

Can anyone help point me in the right direction?

Thanks in advance,
Bob Fachetti
fachetti at pweh.com

-----Original Message-----
From: John E. Malmberg [mailto:wb8tyw at qsl.net]
Sent: Wednesday, November 28, 2001 12:08 AM
To: samba-vms at lists.samba.org
Subject: Re: Running Samba 2.0.6 on Alpha VMS


J Beets <jbeets at cnd.co.newzealand>

> 
> Hello John/ other VMS Samba users,
> 
> Thanks for your help. I had upgraded to Samba 2.0.6 from 2.0.3 hoping it 
> would help but you're right - all the versions of Samba are affected
including 
> 2.0.6
> 
> Adding /FLAGS=LISTEN stopped smbd crashing on start up.
> 
> I now have one remaining error in the smb.log file - can you help?


> (I have no printers on the VMS server)
> 
> [2001/11/27 09:11:24, 1] 
> CMS_ROOT:[SAMBA.SOURCE.SMBD]SERVER.C;2:(643) 
>   smbd version 2.0.6 started. 
>   Copyright Andrew Tridgell 1992-1998 
> [2001/11/27 09:11:25, 0] 
> CMS_ROOT:[SAMBA.SOURCE.PARAM]LOADPARM.C;2:(1797) 
>   No path in service printers - using /tmp 
> [2001/11/27 09:11:26, 0] 
> CMS_ROOT:[SAMBA_VMS.SOURCE.LIB]UTIL_SID.C;1:(262) 
>   string_to_sid: Sid  does not start with 'S-'. 
> [2001/11/27 09:11:26, 0] 
> CMS_ROOT:[SAMBA_VMS.SOURCE.PASSDB]PASSDB.C;1:(812) 
>   unable to generate machine SID. 
> [2001/11/27 09:11:26, 0] 
> CMS_ROOT:[SAMBA_VMS.SOURCE.PASSDB]PASSDB.C;1:(872) 
>   unable to read file SAMBA_ROOT/VAR/PRIVATE/MACHINE.SID. Error was 
> can't assign  requested address  
> [2001/11/27 09:11:26, 0] 
> CMS_ROOT:[SAMBA.SOURCE.SMBD]SERVER.C;2:(677) 
>   ERROR: Samba cannot create a SAM SID. 
> 
> Is this a privilege problem? Samba was installed under the System
username.
> The smb.conf file is currently the default with only the workgroup name 
> changed and [tmp] enabled


The MACHINE.SID from SAMBA 2.0.3 can not be parsed by SAMBA 2.0.6.
If you delete the MACHINE.SID, Samba will recreate it, and all should be
well.

-John
wb8tyw at qsl.network
Personal Opinion Only

 
> http://lists.samba.org/listinfo/samba-vms
> 
> 
> End of samba-vms Digest
>