Came in to work this morning, and something wierd had happened. We're running samba on a linux box for file sharing. Nothing changed on that box, in terms of software versions or configuration. Some machines, both 98 and 2000 professional can't see the machine in network neighbourhood, but can get to it manually. Other machines still show up normallly. Other machines, 2000 professional, can see ONLY that machine in NN. Very odd. Any ideas? Shayne Lebrun Systems Administrator Veredex Logistics slebrun@veredex.com Office: (905) 282-1515 x 242 Pager: page_shayne@veredex.com
hi. I think you have a browsing problem, try to read browsing.txt that comes along with samba distribution. I get my book on unleashed by S. Litt, email you the troubleshooting for W2K and Win98 Mon Message: 5 From: "Shayne Lebrun" <slebrun@veredex.com> To: <samba@us5.samba.org> Subject: Samba machines disappeared? Date: Wed, 25 Oct 2000 12:04:45 -0400 Came in to work this morning, and something wierd had happened. We're running samba on a linux box for file sharing. Nothing changed on that box, in terms of software versions or configuration. Some machines, both 98 and 2000 professional can't see the machine in network neighbourhood, but can get to it manually. Other machines still show up normallly. Other machines, 2000 professional, can see ONLY that machine in NN. Very odd. Any ideas? Shayne Lebrun Systems Administrator Veredex Logistics slebrun@veredex.com Office: (905) 282-1515 x 242 Pager: page_shayne@veredex.com
Shayne wrote: | Some machines, both 98 and 2000 professional can't see the | machine in network neighborhood, but can get to it manually. | Other machines still show up normally. Other machines, 2000 | professional, can see ONLY that machine in NN. Very odd. It's mismatched protocols. Samba speaks TCP/IP, but PCs can speak TCP, Novell or NetBEUI, and often do, leaving Samba out of the conversation. Mounting the disk will cause all "bound" protocols to be tried, one after another, until something works or they all fail. This makes manual mounting work reliably. Browsing (Network Neighborhood) isn't as reliable: it prefers NetBLOOIE and local LAN broadcasting. The machines who can't see Samba are using NetBEUI, the ones who can, TCP. Remove the unneeded protocols from the PCs: it'll improve their performance, too! --dave -- David Collier-Brown, | Always do right. This will gratify some people 185 Ellerslie Ave., | and astonish the rest. -- Mark Twain Willowdale, Ontario | //www.oreilly.com/catalog/samba/author.html Work: (905) 415-2849 Home: (416) 223-8968 Email: davecb@canada.sun.com
Shayne, On Wed, 25 Oct 2000 12:04:45 -0400, Shayne Lebrun wrote:>Came in to work this morning, and something wierd had happened.>We're running samba on a linux box for file sharing. Nothing changed >on that box, in terms of software versions or configuration.>Some machines, both 98 and 2000 professional can't see the machine in >network neighbourhood, but can get to it manually. Other machines >still show up normallly. Other machines, 2000 professional, can see >ONLY that machine in NN. Very odd. Any ideas?Additionally to what DCB suggested (check for unneeded protocol stacks on the clients) you should check if your nmbd died. We sometimes see this (according to nmbd's log file it terminated after getting a SIGTERM nobody has knowingly sent). We now regularly check for existance of 1 or 2 nmbd instances (it depends on your wins configuration) and restart them if needed. Regards, Robert -- --------------------------------------------------------------- Robert.Dahlem@gmx.net Fax +49-69-432647 --------------------------------------------------------------- Sent using PMMail (http://www.pmmail2000.com) - fast, decent, email software; far better than Outlook. Try it sometime.