![]() ![]() Tue, 12:08:33 (0000007) The user InsideSalesUSR login successfully via SSH. Tue, 12:08:33 (0000007) SSH authentication complete successfully. Tue, 12:08:33 (0000007) SSH session receive password of user InsideSalesUSR Tue, 12:08:33 (0000007) SSH session receive user name:InsideSalesUSR As I've mentioned, I can see the directory structure and contents when connected via ssh (port 22), but cannot upload although full rights are enabled and verified port 22 is available. The second is a standard ftp transfer test of the same file. I have two sets of logs here.one from an SSH connection attempting to upload a simple txt document. Permissions on the folder when viewed via the sftp client show all 7's (full authority). Permissions are set on both Server1 and Server2 to full control for Everyone, the local ftp user, and the wingftp service account. I did check with the Firewall guy and he verified port 22 is open on Server2 (the remote server) and that the two servers can access each other's folder structures. When using that latter method, it does not write to the directory and generates a "Server cannot write to a given path" message in my sftp client. Works if I use standard ftp over port 21, but not if I use the sftp/ssh over port 22. Problem seems to be when trying to actually upload a file to the site. ![]() I can connect to the new site and see a test file I had created in that remote home directory manually (directly on the server, no ftp/sftp/ssh). I've created home directories to remote servers before in WingFTP, but all those prior to this one were just standard ftp over port 21. Granted the WingFTP service account, ftp user account, and same local account full rights.even tried the 'everyone' group. ![]() I created a local user account that is identical to the user account I created in WingFTP. WingFTP is set up on Server1, the user's home directory is mapped to a shared folder on a a different server in the same domain (Server2). Wondering if someone can help me out here since I've exhausted my options. ![]()
0 Comments
Leave a Reply. |