Re: setting up SAMBA 1.9.17p4

[John E. Malmberg]

Maruyama, Kazutoshi [EMAIL PROTECTED] 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
[EMAIL PROTECTED]
Personal Opinion Only
PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:

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

re: SAMBA 2.2.4 or 2.2.7a and broken pipe

[John E. Malmberg]

From: [EMAIL PROTECTED]
  (Carl Gunnar Linden, MSL Stockholm Sweden.) wrote:
  I am running OpenVMS V7.3 and
  Compaq TCP/IP Services for OpenVMS Alpha Version V5.3 - ECO 1

  I try to run SAMBA 2.2.4 or 2.2.7a. It works with TCPIP V5.3-18 but
 I think it stopped working since I applied the TCPIP_ECO V5.3-181
 patch.
snip
 Has anybody else seen something like this and what is a broken pipe?

A broken pipe indicates a general connection problem.  By it self it is 
not useful to tell you what the problem is.

I would try the nmblookup (OpenVMS), NET VIEW (DOS Command prompt) tests 
to see if you can get information that way.

There is a file diagnostic.txt that should be in the SAMBA distribution 
that describes how isolate some of these problems.  You can get a copy 
of it at http://www.samba.org.

The other thing to do is to increase the error level for the SMBD 
process.  Previous versions of SAMBA allowed this to be done by defining 
a SYSTEM wide logical.

SAMBA 2.0.6 allows the smbd process to be run interactively so that 
these tests can be more easily run.  I do not know if the SAMBA 2.2.x 
branch has this ability.

-John
[EMAIL PROTECTED]
Personal Opinion Only
PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:

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