setting up SAMBA 1.9.17p4

[Maruyama, Kazutoshi]

Thanks John for advice. 

I am using OpenVMS V6.2 and DIGITAL TCP/IP Services for OpenVMS VAX Version
V4.2 - ECO 2. 

I tried to install SAMBA 2.0.6 before, but I could not install. Because, I
got the install error during the frontport installation. 

After this I decided to use 1.9.17p4, so I can sucessfuly install it. 

If SAMBA 2.0.7 can be installed and worked with OpenVMS V6.2 and DIGITAL
TCP/IP Services for OpenVMS VAX Version V4.2 - ECO 2.
(Upgrade of the OS is not possible due to the current operation of our
system.) 

I will install it. Please let me know the location of kit. I have never find
the SAMBA 2.0.7 kit so. 


-Kazu

-----Original Message-----
From: John E. Malmberg [mailto:wb8tyw at qsl.net]
Sent: Sunday, March 02, 2003 2:34 AM
To: samba-vms at lists.samba.org
Subject: Re: setting up SAMBA 1.9.17p4


Maruyama, Kazutoshi" <Kazutoshi.Maruyama at japan.pfizer.company> wrote:
> Hello,
> 
> I have a question. 
> I am try to setting up SAMBA 1.9.17p4. 
> (I am using OpenVMS 6.2, so I guess I cannot use the other samba version.)
> My windows cliant is Windows 2000.

As I pointed out in my previous message, for that to work, you really 
need SAMBA 2.0.7 to work, even for the UNIX versions of SAMBA.

Otherwise you will have no communications or intermittant communication 
problems.  This is a protocol negotiation error that was fixed in SAMBA 
2.0.7.

> I have no luck  to accessing VAX directory from Windows 2000. 
> 
> Please give me some suggetion. 

Encypted passwords must be disabled in the client, otherwise look at my 
previous message that was posted to the list just before yours came out.

Some people have been able to get Windows 2000 and early SAMBA to work. 
  The bug in the protocol incompatablility seems to hit some people and 
not others.

> I assume that there is somehow I can see the directory from Windows 2000.
>  
> When I see the error log from LOG.SMB;1,  I got the message below.
> Anybody knows how to fix the problem. 
> 
> ** vms_file: no filespec available
> ** vms_stat: st = -1, mode = 001402
>              size = 1476395086 

Can you do the steps in diagnostic.txt to make sure that you can connect 
locally?  If you do not have a copy of diagnostic.txt, a copy can be 
obtained from http://www.samba.org.

> 
> =======orginal===============
> Processing section "[homes]"
> doing parameter comment = Home Directories
> doing parameter browseable = yes
> doing parameter guest ok = yes
> doing parameter path = /sys$sysdevice2
> doing parameter create mode = 0750
> pm_process() returned Yes
> adding IPC service
> == vms_file: file_spec: ""
>                      -> ""
> ** vms_file: no filespec available
> ** vms_stat: st = -1, mode = 001402
>              size = 1476395086

This looks like the user account used for access did not have access to 
one or more of the directories required to complete the login or access 
the file.

On my post that immediately preceded yours, I reference a FAQ that I 
wrote that should give you many other tips.

-John
wb8tyw at qsl.network
Personal Opinion Only


PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:

http://www.tuxedo.org/~esr/faqs/smart-questions.html