As I said http://lists.samba.org/archive/samba-technical/2005- January/039067.html Currently the description for "remote browse sync" in smb.conf(5) is not correct than the real behavior of that parameter. I think document update is needed...
(In reply to comment #0) > As I said http://lists.samba.org/archive/samba-technical/2005- > January/039067.html > Currently the description for "remote browse sync" in smb.conf(5) is not > correct than the real behavior of that parameter. > > I think document update is needed... Please explain what is wrong and how is can be fixed. As a minimum, please explain how we can reproduce the problem. Thanks.
>> As I said http://lists.samba.org/archive/samba-technical/2005- January/039067.html >> >Please explain what is wrong and how is can be fixed. As a minimum, please >explain how we can reproduce the problem. Thanks. Is that not enough to explain what is wrong and how reproduce... And please read the description for "remote browse sync" in smb.conf(5). Currently the behavior is different from that described in smb.conf(5). And I want to know if this difference happens because of miss-documentation or the implementation has been degraded. ----- As far as I examined, "remote browse sync" parameter does not work as described in smb.conf(5). In addition to the description in smb.conf(5), 1) both Samba box must be a **domain** master browse because they need to receive a Master Announcement. 2) both Samba box must be a WINS server because the workgroup name included in received Master Announcement packet must exists in UNICAST_SUBNET. The following smb.conf is a minimum one to work remote browse sync parameter. ----- [global] workgroup = SAMBA01 (should be same atboth Samba box) domain master = Yes wins support = Yes remote browse sync = x.x.x.x (shoube be the other Samba box's IP) enhanced browsing = No (or Yes) ----- At least this behavior differs from that in smb.conf(5). This behavior is by design or a bug? Umm, this parameter is really used ?
(In reply to comment #2) > Currently the behavior is different from that described in smb.conf(5). > And I want to know if this difference happens because of miss-documentation > > or the implementation has been degraded. > > ----- > As far as I examined, "remote browse sync" parameter does not work as > described in smb.conf(5). > > In addition to the description in smb.conf(5), > > 1) both Samba box must be a **domain** master browse because they > need to receive a Master Announcement. > > 2) both Samba box must be a WINS server because the workgroup name > included in received Master Announcement packet must exists in > UNICAST_SUBNET. > > The following smb.conf is a minimum one to work remote browse sync > parameter. > > ----- > [global] > workgroup = SAMBA01 (should be same atboth Samba box) > domain master = Yes > wins support = Yes > remote browse sync = x.x.x.x (shoube be the other Samba box's IP) > enhanced browsing = No (or Yes) > ----- > > At least this behavior differs from that in smb.conf(5). > This behavior is by design or a bug? > > Umm, this parameter is really used ? I am finally getting back to the HOWTO documentation (including man pages). Apologies for the long delay. The remote browse parameter should work without a WINS server. It is not necessary to use the remote browse parameter when there is a central WINS server. I will check and update the man page. - John T.
I have added a notation to the smb.cnf man page entry for the remote browse sync parameter. Thanks for reporting this. - John T.