Hi all,>With patch 1 of samba 1.9.17, browsing of remote subnets still doesn't >work: Windows 95 still only sees workgroups on the SAMBA server's >local subnet, whereas workgroups on remote subnets are invisible. SAMBA >LMB's on remote subnets only see the DMB's workgroups, not even the >workgroups on the LMB's local subnet :-( The SAMBA WINS server seems >OK, since by knowing the WINS name of a remote computer, we can also >look up its shares (but not its parent workgroup).Been said before. Needs saying again. Samba only supports ONE workgroup! It does not distribute information about any workgroup (to clients or other MBs) about any workgroup except the one in its 'workgroup =' line in smb.conf There was once a Multi Workgroup version of Samba that Luke put together, but I rather think it's dropped out of sight now. Mac Assistant Systems Adminstrator @nibsc.ac.uk mac@nibsc.ac.uk (also [hp]ostmaster) Work: +44 1707 654753 x 285 Everything else: +44 956 237670 (anytime)
With patch 1 of samba 1.9.17, browsing of remote subnets still doesn't work: Windows 95 still only sees workgroups on the SAMBA server's local subnet, whereas workgroups on remote subnets are invisible. SAMBA LMB's on remote subnets only see the DMB's workgroups, not even the workgroups on the LMB's local subnet :-( The SAMBA WINS server seems OK, since by knowing the WINS name of a remote computer, we can also look up its shares (but not its parent workgroup). Ole Holm Nielsen Department of Physics, Building 307 Technical University of Denmark, DK-2800 Lyngby, Denmark E-mail: Ole.H.Nielsen@fysik.dtu.dk WWW URL: http://www.fysik.dtu.dk/persons/ohnielse.html Telephone: (+45) 4525 3187 Telefax: (+45) 4593 2399
ohnielse@fysik.dtu.dk (Ole Holm Nielsen) writes:> With patch 1 of samba 1.9.17, browsing of remote subnets still doesn't > work: Windows 95 still only sees workgroups on the SAMBA server's > local subnet, whereas workgroups on remote subnets are invisible.Here is what I did to enable browsing between workgroups on different subnets. By default each workgroup is isolated in its own subnet. On each subnet there is one domain master for the related workgroup. One SAMBA-client from subnet A is assigned to WORKGROUP_B which is located on subnet B. This SAMBA-client becomes the local browse master for the WORKGROUP_B on subnet A. It is acting as a router for the browsing information of WORKGROUP_B on subnet A. Each of the members of WORKGROUP_A on subnet A should now have the WORKGROUP_B in the browse list. This apparently only works in one direction. WORKGROUP_B on Subnet B is still only seeing the browse list of WORKGROUP_B. You need to add a SAMBA-client on subnet B to WORKGROUP_A to make WORKGROUP_A visible on subnet B. The configuration I am using at the moment consists of three workgroups which are located on three broadcast isolated subnets. I am using a WinNT server as the WINS server and PDC of one workgroup/domain. The two other subnets do not contain WinNT servers only SAMBA/Win3.11/Win95 and WinNT Workstations. SAMBA acts on these two subnets as domain master and WINS proxy. I have no idea what would happen if the WINS server would be replaced by a SAMBA WINS server. Hope this helps, -- ------------------------------------------------------------------ Eckard Koch email : czkec@ocag.ch Contraves Space; W-EE3 ekoch@access.ch Schaffhauserstr 580 Phone : ++41/1/306-3054 CH-8052 Z|rich FAX : ++41/1/306-3750 ------------------------------------------------------------------