Problem connecting to samba-2.0.3/vms

[georges.bert at Lafarge-Ciments.Lafarge.com]

Hello,

I have successfully installed SAMBA-2.0.3 on a VAX running VMS-6.2 and TCPWARE-5.4-3 (this VAX's name is CLFTS2).

I installed the same SAMBA-2.0.3 on another VAX (name = CLF10U) ... but now I'm not able to get the smbd working correctly on this new VAX.

I've found the following behaviours :

A. Using smbclient, I can get a response from the old VAX (CLFT2).
   Example :
     10U_SY $ mc samba_exe:smbclient "-L" clfts2 "-N"
     Added interface ip=192.168.10.1 bcast=192.168.10.255 nmask=255.255.255.0
     Domain=[CLFTS2_D] OS=[OpenVMS] Server=[Samba 2.0.3]

             Sharename      Type      Comment
             ---------      ----      -------
             public         Disk      Partage
             test           Disk      Test
             IPC$           IPC       IPC Service (Samba-2.0.3/VMS)

             Server               Comment
             ---------            -------

             Workgroup            Master
             ---------            -------
             AUTOMATION           S_DEVEL
             CLF02S_D             S01ARM
             CLFTS2_D             CLFTS2_SMB
             IDFBFRTCP01M         LGS-OPF700JDNMD
             LAFCIM               LCSIE01
             LCJDE                LCJDE00
     10U_SY $

B. Using smbclient, I can't get a positive response from the new VAX (CLF10U).
   Example :
     10U_SY $ mc samba_exe:smbclient "-L" clf10u "-N"
     Added interface ip=192.168.10.1 bcast=192.168.10.255 nmask=255.255.255.0
     session request to CLF10U failed
     session request to *SMBSERVER failed
     10U_SY $


Following are several files that may give some information:

tcpware:NETCP.LOG
-----------------
  ...
  ** 26-JUN-2002 13:38:52 TCP connection established on _BG1009: from 192.168.10.1,1546 to
  192.168.10.1,139.
     Created process SMBD_151 (00002080) to service _BG1009:
  ** 26-JUN-2002 13:38:55 TCP connection established on _BG1017: from 192.168.10.1,1547 to
  192.168.10.1,139.
     Created process SMBD_152 (00002081) to service _BG1017:
  ** 26-JUN-2002 13:38:55 Server process 00002080 exited with status.
     %C-E-NOMSG, Message number 1035A00A
  ** 26-JUN-2002 13:38:58 Server process 00002081 exited with status.
     %C-E-NOMSG, Message number 1035A00A

samba_root:[000000]LOG.SMB
--------------------------
  ...
  [2002/06/26 13:38:55, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
    WARNING: no chroot!
  [2002/06/26 13:38:55, 0] DSA1:[KITS.SAMBA-2_0_3.SOURCE.SMBD]OPLOCK.C;1:(79)
    open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was
   can't assign requested address
  [2002/06/26 13:38:57, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
    WARNING: no chroot!
  [2002/06/26 13:38:57, 0] DSA1:[KITS.SAMBA-2_0_3.SOURCE.SMBD]OPLOCK.C;1:(79)
    open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was
   can't assign requested address

samba_root:[LIB]SMB.CONF
------------------------
  [global]
    workgroup = CLF10U_D
    netbios name = clf10u_smb
    server string = Samba-%v/VMS
    log file = /samba_log/log.%m
    security = user
    max log size = 50
    dns proxy = no
    preferred master = no
    encrypt passwords = no
    guest account = SAMBA$GUEST
    map to guest = bad user
    dead time = 10
    map archive = no
    share modes = no
    socket options = TCP_NODELAY

  [A1MWIN]
    comment = *** supprime ***
    path = /clf10u$dka200/pcsa.softspc/a1mwin
    guest ok = no

  [APPROU11]
    path = /clf10u$dka300/pcsax/approu11
    guest ok = no

  [AUDITU11]
    comment = INVENTAIRE PARC MATERIEL LAN AUDITOR
    path = /clf10u$dka300/pcsax/auditu11
    guest ok = yes
    writeable = yes
  ...

Note: at the present time, both VAXes are still running PATHWORKS (via DECnet only).

At this point I'm not able to go further analyzing the problem. If someone has an idea ...

Thanks in advance,                     Georges


"This e-mail is confidential and may contain legally privileged information.  If you are not the intended recipient, you should not copy, distribute,
disclose or use the information it contains.  Please e-mail the sender immediately and delete this message from your system.  E-mails are susceptible
to corruption, interception and unauthorised amendment; we do not accept liability for any such changes, or for their consequences. You should be
aware, that the company  may monitor your emails and their content"