From: George Watson [watson_g@Encompasserve.org]
Sent: Monday, April 07, 2003 1:45 PM
To: Info-VAX@Mvb.Saic.Com
Subject: Re: SAMBA on VMS... how to make it work.

In article <00A1E08D.2AC0A799@SendSpamHere.ORG>, VAXman-  @SendSpamHere.ORG writes:
>
>I have a process called NMBD and two services have been defined
>called SMBD and SWAT.
>
>When I click on the "neighborhood" I get a "Globe" titled "Entire
>Network".  If I click on the "Globe" I get "pipes" with the title
>"Micr$oft Windows Netowrk".  If I click on the "pipes", I get 3
>PeeCees titles "Workgroup".  If I click on the 3 PeeCees, I get a
>"Workgroup is not accessible/The network name cannot be found"
>window.
>
>The SAMBA stull would appear to be functional.  I get OPCOM mes-
>sages saying:
>INTERnet ACP SMBD Accept Request from Host: 192.168.100.250 Port: 1108
>
>I never see anything connected to the NMBS or SWAT ports.
>

Brian,

  The Network Neighborhood window seems to be the least likely thing
to work in a Samba workgroup.  At home, I have my Alpha networked with my
wife's W98 PC.  If the PC starts up BEFORE Samba, it becomes the browse master
and Net.Nbhd works.  If it comes up AFTER Samba (the usual case, since it
has to be rebooted far more often, of course) Net.Nbhd does not work.  However,
all the services are there and can be accessed.

  I would first use SMBCLIENT from VMS to try browsing for services on the
various systems:

  $ smbclient :== $SAMBA_EXE:smbclient
  $ smbclient "-L" hostname

Start with the VMS system itself, to see if it is serving out what you want 
it to serve, and to double check the workgroup name.  If you have the home 
directory service enabled, it will ask for your password.  It may ask in other 
cases as well.

--
George Watson            watson_g.encompasserve.org.nospam