11235 Views 20 Replies Latest reply: Dec 25, 2012 7:56 AM by charlesf49
Currently Being ModeratedNov 3, 2010 1:43 PM (in response to morph21)Bless you!!!!! It's been a long time for me too.
This works! I had to wait several minutes but now it's working like it should.
Thank you so very much.Macbook Pro (Late 2008), Mac OS X (10.6.4), 4GB Core2Duo 2.4 /w SSD
Currently Being ModeratedNov 3, 2010 4:28 PM (in response to morph21)Thanks! Worked for me too, though I did have to manually restart the nmbd service. Also, can you do this to multiple Macs in the same network?iMac, Mac OS X (10.6.4)
Currently Being ModeratedNov 4, 2010 9:59 AM (in response to LCee)Hey LCee, glad it worked for you too!
The "delay" is just for the first time. What happens is that each machine announces its name to the master. It does so when it joins the network and then after 4, 8 and 12 minutes, and from there, each 12 minutes only. That is why you had to wait a bit, but once you set it up like this, you shouldn't have to wait more.
Lets say a Windows machine is turned on first. It then becomes the Master Browser. When the Mac is turned on, it claims the Master for itself and then the Windows machine transfer the information for the new Master. Once again, there is no wait, well, just a few seconds for the transfer.iMac 27" i7 4x2.8GHz 8GB, Mac OS X (10.6.4)
Currently Being ModeratedNov 4, 2010 10:03 AM (in response to falvesjr)falvesjr,
Yes you can. You can have a Master and "backup" Masters, so it should work. In my case, with only one Mac set up all the others started to work too.
It seems that whenever Windows is chosen as a Master Browser things won't work properly anymore. So, if you have a Mac running as MB in your network, everything should be fine.
Worst case you'll have a lot of redundancy with "backup" Master, but unless we are talking about a huge network of 100+ or even more machines, I don't see how this could give any problems.
As for manually restarting the service that is strange, but in the end restarting was the objective and you got it, hehe. =)iMac 27" i7 4x2.8GHz 8GB, Mac OS X (10.6.4)
Currently Being ModeratedNov 4, 2010 4:06 PM (in response to morph21)No, not a huge network, just at home with three Macs and a couple of PCs that are used regularly. I was just wondering if it's OK to have multiple Macs as masters just in case the "main" master Mac is off, then all would still be well for the other Macs.
Thanks for the info! I just wish someone had an easy fix like this for the problems with smb file sharing on the Mac!iMac, Mac OS X (10.6.4)
Currently Being ModeratedDec 29, 2010 10:27 PM (in response to morph21)Anyone know how to do this in Leopard? Those lines don't appear in that OS but it has the same problem seeing my Windows machine.Dual G5, Mac OS X (10.5.8)
Currently Being ModeratedDec 31, 2010 7:13 PM (in response to Kurtster)It is still there. When in the editor you need to scroll down with the arrow keys to see more lines. Then you can add the lines above and you will start to see your network devices. Mine took awhile so be patient. 8))
Hope this helps.MacBook Pro, Mac OS X (10.6.5), iPhone 3GS iOS 4.x
Currently Being ModeratedFeb 28, 2011 1:15 AM (in response to morph21)
Currently Being ModeratedFeb 28, 2011 4:42 AM (in response to morph21)G'day morph21,
Thanks for sharing this workaround. Windows 7 uses an updated protocol for network browsing, which OS X does not support. However, Windows 7 does support the older approach (used by Windows XP and prior) when it is not the master.
It should be remembered that, IF you use your Mac on a corporate network (i.e. running Active Directory), it is NOT a good idea to force it to become the master browser over and above the primary servers on the network. Your IT Admin people will not be happy!
p.s. an alternative way of getting Windows 7 machines to appear on your home network is simply to boot your Mac first. It then becomes the local master by default. When Windows 7 starts it will simply tap into your Mac's list for it's own browsing.MacBook Pro (2.53 GHz, 4GB, 13i), Mac OS X (10.6.6), MacBook (2.16 Ghz, 2 GB), Powerbook G4 12i (867 MHz, 640MB, 10.5.8)
Currently Being ModeratedMar 11, 2011 5:26 PM (in response to morph21)I tried this... for testing...I disabled the Computer Browsing service on 2 Vista Machines and 1 Windows 7 Machine. I forced smb.conf to become the master.
I booted all PCs and confirmed using nbtstat that all PCs were not the Master - I then booted up my Mac Book and it too will not become the master... so there is no master in my network if I were to leave it this way.
Cheers 13" MacBook 2Ghz, Mac OS X (10.6.2), Apple TV iPod Touch 8Gb iPhone 3GS (16GB) Mac Plus (in the closet)
Currently Being ModeratedMar 11, 2011 6:11 PM (in response to morph21)I stand corrected.... after letting everything sit for a few minutes the MacBook finally took over as the Master and all PCs can be seen from the Finder's Sidebar... just weird that it would take so long to take over. 13" MacBook 2Ghz, Mac OS X (10.6.2), Apple TV iPod Touch 8Gb iPhone 3GS (16GB) Mac Plus (in the closet)
Currently Being ModeratedMar 17, 2011 1:51 PM (in response to RodneyW)Rodney,
Can you provide a little more technical details? I'm trying to support OS X in a corporate network and would be very unhappy if the users forced a desktop machine to be the master browser. NOTE to others: If you make the suggested changes on your system and bring the machine to work, the network AND your machine may become very slow!
We are using WINS on Windows 2008 servers, but it appears that 10.6 doesn't take advantage of this. I'm seeing strange entries in the log.nmbd file that the Macs cannot connect to the discovery port (138)
-- PerMacBook Pro, Mac OS X (10.6.6)
Currently Being ModeratedMar 17, 2011 2:06 PM (in response to vikinggeek)No worries Per,
OS X uses "old" protocols for MS Networks, that are compatible with WIn XP/2003 and prior, but not fully compatible with Windows Vista/7/2008 and later.
The upshot of this is that OS X works (close to) perfectly on a network with a Windows XP master browser or a Windows 2003 Domain Controller.
On a network with a Windows Vista/7 Master Browser or Windows 2008 Domain Controller, it fails to be able to populate the network list. This means that the user is forced to manually identify and connect to servers.
On a private network, where I am in full control of the machines, I can force OS X to win the Master Browser election by starting it first. The Windows Vista/7 machines then start up but do not force a re-election, because there is a Master Browser in place.
On a corporate network running Windows 2008 Domain Controller - the OS X user is at a real disadvantage.
As far as I know all of this arises because Apple is on an old version of Samba - because the Samba changed their licensing requirements some time ago. With a bit of luck Apple will do something about this in Lion.
RodneyMacBook Pro (2.53 GHz, 4GB, 13i), Mac OS X (10.6.6), MacBook (2.16 Ghz, 2 GB), Powerbook G4 12i (867 MHz, 640MB, 10.5.8)
Currently Being ModeratedMar 17, 2011 2:36 PM (in response to RodneyW)Rodney,
Thank you for clearing things up. This problem has caused lots of headaches since the Windows users can "see" the Mac users but not the other way around. When you say "old" and "new" do you refer to "Smb" and "Smb2" or is it something else? Any pointers to technical documentation (from Apple) would be appreciated.
-- PerMacBook Pro, Mac OS X (10.6.6)