Score:0

SFTP Account Behaves Differently from Different Client Machines

mv flag

I have an Ubuntu system configured as an SFTP server. It has been reliably serving multiple SFTP clients for several years. Recently, a client made some operations changes and, for testing purposes, a new employee is attempting to access the server via SFTP, using the existing client credentials. They are able to connect to the server using the credentials, but they are unable to access files in directories where they have permissions. I am able to use the same credentials to fully access (r/w) their files and folders. So, from two different systems, using the same credentials, the connected user has different access abilities.

My question is this, could the issue be related to port settings differences on the client side? I know that port 22 is used by SFTP for connecting but, during file access, are other ports used? If port 22 is open on the client side, but port 20/21, or high ports (48000-65000) are closed, would an SFTP client connect to, but be unable to access, files to which they have permissions to do so?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.