We have 2 segments of the corporate network, which are connected by a unstable(~90% uptime) 2Mbps link. This link cannot be made better. So, we are to use 2 WINS servers(both Samba 2.2.8a) - one server in one segment. However, if 2 clients register on 2 different WINS servers, they can't mount network drives of each other. I've tried to use the WINS servers as primary and secondary for all clients, so most of the time all clients register on the same server (primary). However, if a Windows2000-based computer boots when the link is down it registers on the WINS server, which can be connected to; but doesn't return to the primary server when the link is up. I know only one solution of it - use WINS replication, but Samba 2.2.8a still doesn't support it. Why - are any other solutions? Probably the MS WINS replication protocol is hard to be reverse-engeneered, but I'd like to use replication at least between 2 Samba's, no MS Windows! I'm always ready to test such a thing! Here are some "bad" solutions I found on the list archives: 1. Use Windows WINS servers in both segments. (Pff, I hate to use Windows as a server!) 2. Use only one WINS server in both segments (What will happen when the link is down?!)
What about having two samba boxes, one running as a wins proxy and the other as wins server? You could use a tool to check the link avaliability (there are some of them already) with a tool, and when the link is download, you can stop samba and restart it with a different configuration file (and with this file the server would be a wins server). Hey, I never tried this. Is just an idea, and I don?t know if it will work. --- Michael Smirnov <smbsmb@mail.ru> escreveu: > We have 2 segments of the corporate network,> which are connected by a unstable(~90% uptime) 2Mbps > link. > This link cannot be made better. > So, we are to use 2 WINS servers(both Samba 2.2.8a) > - one server in one segment. > However, if 2 clients register on 2 different WINS > servers, > they can't mount network drives of each other. > I've tried to use the WINS servers as primary and > secondary > for all clients, so most of the time all clients > register > on the same server (primary). > > However, if a Windows2000-based computer boots when > the link is down > it registers on the WINS server, which can be > connected to; > but doesn't return to the primary server when the > link is up. > > I know only one solution of it - use WINS > replication, > but Samba 2.2.8a still doesn't support it. > Why - are any other solutions? > > Probably the MS WINS replication protocol is hard to > be reverse-engeneered, > but I'd like to use replication at least between 2 > Samba's, no MS Windows! > I'm always ready to test such a thing! > > Here are some "bad" solutions I found on the list > archives: > 1. Use Windows WINS servers in both segments. > (Pff, I hate to use Windows as a server!) > 2. Use only one WINS server in both segments > (What will happen when the link is down?!) > > > > > -- > To unsubscribe from this list go to the following > URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba_______________________________________________________________________ Yahoo! Mail Mais espa?o, mais seguran?a e gratuito: caixa postal de 6MB, antiv?rus, prote??o contra spam. http://br.mail.yahoo.com/
> We have 2 segments of the corporate network, > which are connected by a unstable(~90% uptime) 2Mbps link. > This link cannot be made better.Just a silly idea don't know even if it works: If you are in control of the link how about messing with the wins.dat file? When the link gets up you exchange/merge wins.dat files from both servers and restart nmbds... For example all machines in one net are called with a distinctive a_ in name so you grep in b network in the wins.dat file and replace all a_ entries with the new ones. Same for the other wins.dat for hosts named b_whatever.
> > Just a silly idea don't know even if it works: If you are > in control > > of the link how about messing with the wins.dat file? When the link > > gets up you exchange/merge wins.dat files from both servers and > > restart nmbds... For example all machines in one net are > called with a > > distinctive a_ in name so you grep in b network in the > wins.dat file > > and replace all a_ entries with the new ones. Same for the other > > wins.dat for hosts named b_whatever. > > > wins.dat has simple format, > so it's possible to detect fi any machines are registered on > a secondary WINS server, replace/add this data to the primary > WINS server's wins.dat,The idea is not to add to the primary but also to bring back the data FROM the primary to the secondary. A more elegant approach will be to detect the link is down and DELETE from secondary the "missing" primary machines! There seems to be one aspect you're missing: the damn browse list! IMO You'll have to change that too.> and kill&start nmbd (because I don't > know how to make it reread wins.dat).Oh, that was a problem for me too.> > Will this work?Exactly my point Michael: why don't you try and tell us? ;-) Long ago I had problems with a stupid NT server refusing to register himself at the wins... Without being rebooted; So all I did was to alter the wins.dat file "by hand"... It worked back then it was samba 2.2.0 or smth. I think it *should* work but someone has to try and bring back the knowledge...