I am not familiar with Mandrake and have not experienced this before. How is smbd and nmbd being started? Through inetd or as a standalone service in daemon mode (nmbd -D), you can do either but it is generally better to NOT use inetd.
Even with nmbd not running and the Linux machine not showing up in network neighborhood, you will still be able to connect to any shares it has if smbd is still running properly provided you know the share name. Basically a share or a machine does not have to be visible to be mapped and used, you just have to remember the share name yourself or map it manually once using the /PERSISTENT:YES yes switch so it maps every time you login the Win machine. Not a fix for your problem but it will allow continued use until you figure out nmb. Are there any obvious errors or hints in the nmb logs? On 31 Jan 2003 at 11:57, Rodney Kanno wrote: > > I have a Linux machine (Mandrake 8.0) running on a Windows network > with Samba. The Linux machine shows up in network neighborhood on > Windows machines, but every so often it disappears. To get it to re- > appear, I have to restart Samba twice. > > During the first restart, the "status" indicator says that NMB fails > to shut down, everything else is ok, but the Linux machine still does > not show up in Windows network neighborhood. However, if a windows > machine has mapped the Linux machine, it is still accessible through > the mapped drive. A second restart of samba is neccessary to get the > Linux machine to show up in windows network neighborhood. > > I am guessing that the NMB service is shutting down automatically for > some reason...does this seem accurate? What can I do to fix this? The > Linux machine is set-up to update a photolibrary via cron and as a > local web server. Any help/suggestions is appreciated! > > Rodney Kanno >
