So, after the last tutorial and battle with ubuntu, I’m no further along towards my objective, but more experienced. 🙂
I have turned to the ubuntu forums to seek advice and help. Turns out there are some awesome people there who are willing to help. Hopefully my issue can help others on the forum as well. Here’s the edited highlights of the thread. If you want to see the original, it’s here: http://ubuntuforums.org/showthread.php?t=2203514
I was asked to restart smbd which is supposed to be the Samba daemon (application that runs Samba in the background) but it didn’t help me at all. It’s all just trouble shooting, I guess. Here’s what I did – bold was the reply – in the Terminal window.
sudo restart smbd
smbd start/running, process 2782
sudo status smbd
smbd start/running, process 2782
That didn’t seem to be getting me anywhere, so the next step is to give more information. The follow information is the command they asked me to run and the result (command in bold). And of course this was run from the Terminal window (I’m getting the hang of just hitting Crtl-Alt-T to bring the window up).
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section “[homes]”
Processing section “[printers]”
Processing section “[print$]”
Loaded services file OK.
Server role: ROLE_STANDALONE
server string = %h server (Samba, Ubuntu)
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
username map = /etc/samba/smbusers
unix password sync = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
usershare allow guests = Yes
panic action = /usr/share/samba/panic-action %d
idmap config * : backend = tdb
comment = Home Directories
valid users = %S
comment = All Printers
path = /var/spool/samba
create mask = 0700
printable = Yes
print ok = Yes
browseable = No
comment = Printer Drivers
path = /var/lib/samba/printers
net usershare info --long
\\KBFILESERVER KBFileServer server (Samba, Ubuntu)
\\KBFILESERVER\keith Home Directories
\\KBFILESERVER\IPC$ IPC Service (KBFileServer server (Samba, Ubuntu))
\\KBFILESERVER\print$ Printer Drivers
\\KBFILESERVER\homes Home Directories
So that’s pretty much it for all the info. They then asked me to try some things. Here’s the commands and the results.
- sudo restart nmbd
nmbd start/running, process 2586
This didn’t seem to have any effect, but I tried it anyway. The next step was to try to get me connecting to the Mac. The ubuntu forum user Morbius1 (http://ubuntuforums.org/member.php?u=982144) helped me through the steps:
- If you are talking about the [homes] share you won’t be able to connect to it unless you access it a certain way
- Create a samba password for keith:
sudo smbpasswd -a keith
I did this already iin the last tutorial, but it can’t hurt. I got the same result, though. It asked me for the sudo password (I assume because it’s making serious changes) and then asked me for my samba password. I then confirmed the password and iot sent me back to the prompt.
- From the mac Connect to Server it should be like this
- Finder > Go > Connect to Server >Server Address
This is on the Mac itself now. I opened a new Finder window then from the menu bar at the top, I clicked on the word Go. It dropped down a list where I found “Connect to Server” at the bottom of the list. Once I did that a little box popped up.
In the box, it asked me for my server address and then I hit to hit the little plus symbol beside it to add it to the list of favourite servers the Mac is connected to. It was then added to the list, I clicked on it to highlight it and then hit the Connect button. It searched for a while, but came up blank. This was the error message:
The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again.
Almost in preparation for this, Morbius1 suggested an alternative.
- You may have to pass the username twice:
Unfortunately, it came up with the same error as above. Unable to connect. Weird.
The next piece of advice from Morbius1 was the following:
- the one thing you do not want to do is have 2 share definitions for the same path so if you create a share definition in smb.conf delete the one you created in Nautilus. You can do it graphically or by command:
net usershare delete documents
I entered that at the prompt on the terminal and pressed enter. A new line showed up, but nothing seemed like it had done anything. I tried to reconnect on the mac to the server address that I have mentioned above (both of them) and still the same error message. It seems to me that I’m still not allowing the mac to visit. 😦
Posting now to see what happens next.