From: malmberg@eisner.decus.org Sent: Monday, January 08, 2001 5:02 PM To: Info-VAX@Mvb.Saic.Com Subject: Re: samba In article <93c74r$96a6@eccws12.dearborn.ford.company>, "Carlo Mussche" writes: > hello, > > I have installed samba version 2.0.3 on a Alpha VMS 7.1 > but everytime I want to map (from my NT-station) to a drive, > I get the message (after supplying the correct password : > > "the network name cannot be found" That message can indicate many different problems. > how can I solve this? Samba 2.0.3 for OpenVMS does not support encrytped passwords clients connecting to it. There is a registry patch that if it is not with your distribution kit can be obtained from one of the mirrors of http://www.samba.org. If you need to run with encryted passwords, then you must convert to using SAMBA 2.0.6 for OpenVMS. In my observations on using Windows NT clients to connect to SAMBA 2.0.6 shares, the NT client would attempt to log into the VMS system through an special pipe that SAMBA seems to map to the SAMBA GUEST account. If the SAMBA GUEST account does not exist, then SAMBA server will request that the NT client ask for a password for that special pipe. Only after it gets the password, will it attempt to find it special pipe name in the VMS account database. Since there is no corresponding VMS account when the SAMBA GUEST account does not exist, there is no correct password for you to supply. The result will be that the NT client will have failed validation and not be allowed to see a list of "network names". As I have never actually run SAMBA 2.0.3 for OpenVMS, I would have to refer you to the documentation that was with it for creating the SAMBA guest account for it. For SAMBA 2.0.6 for OpenVMS, the name of the SAMBA Guest account defaults to "SAMBA__GUEST" (two underscores preceding GUEST). SAMBA 2.0.6 for VMS seems to currently require OpenVMS 7.x because of some issues with the FRONTPORT library. The download locations for it are: http:\\eisner.decus.org\~malmberg\samba\ and it requires: http:\\eisner.decus.org\~malmberg\frontport\ Because of differences in the way that the two ports were done, and the differences in capabilities, some of the setup and configurations are different. Read the installation and release notes carefully. -John wb8tyw@qsl.network Representing only my own opinion