After I enable Samba on my Linux box, the windows machines on the network slowly (over hours) start disappearing from view of the network neighbourhood and windows services provided by windows machines become inaccessible too. Within 24 hours, windows services are totally crippled. Initially everything works great. But it appears the Linux (Intel) box running samba (2.2.7, compiled from source) is 'taking over', for reasons that I'm simply unaware of. Could someone please point me to relevant documentation? I've provided details of this problem before; and I'd be happy to do it again to anyone who expresses interest in helping me or pointing to the relevant documentation. -Jamie
> After I enable Samba on my Linux box, the windows machines on the network > slowly (over hours) start disappearing from view of the network > neighbourhood and windows services provided by windows machines become > inaccessible too. Within 24 hours, windows services are totally crippled.Add the following to the global section of smb.conf: local master = no for some reason samba as the master browser results in Not Happy Things, at least in my experience.
Maybe Matching Threads
- Stumped at "Network Neighbourhood", Samba server is visible, but it's path can't be found ...
- Stumped at "Network Neighborhood", Samba server is vi sible, but it's path can't be found ...
- My Workgroup eventually disappears when I enable SAMBA!
- AW: Machines not disappearing from browse list
- Disappearing shares