The next step in trying to fix this is now back to the terminal window and trying to get this thing connecting.
From the ubuntu boards, Morbius1 has suggested:
-  Then I want to create a “Samba” directory away from your home directory.
sudo mkdir -p /Samba/Public
I’ve just gone into my Terminal window (remember it’s Crtl-Alt-T) and typed this in.
Looking at the command, again we see the power word “sudo” and the command “mkdir” could possibly be MaKe DIRectory. The “-p” could be anything, but I’ve noticed that there are other ones too, like “-a”, but I don’t know what they mean. I’m assuming it’s some sort of formatting command. Lastly, the /Samba/Public must be the actual name of the directory (or folder) that’s being created here.
I sure hop it worked, because the Terminal just asked me for my sudo password and then spat me back to the cursor. I’m assuming no news is good news.
- Then change permissions so that anyone can access it:
sudo chmod 777 /Samba/Public
This is typed in the terminal window. Power word sudo, as usual. The chmod 777 is tricky, but I’m think the mod is short for modification, so that kinda makes sense – the 777 I believe is the setting for the modification. I don’t know much about this, but I looked it up on Wikipedia and it seems I was wrong. Chmod is short for CHange MODe. And the numbers are about permissions. This is a little off track, but interesting…
|6||read and write||110|
|5||read and execute||101|
|3||write and execute||011|
I don’t know about this rwx thing, but the fact that each of the 7’s give full permissions, seems like a pretty solid thing to do. Hang I just worked it out. r = read, w = write and x = execute. Therefore, it seems that the 777 means that we’re setting full permissions to read, write and execute (execute = run or start up).
I put that into the terminal and it didn’t care. Again, assuming no news is good news.
-  I want to create the simplest possible share at the bottom of smb.conf as the only share on this box:
[public] path = /Samba/Public guest ok = yes read only = no force user = keith
I’m getting a bit dizzy going back and forth between the Terminal and the pop-up conf edit window, but it seems necessary.
I’ve opened the conf window again using the command as I did in the last post:
sudo gedit /etc/samba/smb.conf
I didn’t want to just whack it in, so I did a little comment of my own and added the code as suggested above.
# This section added for troubleshooting connection # [public] path = /Samba/Public guest ok = yes read only = no force user = keith
I then saved the conf file by pressing the save button in the menu bar of the pop up window. When I’m back in the Terminal, I’ll do the next step.
-  Then restart some services:
sudo service smbd restart sudo service nmbd restart
As you may recall, we went through all about these “daemon” things that are the little services that run all of the samba stuff in the background. We’ve made changes to the config and other things, so we should start these running again so any changes can be picked up. Sudo, power word. “Service smbd” or “Service nmbd” are the file names of the services and, I assume, the type (eg service). Restart is pretty straight forward.
After entering the above into the Terminal window and hitting enter after each line, I got the following responses:
smbd start/running, process 4040
nmbd start/running, process 4054
That done, onto the last step as offered on the forum…
-  Then we’ll see if the Linux box itself can access it’s own samba share with the following command in the terminal:
This is starting to look a little scary now, because I’m not quite sure if there are steps I should be doing. I’m writing this post as I’m doing the tutorial, so I hope I’m doing it right!
Alright, done. Some, I think, positive results. Firstly, there isn’t anything that happens when you type the above in – you end up at the cursor with no message. However, when I first did it, it gave me a pop up error message that said I couldn’t connect.
Then I remembered that I had turned the wireless off. I reconnected to the network and typed the line in again. This time there still wasn’t a message, but there was a whiring of the hard drive – it seemed that something was happening.
I noticed that the “files” tab on the desktop was highlighted as if I had opened a screen. I clicked on the icon and it happily looks like I am now connected to that folder through the network. This is kinda of cool. It really seems like we’re getting somewhere.
-  If that works we can see if you can do the same thing from the mac using “guests” not “keith” as the “Connect As” user.
Just when I was doing so well. I don’t really know what this step means, and further, I don’t know how to do it. Bear with me while I try to battle my way through it.
I’ve gone to my Mac and clicked on the Finder program to bring it up. Then I’ve gone to the menu bar at the top and clicked on Go to get the drop down for “Connect to Server”. Currently I have two connections set up – neither work – as recommended earlier in my posts.
The kbfileserver.local/keith seems to be very similar to the one I got nautilus to set up above. So I doubled clicked on it and it gave me the not connected error message.
There is something I can try though – and it may be what I’m supposed to do. Morbius1 has said I should connect using “guests” not “keith” so that might be where it could work.
Unfortunately, this didn’t seem to work. I typed in:
And it gave me:
- There was a problem connecting to the server “kbfileserver.local”
I also tried both “guest” and “guests” to no avail. I’m thinking that I’m getting close, but not quite there yet.
I have just jumped back to the forum to see that Morbius1 has made a comment, so I had some other things to try.
- The same as above, but instead of guest, I should be writing “public” – which makes sense because that’s what we called the folder.
- I should try pinging from the Mac to see if it connects.
The “public” thing didn’t work and the ping gave this error:
ping: cannot resolve kbfileserver.local: Unknown host
(By the way, the Terminal window on the Mac is on the launchpad under “Other”. You just click on it and it opens the terminal window.)
I’ll report back to the forum and see what comes out of my results.