![]() ![]() So, again, the uninstall failed to remove the folders. At 10:36 (after running SMBup) the folder existed. So, without functional SMB sharing, the machine is useless. I have at least 5 devices that need to access this server via SMB. When I say my Mini is "hosed" here is what I mean: I purchased this Mini to be a file server on my home network. Sudo launchctl load -w /System/Library/LaunchDaemons/įirst, thanks for the reply, really appreciate it. Sudo launchctl unload -w /Library/LaunchDaemons/ The last two ensure Apple's netbios Daemon (the one that talks to the finder sidebar) is: The first two lines make sure Samba is not running. Paste each of these lines separately in the terminal, since the first one will ask for your password and the rest won't. If you can connnect to the server manually and what you're missing is seeing the shared servers in the sidebar, you can force the Apple netbios daemon to start: This has never happened before for any user, the common error is not seeing network shared in the Finder's sidebar but accessing the shares has always worked with or without SMBUp (Samba and SMBUP don't touch the Finder's ability to connect to network shares, but OS X loses the ability to automatically add servers to it sidebar if its netbios service is replaced).Ĭan you confirm whether you can connect directly to servers? "Finder -> Connect to Server" menu option should allow you to enter the server and connect to it. ![]() I imagine you mean you can't access any shared folders from Windows in the Finder. ![]() You say you "cannot access and shares via Windows". From what I understand your mini is not hosed, but a single functionality for you is failing. The plist files, though, also don't make a difference to the local network services, they only start or stop the Samba services.Ĭontinously restarting and reenabled/disabling services doesn't (and shouldn't) make a difference. The program should make sure Samba isn't running but external factors may make it look as if it isn't already. If the plists where flagged for removal and weren't removed (they are NOT in /opt) either the folders have incorrect permissions or the files were in use. It affects whether Samba can run or not, only. ![]() To be clear: Nothing in /opt affects the machine's ability to use native services. Finally: If the program finds any problems removing (open files, permissions, etc.) the files will also remain. If you had ever, even unknowingly, placed a file in that structure then it would also remain. If you had ever installed MacPorts, for example, the structure would remain (as it uses /opt) as well. RE:EDIT3: The program only deletes its own files and won't touch anything else. I'll check the bug you mention, as it hasn't been reported before. RE:EDIT2: From your first post I imagined there had been a confusion with the uninstall screen. There's a simple one-line workaround to it but I didn't have time to tell you from the time you replied here to when you removed everything. RE:EDIT1: This is a limitation from OS X that became obvious only after the current version came out. Sadly, by now you've done all these actions I can't help much with. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |