topic Re: Problem logging to CIFS from Windows client in Operating System - OpenVMS

Problem logging to CIFS from Windows client

Francesco.D — Mon, 14 Jan 2008 17:16:15 GMT

Hi all
I've configured a Samba server (CIFS) Version 1.0 (based on Samba V3.0.24) on an IA64-VMS system.

The following steps are what I've done, as show in the
"HP OpenVMS Common Internet File System (CIFS) Based On Samba - Installation and Configuration Guide" :

1.successfully installed Samba software on OpenVMS Integrity 8.3 OS
2.run samba_setup to configure a Samba server
3.Modified smb.conf as show below

[global]
server string = Samba %v running on %h (OpenVMS)
security = user
passdb backend = tdbsam
domain master = Yes
guest account = SAMBA$GUEST
domain logons = Yes
log level = 2
log file = /samba$root/var/log_%h.%m
create mode = 0755
load printers = no
printing = OpenVMS
workgroup = ISTINET
netbios name = PECSERVER
[pecdir]
comment = Pec Shared Folder
path = /$1$DGA30/DIR$USER/PEC
read only = no
valid users = pec
public = no
create mask = 0664
directory mask = 0775
browsable = Yes
[test]
comment = Test
path = /samba$root/tmp
guest ok = Yes
read only = no
[End of file]

4.Then i tried to add a samba user in this way:

- creating a VMS user, using the following commands

$ MC AUTHORIZE
UAF> COPY SAMBA$TMPLT SMBTEST /UIC=[500,500]/add_identifier

- creating a samba user

$ PDBEDIT -A SMBTEST

- $ samba$root:[bin]@SAMBA$GRANT_GIDUSERS.COM

to grant the identifiers CIFS$_SMBTEST to the users

- then i tried to change password,using:
$ NET RPC PASSWORD

having this error message

Could not connect to server 127.0.0.1
The username or password was not correct.
Connection failed: NT_STATUS_LOGON_FAILURE

I succesfully log on the server through a linux client or smbclient command but i fail using windows client (XP and VISTA).

A log example from a windows machine:

[2008/01/14 16:24:22, 2] SAMBA$SRC:[SOURCE.SMBD]SESSSETUP.C;1:(799)␊
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.␊
[2008/01/14 16:24:22, 2] SAMBA$SRC:[SOURCE.SMBD]SESSSETUP.C;1:(799)␊
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.␊
[2008/01/14 16:24:22, 2] SAMBA$SRC:[SOURCE.AUTH]AUTH.C;1:(317)␊
check_ntlm_password: Authentication for user [dona] -> [dona] FAILED with error NT_STATUS_NO_SUCH_USER␊
[2008/01/14 16:24:22, 2] SAMBA$SRC:[SOURCE.SMBD]SESSSETUP.C;1:(799)␊
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.␊
[2008/01/14 16:24:22, 2] SAMBA$SRC:[SOURCE.SMBD]SESSSETUP.C;1:(799)␊
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.␊
[2008/01/14 16:24:26, 2] SAMBA$SRC:[SOURCE.AUTH]AUTH.C;1:(317)␊
check_ntlm_password: Authentication for user [smbtest] -> [smbtest] FAILED with error NT_STATUS_NO_SUCH_USER␊
[2008/01/14 16:24:27, 2] SAMBA$SRC:[SOURCE.SMBD]SESSSETUP.C;1:(799)␊
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.␊
[2008/01/14 16:24:27, 2] SAMBA$SRC:[SOURCE.SMBD]SESSSETUP.C;1:(799)␊
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.␊
[2008/01/14 16:24:27, 2] SAMBA$SRC:[SOURCE.AUTH]AUTH.C;1:(317)␊
check_ntlm_password: Authentication for user [smbtest] -> [smbtest] FAILED with error NT_STATUS_NO_SUCH_USER␊
[2008/01/14 16:24:27, 2] SAMBA$SRC:[SOURCE.SMBD]SESSSETUP.C;1:(799)␊
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.␊
[2008/01/14 16:24:27, 2] SAMBA$SRC:[SOURCE.SMBD]SESSSETUP.C;1:(799)␊

I Cannot log on to SAMBA server from Windows machines, any suggestion?

Thanks in advance.

Re: Problem logging to CIFS from Windows client

Willem Grooters — Tue, 15 Jan 2008 06:59:26 GMT

I cannot recalll what exactly has to change, hopefully this rings a bell: there are some settings in Windows to allow the system to connect. The same applies to Advanced Server, it has something to do with the authentication mothods that was introduced in XP.

Re: Problem logging to CIFS from Windows client

Karl Rohwedder — Tue, 15 Jan 2008 08:30:25 GMT

There once was a problem with windows encrypting the access information whenaccessing SAMBA or pathworks shares. This as solved by adding the following registry key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters]

"EnablePlainTextPassword"=dword:00000001

regards Kalle

Re: Problem logging to CIFS from Windows client

Francesco.D — Tue, 15 Jan 2008 11:01:08 GMT

i tried adding the registry key but nothing happened.
I think that is an accounting problem (on VMS system) between VMS user and NT user or maybe some issue about the RPC server.

Re: Problem logging to CIFS from Windows client

Wayne Gillan — Tue, 29 Jan 2008 01:50:45 GMT

The enabling of plain text passwords on windows clients is only needed if you have "encrypt passwords = No" in the global section of the smb.conf file. The default is 'Yes' even if the line is not there. Even then you only had to edit the registry for pre windows 95 machines I think. For Windows XP and Vista, navigate to Control Panel -> Administrative Tools -> Local Security Policy -> Security Settings -> Security Options. There will be a policy called "Microsoft network client: Send unencrypted password to third-party SMB servers" which you can enable.

To change the samba password for your SMBTEST user, why not use the smbpasswd utility? While you are logged in with SMBTEST:

$ @samba$root:[bin]samba$define_commands
$ smbpasswd
New SMB password:
Retype new SMB password:

The net rpc password is used to change passwords on remote servers:

$ net --server= rpc password
Password:
Enter new password for :

I also had a lot of trouble getting XP and Vista to 'see' the samba server. The only way to get it working in the end was to access the SWAT (http://your_server:901/) page on each client machine first. After that it worked fine. I'm yet to figure out why.

Cheers,
Wayne