RHEL 5 Likewise and users home folders permission denied issue
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
RHEL 5 Likewise and users home folders permission denied issue
I have one linux server that many users need to log into mostly to copy files. I've setup likewise to allow AD authentication so I don't have to mess with password resets and groups can be controlled in a more central location.
Here recently I'm having an issue where users are losing access to their home folder. The only way I can recreate the problem is by using a piece of software known as WinSCP. This will cause the issue to show up on my account and it's a common piece of software for other users, but it's something that all users have but not all users are experiencing the problem.
I realize this is a very specific issue and I can't seem to find anything in any logs telling me what could be going wrong.
Do you mean Likewise Open?
With the problem occurring, open a terminal and report the results of these commands:
Code:
who am i
ls -ldZ ~
Yes Likewise open sorry.
who am i
myuseraccount pts/0 2014-04-07 06:37 (computer I'm accessing from)
ls -ldZ
drwx------ myusername myusername
I've also done these commands for the user account I'm having the most problems with and I get the same outputs except anywhere that says 'myusername' it would be their user name.
Basically if you login through WinSCP everything looks fine and you can copy files, then if you try to use Putty to ssh into the sever again you will get a message that says
Could not chdir to home directory /home/username: Permission denied
and like I stated before doing chown -R username /home/username resolves the issue but it doesn't seem to fix it forever. I can keep recreating it on my user account.
as your clients (the work stations) are running MS Windows, why are they using WinSCP or Filezilla, why not just create a SAMBA share and map their network drive via a bat script at login?
as your clients (the work stations) are running MS Windows, why are they using WinSCP or Filezilla, why not just create a SAMBA share and map their network drive via a bat script at login?
Yes they are. I didn't set this up from the start but they actually have another share that is mounted in that way so I don't really know why this wasn't done again. When we deploy a new version of the server I will be bringing this up though.
Basically if you login through WinSCP everything looks fine and you can copy files, then if you try to use Putty to ssh into the sever again you will get a message that says
Could not chdir to home directory /home/username: Permission denied
and like I stated before doing chown -R username /home/username resolves the issue but it doesn't seem to fix it forever. I can keep recreating it on my user account.
ahh that is simple. both WinSCP and FileZilla have the ability to CHANGE permissions on the destination they are connecting to. verify that the permissions are set properly in the clients WinSCP program and your problems will not go away as the next update, or if an end users mucks with something he/she/it should not then poof the problem will return. see my other post on how best to resolve.
ahh that is simple. both WinSCP and FileZilla have the ability to CHANGE permissions on the destination they are connecting to. verify that the permissions are set properly in the clients WinSCP program and your problems will not go away as the next update, or if an end users mucks with something he/she/it should not then poof the problem will return. see my other post on how best to resolve.
In relation to the change permissions comment. I know they can change permissions of the file they are uploading but I was unaware they could change permissions to folders unless you think they are right clicking on a folder and going to properties to change it (which I doubt is happening). Otherwise I'm not aware of how they would change any permissions when they connect.
In relation to the change permissions comment. I know they can change permissions of the file they are uploading but I was unaware they could change permissions to folders unless you think they are right clicking on a folder and going to properties to change it (which I doubt is happening). Otherwise I'm not aware of how they would change any permissions when they connect.
if they perform any kind of sync action ever, it will sync with the "new" permissions.
This is just one of the headaches of letting EU play around with tools that are far to powerful for them to have access to.
I can't be for sure without asking them directly and even then they might not realize they are doing it but I don't think they are performing any sort of sync action but I see what you're saying.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.