Rudolf Kollien
1999-Oct-12 17:04 UTC
Client not cleared from browslist with browse list sync
Hello everybody, I use 2 samba servers. Server A (SA) is connected to networks n1 and n2. It is the wins server and the domain controller with domain logons and used as password server. Server B (SB) is connected to networks n2 and n3. As diagram it looks like this: +---n2-----(SA)----n1--+ | (SB) | +-------n3---+ Server B's smb.conf has: ... time server = yes domain master = no local master = yes preferred master = no wins server = <addr. of SA> security = SERVER password server = SA interfaces = <addr. of nic1>/255.255.255.240 <addr. of nic2>/24 remote announce = <n2>.255/WORKGROUP remote browse sync = <addr. of SA> ... On Server A it looks like: ... time server = yes domain master = yes local master = yes preferred master = yes domain logons = yes wins support = yes interfaces = <addr. of nic1>/24 <addr. of <nic2>/24 remote announce = <n1>.255/WORKGROUP <n2>.255/WORKGROUP ... Now when a client logs on to Server B the client is added to the browselist of Server B and after a short time he's synced to Server A. So i can see all clients and servers on Server A and B. As the client logs off he is removed from the browselist of Server B but he remains in the browselist of Server A forever. Did i missunderstand the behavor of the "remote browse sync"? All i want is, that all active clients/servers can be browsed and accessed using the network neighbarhood. Can anyone help? Thanks in advance. Rudolf Rudolf Kollien email: Rudolf.Kollien@medas.de ********************************************************* Never trust a operating system you have no sources for ********************************************************* Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. *********************************************************
Seemingly Similar Threads
- AW: Windows 3.1 and Samba
- AW: AW: Windows Profiles not being placed in defined logon path
- [PATCH server] fixed functional tests after recent controller refactoring and managed node controller fixes.
- AW: Smbclient bind to IP
- UDP routing issues with multiple NICs