NETWORK DRIVE ACCESS PROBLEM WITH SAMBA/ALPHA/OPEN VMS From a PC with W2K or W98

[jpseck]

NETWORK DRIVE ACCESS PROBLEM WITH SAMBA/ALPHA/OPEN VMS From a PC with W2K or W98

Conditions :

The SAMBA SERVER :
	ALPHA / OpenVMS V6.2
	SAMBA-2_0_3-VMS0-BIN_ALPHA
	Digital TCP/IP Services for OpenVMS Alpha Version V4.2 - ECO 3
	on a AlphaServer 2100 4/200 running OpenVMS V6.2

	With :

	UCX> sh service smbd/full

	Service: SMBD
                           State:     Enabled
	Port:              139     Protocol:  TCP             Address:  0.0.0.0
	Inactivity:          5     User_name: SYSTEM          Process:  SMBD
	Limit:           10000     Active:      1             Peak:       2

	File:         SAMBA_ROOT:[BIN]SMBD_STARTUP.COM
	Flags:        Listen

	Socket Opts:  Rcheck Scheck
	 Receive:            0     Send:               0

	Log Opts:     Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
	 File:        SAMBA_ROOT:[VAR]SMBD_STARTUP.LOG

	Security
	 Reject msg:  not defined
	 Accept host: 0.0.0.0
	 Accept netw: 0.0.0.0

I have created the following Alpha Open VMS username accounts

dry  :  with 1 password and sys$sysdevice:[dry] for VMS directory
	and [mgm] pointing on the directory sys$sysdevice:[mgm] as Samba user private resource in the smb.conf file.

dry1  : with 1 password and sys$sysdevice:[mgm1] for VMS directory
	and [mgm1] pointing on the directory sys$sysdevice:[mgm1] as Samba user private resource in the smb.conf file.

dry2  : with 1 password and sys$sysdevice:[mgm2] for VMS directory
	and [mgm2] pointing on the directory sys$sysdevice:[mgm2] as Samba user private resource in the smb.conf file.

dry3  : with 1 password and sys$sysdevice:[mgm3] for VMS directory
	and [mgm3] pointing on the directory sys$sysdevice:[mgm3] as Samba user private resource in the smb.conf file.

dry4  : with 1 password and sys$sysdevice:[mgm4] for VMS directory
	and [mgm4] pointing on the directory sys$sysdevice:[mgm3] as Samba user private resource in the smb.conf file.

All these VMS username accounts have the same parameters, except they differ by they UIC, password, directory!

I also have created and additional public Samba resource :

[public] pointing on the directory sys$sysdevice:[public] as Samba user private resource in the smb.conf file.

For a all these users VMS directories i give full access (for system, owner, group and world).

The PROBLEM :

When i attempt to connect to the created Samba resources i always  have the following results :

net use  E: \\SAMBASVR\dry  + password  >>> OK
net use  F: \\SAMBASVR\dry1  + password  >>> OK
net use  G: \\SAMBASVR\dry2  + password  >>> OK
net use  H: \\SAMBASVR\dry3  + password  >>> OK
net use  I: \\SAMBASVR\dry  + password  >>> OK
net use  D: \\SAMBASVR\public  >>> OK

and :

net use  J: \\SAMBASVR\dry  + password  >>> OK
net use  K: \\SAMBASVR\dry1  + password  >>> OK
net use  L: \\SAMBASVR\dry2  + password  >>> OK
net use  M: \\SAMBASVR\dry3  + password  >>> OK
net use  N: \\SAMBASVR\dry  + password  >>> OK


BUT  when i attempt to map any network drive letter to dry4 as :

net use  P: \\SAMBASVR\dry4 + password >>>> It will give me the following message :