On Tue, 2004-12-14 at 17:57 -0500, Misty Stanley-Jones wrote: > On Tuesday 14 December 2004 16:57, Ryan Novosielski wrote: > > I do the same thing. I would set your remote browse sync, however, to the > > "other" server. > > > > What I do on my two WINS servers (on different campuses) is: > > > > On server A: > > remote browse sync = serverb.ip.address.here > > On server B: > > remote browse sync = servera.ip.address.here > > I tried this and still it does not work. The funny thing is that tcpdump > does > show me some netbios traffic between the two servers but it doesn't seem to > be the -right- traffic. 'nmblookup' does not work across the subnets for > some reason. I even tried adding a subnet mask of 255.255.0.0 into the > interfaces directive so that the nmb's would listen on both 192.168.1.x and > 192.168.2.x, but still no dice. ---- I set remote browse sync to the 'broadcast' address of the remote network...
i.e. Network A 192.168.0.0/255.255.255.0 broadcast address is 192.168.0.255 Network B 192.168.1.0/255.255.255.0 broadcast address is 192.168.1.255 smb.conf on server on Network A remote browse sync = 192.168.1.255 smb.conf on server on Network B remote browse sync = 192.168.0.255 and lastly, clients are set to use wins server Network A ip.address.of.server.A Network B ip.address.of.server.B and dhcpd of clients sets 'option netbios-node-type 8;' #broadcast Make your changes, shutdown samba, delete wins.dat and restart samba Craig -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
