Samba 2.0.3 on OpenVMS

Dr. Guilherme Regis lgemedia at 200-171-183-182.dsl.telesp.net.br
Thu Nov 7 00:09:54 GMT 2002


Hi again, Samba experts:

I found out that NMBD Samba 2.0.3 VAX/VMS, version file:

    SAMBA-2_0_3-VMS0-BIN_VAX.ZIP;1

does not read the network *routing* information from the Multinet 
setups correctly.

My network configuration is, in brief:

           Machine/OS             NETBIOS name  Samba Version
--------------------------------  ------------  ------------- 
VAXstation 4000/60 OpenVMS 6.2     VAXSTATION    2.0.3  VMS
Pentium III 600 RedHat Linux 6.2   NOSTROMO      2.0.10 LINUX

Workgroup name for VAXSTATION (bsuhep.cp.bsu.edu) is SNATCHER.
Workgroup name for NOSTROMO (nostromo.physics.bsu.edu) is BSUHEP.

Using smbclient and nmblookup on VAX, it has reported *wrong* BCAST 
and NMASK, and Domain SNATCHER *never* shows up. BCAST should be
10.87.16.255 and MCAST=255.255.255.0 as seen from the Linux side.

For instance, on VAX:
BSUHEP::SYSTEM> smbclient "-L" nostromo.physics
Added interface ip=10.87.16.252 bcast=10.255.255.255 nmask=255.0.0.0
Password: Domain=[BSUHEP] OS=[Unix] Server=[Samba 2.0.10]

        Sharename      Type      Comment
        ---------      ----      -------
        IPC$           IPC       IPC Service (nostromo server Samba2.0.10)
        debianjet      Printer   lp3
        lp2            Printer   
        deskjet        Printer   hp
        oberjet        Printer   lp4
        lp1            Printer   
        lp5            Printer   

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

        Workgroup            Master
        ---------            -------
        BSUHEP               NOSTROMO
        MSHOME               DCV5GX11
        SCIFAIR              CUTIVATE
        WORKGROUP            A-DHPF4QC7528O0

However, VAX Multinet parameters are correct, as follows:

BSUHEP::SYSTEM> mu show/interface
_Network Device: se0
Device se0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST>
            IP Address = 10.87.16.252
            IP Sub-Net Mask = 255.255.255.0
            IP Broadcast Address = 10.87.16.255

Now, issuing the nmblookup command, I found out that it can not find
neither VAXSTATION nor NOSTROMO:

BSUHEP::SYSTEM> nmblookup vaxstation
Sending queries to 10.255.255.255
name_query failed to find name vaxstation

BSUHEP::SYSTEM> nmblookup bsuhep.cp.bsu.edu
Sending queries to 10.255.255.255
name_query failed to find name bsuhep.cp.bsu.edu

BSUHEP::SYSTEM> nmblookup nostromo.physics.bsu.edu
Sending queries to 10.255.255.255
name_query failed to find name nostromo.physics.bsu.edu

Nevertheless, using "-B" option, NMBD is now able to find these 
machines:

BSUHEP::SYSTEM> nmblookup "-B" 10.87.16.255 vaxstation
Sending queries to 10.87.16.255
10.87.16.252 vaxstation<00>
10.87.16.252 vaxstation<00>

BSUHEP::SYSTEM> nmblookup "-B" 10.87.16.255 nostromo  
Sending queries to 10.87.16.255
10.87.16.254 nostromo<00>

In fact, I decided to include the following line in the smb.conf:

	interfaces = se0 10.87.16.252/255.255.255.0

that is, the VAXSTATION IP number and its netmask.

After rebooting the system and issuing the smbclient command,
VAXSTATION is finally listed under SNATCHER workgroup, as follows:

BSUHEP::SYSTEM> smbclient "-L" nostromo 
Added interface ip=0.0.0.0 bcast=0.255.255.255 nmask=255.0.0.0
Added interface ip=10.87.16.252 bcast=10.87.16.255 nmask=255.255.255.0
Got a positive name query response from 10.87.16.254 ( 10.87.16.254 )
Password: Domain=[BSUHEP] OS=[Unix] Server=[Samba 2.0.10]

        Sharename      Type      Comment
        ---------      ----      -------
        IPC$           IPC       IPC Service (nostromo Samba2.0.10)
        debianjet      Printer   lp3
        lp2            Printer   
        deskjet        Printer   hp
        oberjet        Printer   lp4
        lp1            Printer   
        lp5            Printer   

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

        Workgroup            Master
        ---------            -------
        BSUHEP               NOSTROMO
        MSHOME               DCV5GX11
        SCIFAIR              CUTIVATE
        SNATCHER             VAXSTATION      <---<<<
        WORKGROUP            A-DHPF4QC7528O0

However, nmblookup command is still *unable* to grab the correct
BCAST number and find the machines:

BSUHEP::SYSTEM> nmblookup vaxstation
Sending queries to 0.255.255.255
name_query failed to find name vaxstation

BSUHEP::SYSTEM> nmblookup nostromo  
Sending queries to 0.255.255.255
name_query failed to find name nostromo

Any ideas here ?

Furthermore, I still have problems to log in as GUEST.

BSUHEP::SYSTEM> smbclient "-L" vaxstation
Added interface ip=0.0.0.0 bcast=0.255.255.255 nmask=255.0.0.0
Added interface ip=10.87.16.252 bcast=10.87.16.255 nmask=255.255.255.0
Got a positive name query response from 10.87.16.252 ( 10.87.16.252 )
Got a positive name query response from 10.87.16.252 ( 10.87.16.252 )
Password: 
  ???

Nothing happens here. Guest's directory and file protections are W:RE

I wonder if it might be related somehow to the following error:
    personal login command procedure does not use 'F$VERIFY(0)'

reported by the multinet check command:

BSUHEP::SYSTEM> multinet check   
MultiNet Checkout Utility V3.3(24)
%MNCHK-I-SYLOGVRFY, system login command procedure does not use'F$VERIFY(0)
%MNCHK-I-LOGVRFY, personal login command procedure does not use'F$VERIFY(0)
%MNCHK-W-GATEUNREACH, gateway 10.87.16.1 (route to 0.0.0.0 on interface
se0) not reachable
%MNCHK-S-ALLOK, all tests passed

For some reason, Multinet reports a gateway not reachable, but all 
connections, other than SAMBA, are working fine.

Why can't NMBD/SMBD grab, correctly, the BCAST information from Multinet?

I appreciate any help or comments on these problems.

Many thanks in advance,
  Luiz Guilherme Regis







More information about the samba-vms mailing list