It seems to be working for us now. I have the following relevant settings in the [global] section of smb.conf ... remote announce = 199.170.245.255/ENGINEER 199.170.224.255/ENGINEER 199.170.232.255/ENGINEER workgroup = ENGINEER wins support = no wins server = 199.170.224.6 domain master = yes local master = yes preferred master = yes ; os level = 0 don't want Samba to win master browser elections ; os level = 2 should allow samba to be the Master Browser ; over even local 95 and NT machines (see BROWSING.txt) ; os level = 33 should allow samba to be the Master Browser ; over even NTAS (which uses 32; see BROWSING.txt) os level = 33 I'm not sure if the 'remote announce' is necessary if all our PCs are pointing to the correct WINS server (199.170.224.6) in their WINS configuration (I believe most, if not all do refer to the correct address WINS server). But I'm hesitant to take it out since it's working now, and it did not seem to work well without it. I have no control over our NTAS WINS server, so it's possible that it was not keeping track of master browsers correctly when I originally wrote this email (maybe it still doesn't, but that machine is in a different group here at our work, so it's hard for me to tell). In any case, in theory the above settings should work for you WITHOUT the 'remote announce' line above if you have a working WINS server (change it to the correct IP address for your organization). That is, you should be able to browse a workgroup from a PC and see hosts from more than just your local subnet. Another issue I considered when I was having problems was the amount of time it took to resolve elections and update browse lists and so on. When I was experimenting, I may have been changing smb.conf and restarting nmbd too frequently. You may want to give it 10 minutes to settle between changes. Does anyone have a good idea how long things like that (elections, browse list updates, etc.) might take? How long should I have to wait to decide that a certain smb.conf setup works or does not work with respect to network browsing? Wajihuddin Ahmed wrote at 18:45 +0500 on Feb 23: > Hi: > > Did you find a solution to your problem? If so i'll be interested in > it. > > Thx > > --- > > ohn E Hein (jhein@fallschurch.esys.com) > Sat, 20 Dec 1997 05:14:31 +1100 > > Messages sorted by: [ date ][ thread ][ subject ][ author ] > Next message: Matthew Harrell: "Couldn't register domain?" > Previous message: Martin.Wunderli@jungle.ch: "Re: about Samba and > NT" > > I have 2 subnets. Subnet 1 has an NT WINS server. Subnet 2 has a > Samba > server acting as domain master browser and local master browser > for a workgroup. > > If I view the network neighborhood from a Win 95 PC on Subnet 1 > (call it PC_A), I can see all the hosts in the workgroup on both > subnets. > > If I view the network neighborhood from a Win 95 PC on Subnet 2 > (call it PC_B), I cannot see PC_A. I CAN 'map a network drive' on > PC_B > for a directory that has been shared by PC_A. > > Both PCs are in the same workgroup (which happens to be the same > workgroup as the Samba server). > > What might be the reason(s) that I can map a network drive of > a PC, but cannot see it in the network neighborhood? > > > > -- > Wajihuddin Ahmed | EMAIL: wajih.ahmed@isb.worldwerx.com.pk > WorldWerx, Pakistan | Ph/Fax: +92-51-282192 > >
Hi all, My situation: I have a samba server on one subnet which is currently very happy serving Win 95/98 clients on the same subnet. I have to allow several Win 95/98 clients on a seperate subnet the ability to use & browse the samba server's shares. Reading through BROWSING.txt has led me to believe the following should be done: (i) The Samba server should be the Domain Master Browser (and the only one for the workgroup) (ii) The Samba server should be the local master browser for its subnet (iii) On each subsequent subnet there should be a local master browser which uses the Domain Master Browser as its WINS server (so that it can send its browse list to the Samba server) My smb.conf contains the following: [snip] wins support = yes domain master = yes local master = yes preferred master = yes remote announce = 129.78.179.255 129.78.153.255/CST [snip] By my understanding this smb.conf allows for the Samba server to meet the first two requirements stated above. The remote announce line contains the subnet that the Samba server is within, and the additional subnet that will have clients requiring browsing access to the Samba box. Now I have to setup a local master browser for the additional subnet. This is to be a Win 95/98 machine. Providing I've understood BROWSING.txt correctly (i.e. my config of the Samba box is correct) this is the only real step I have to worry about now. My real question then is "how do I configure a Win 95/98 machine to act as a local master browser in a subnet?" Thanks in advance, John ==================================================================John Twyman | Computer Systems Officer | Faculty of Science | College of Sciences & Technology | Room 207/210 | Email: J.Twyman@cst.usyd.edu.au Carslaw Building, F07 | Phone: +61 2 9351 5453 University of Sydney NSW 2006 | Fax: +61 2 9351 5467 ===================================================================
John, On Mon, 30 Nov 1998 14:27:12 +1100, John Twyman wrote:>I have a samba server on one subnet which is currently very happy serving >Win 95/98 clients on the same subnet. I have to allow several Win 95/98 >clients on a seperate subnet the ability to use & browse the samba server's >shares.>My smb.conf contains the following:>wins support = yes >domain master = yes >local master = yes >preferred master = yes >remote announce = 129.78.179.255 129.78.153.255/CSTAre you sure this will work? AFAIK these are broadcasts and probably will not cross the router between your subnets. I would prefer to direct the remote announces directly to the browse master in the remote subnet. Hasta la vista, Robert -- --------------------------------------------------------------- Robert.Dahlem@frankfurt.netsurf.de Radio Bornheim - 2:2461/332@fidonet +49-69-4930830 (ZyX, V34) 2:2461/326@fidonet +49-69-94414444 (ISDN X.75) ---------------------------------------------------------------
Hey guys, I have two subnets, 192.168.5.0/24 and 192.168.0.0/24. Each subnet has one Samba server and few Windows 9x clients. The first subnet has its samba server acting as the Master Domain Browser(192.168.5.100/24). This subnet's samaba box also has wins support set to yes, and of course all machines on both networks is using the wins server. The samaba server on the other subnet(192.168.0.2/24) is configured to be the Local Master Broswer for its network.(192.168.0.0/24). This box is has wins server=192.168.5.100. My problem is broswe list syncing is only working in one direction. The 192.168.0.0/24 LMB includes all local machines as well as the other subnet, 192.168.5.0/24 which contains the DOmain master browser. _BUT_, the 192.168.5.0/24 network doesn't have have broswe list for the 192.168.0.0/24 network. I read BROWSING.txt and Browsing-config.txt several times. I have my debug level set to 7 on both samba boxes. Couldn't find a clue there. Here is the smb.conf from both machines. Note: I left out the shares info. =======================192.168.5.100: /usr/local/samba/lib/smb.conf =======================[global] security=user netbios name=OlafServer workgroup=workgroup encrypt passwords=yes invalid users=root debug level=7 os level=34 null passwords=yes domain master=yes local master=yes preferred master=yes remote announce=192.168.0.2 remote browse sync=192.168.0.2 wins support=yes hosts allow=192.168.5.0/255.255.255.0 192.168.0.0/255.255.255.0 64.244.3.240/255.255.255.248 127.0.0.1 interfaces=192.168.5.100/24 127.0.0.1 64.244.3.245/255.255.255.248 bind interfaces only=yes < shares snipped > ==============192.168.0.0: /usr/local/samba/lib/smb.conf ===============[global] security=server netbios name=whosyourdaddy workgroup=workgroup encrypt passwords=yes invalid users=root debug level=7 os level=34 null passwords=no hosts allow=192.168.0.0/255.255.255.0 192.168.5.0/255.255.255.0 hosts deny=0.0.0.0 interfaces=192.168.0.0/24 bind interfaces only=yes invalid users=root deadtime=0 socket options=TCP_NODELAY local master=yes preferred master=yes remote announce=192.168.5.100 remote browse sync=192.168.5.100 domain logons=yes valid users=steve angie downstairs konrad logon script=AllUsers.bat time server=yes wins server=192.168.5.100 # Global printer options printer driver file=/usr/local/samba/printer$/printers.def <shares info snipped> Note: These networks are routed using VPN gateways. All protocols above IP seem to work. VPN connection shouldn't be my problem. Thanks for any help guys. Steve Maroney
I am trying to get cross subnet browsing working, could someone confirm if it is possible to do this using different workgroup names on each subnet? (Each subnet is actually set up as a separate domain, all the machines across both subnets point to one WINS server, but the browse lists are not being propagated) Thanks Simon
I've also noticed I'm getting the following errors in log.nmbd if that helps anyone diagnose my problem. [2002/05/25 19:59:01, 0] nmbd/nmbd_browsesync.c:get_domain_master_name_node_status_fail(509) get_domain_master_name_node_status_fail: Doing a node status request to the domain master browser at IP 192.168.4.1 failed. Cannot get workgroup name. Cheers Simon> -----Original Message----- > From: Simon Hodgson > Sent: 25 May 2002 15:56 > To: samba@lists.samba.org > Subject: Cross subnet browsing > > > I am trying to get cross subnet browsing working, could someone > confirm if it is possible to do this using different workgroup > names on each subnet? > > (Each subnet is actually set up as a separate domain, all the > machines across both subnets point to one WINS server, but the > browse lists are not being propagated) > > Thanks > > Simon