>First off setting up samba is easy, debugging the simple errors is hard.
Follow this tutorial:
And it should work. I did this at home on my windows/linux computers in five minutes.
It took me longer at the office. First doesn't work, why? Check on the local machine.
smbclient -L my.ip.address -U username
That will let you get your permissions set.
session setup failed: NT_STATUS_LOGON_FAILURE
This is just a login error. So a) you got the passwd wrong, b)you didn't at the username/passwd to the smbpasswd.
tree connect failed: NT_STATUS_NO_SUCH_GROUP
I turned off the force group=no group,
#force group = no group
or I made the force group = usergroup where usergroup is a valid group that the user is part of.
force group = usergroup
Then once you get the going you can use:
(remember to excape your slashes)
That will help you get your r/w access permissions straight. So I had a lot of problems here
THE HOME DIRECTORY IS A SPECIAL DIRECTORY
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
This means that the directory you are pointing to is not accessible. If you think you have recieved this message in error it could be because you are using a special samba directory. Point it somewhere else and fix the permissions.
Now that it is working on the local host, move to a remote computer. If you have access to another linux box with smbclient on it. All the better.
smbclient \\my.ipadd\share -U uname
wrong ip address, at least it was in my case
You have a firewall up. I need to go to here to figure out how to disable my firewall, for certain ports. Possibly this Samba Security and Troubleshootingcould help, but if you have a gui version, all the better.
This is very likely to be a problem
Those are all the problems I had. I have about 15 tabs opened in mozilla trying to research these problems. It seems that a lot of people experience these problems and then don't write about it afterwards. Essentially
A) Set up samba
B) Set up your firewall
C) Make sure you aren't using /home/stuff becuase it is special and if you want to use it. There is a way to do that.
SElinux: SElinux which comes with certain distributions can certainly be attributed to some of my troubles. I had directories that I could not write to. It seemed like we were connected but in actuallity ... we weren't, so here is what I did.
This helped take care of all the firewall and the "special" directories.