sftp net drive ssh server settings - get error 10058 - sftp

I am trying out Eldos's SFTP Net Drive to map a drive to a virtual Ubuntu server. I works great when authenticating with a password. I have tried the normal/typical methods for configuring Key-based access. However, I receive error 10058. I have searched for clear instructions without success.
Anyone using this with Key-based access? Please share how you have it configured.
Thank you :)

If you're connecting via command line (e.g. using "open /profile:server" command line arguments) and you're accessing recently reinstalled server, the connection will silently fail because of changed server ssh fingerprint.
Try to reconnect manually (not using command line), accept new fingerprint and the problem will resolve.

This is because the server doesn't accept the key for whatever reason and closes connection. Usually this is an indicator of buggy server which normally should send the error packet in response.
But your question is offtopic here on StackOverflow.

Related

Receiving Invalid Signature - SFTP

Our file transfer automation software is connecting to an external SFTP server to download files. It's connecting using Putty's command line tool PSFTP. When it kicks off at it's scheduled time, an error results. The error is:
Remote working directory is /directory
lcd: unable to change directory: Invalid Signature.
Using username "username".
Pre-authentication banner message from server:
| IM CCaaS FTP server
End of banner message from server
When I manually FTP to the server, I can log in with no issue. I then re-run the job and it completes successfully. I've googled this and found articles on key exchanges with similar errors, but this connection isn't using private/public keys. I cut over the application to a new Windows 2016 server on September 21st. There have been some successful transfers. I've also read the version of PSFTP may be the issue (0.73), but I would have expected consistent issues connecting. It seems sporadic. I'm not sure if the issue is on my end or at the destination. Any thoughts?
This is not SFTP problem. You have problem when changing a local working directory (using lcd command in the sftp client).
So this probably covers the problem:
System error 2148073478, extended error, or Invalid Signature error message on SMB connections in Windows Server 2012 or Windows 8.

Snowflake - ERROR [HY000] [Snowflake][Snowflake] (4)

ERROR [HY000] [Snowflake][Snowflake] (4)
We are running ODBC on a Windows 10 computer. I have posted an image of the error messages below. We are also NOT using a proxy server.
enter image description here
You are connecting from behind a Proxy server, the name of which the driver is not able to resolve.
Try giving the IP address of the proxy server. Check
https://docs.snowflake.com/en/user-guide/odbc-parameters.html#connecting-through-a-proxy-server
for deatails on how to connect.
get the latest odbc driver
Change registry setting in windows to set ssl_default=true,
https_proxy environment variable with proxy serve:port
finally you would have to allow all the url that is emanating from that server to internet. There will be url's to snowflake computing and s3 aws urls while you invoke odbc different from web UI for querying.
Some systems have proxy settings in their environment; this is not documented on the odbc description on the Snowflake website.
So, if the other solution don't work, check this out.
I had the same issue and it was solved by taking out "https://" from the beginning, so that it will be treated as a server as opposed to a URL.

Configure HTTP Access to Analysis Services - Won't work with basic authentication

Followed the instructions in https://msdn.microsoft.com/en-us/library/gg492140.aspx
SSAS is running on a hosted server. No domain.
Able to connect with anonymous authentication, but when basic is enabled, neither SSMS or Excel will connect.
Error from SSMS is "The remote server returned an error (401). Unauthorized"
Credentials are set up on the remote machine as DOMAIN:443
Credentials have admin privileges on the server.
Excel says "connection cannot be made to remote machine or SSAS is not running"
HTTP or HTTPS doesn't matter.
When it connects with anonymous, no cubes are returned so it is apparently doing nothing with the userid/password. Just connecting.
When I connect via port 2383 using the same credentials, I have no problem in SSMS or Excel.
Help is GREATLY appreciated. Thanks.
This was partially solved by starting over and following the steps in this article:
https://technet.microsoft.com/en-us/library/cc917670.aspx
Honestly, I can't pin down the exact resolution, but I believe it has to do with using a different folder structure (other than inetpub/wwwroot...) on my D drive and therefore losing the standard security configuration.
I created an OLAP folder on C:/inetpub/wwwroot and it works... with the exception of SSL which still does not work.
HTTP connects fine, but not HTTPS. Still working on that.

EOF while reading packet - connection failed

I use cyberduck for SFTP my website files to the server. Dreamhost is the server.
In setting up a new bookmark in cyberduck I received this error "Connection failed - EOF while reading packet." [end of file]
The website is up and working fine, http://ce-t.org
Initially I thought this error had to do with the connection opening with cyberduck. So I setup a different bookmark to test and was able to do without a problem.
I have also deleted my first attempt to setup and reset up. This did not alter anything.
Now after doing more reading, may be in one of the website files?
As you can see i am a novice.
Help appreciated.
Usually when I run into this issue, its because my pw has expired.
Try SSHing into the server and change/update your pw. After I change it, I can FTP in.
This is 3 years too late for the OP. But I had this error when trying to make an SFTP connection to hosting on a Plesk server and the solution was to:
Enable the 'Access to the server over SSH' setting for the ftp user via the Plesk Control panel.
Of course you might need to contact your hosting service to get this done if you are not managing your own server.
In my case the same error occurred due to a syntax error in the .bashrc file on the remote server.
Also note that the default account setting for an FTP user at Dreamhost might specify an FTP connection. If so, trying to use Cyberduck to connect via SFTP will generate this error message. You can use the Dreamhost control panel to edit the user's record to specify SFTP.
In my case I have used dropbear ssh server.
I replace this server with openssh server, and now i can open the sftp connection without any issues.

The server rejected SFTP connection, but it listens for FTP connections

When I use WinSCP in Windows to connect to VMware with Ubuntu, it prompted this:
The server rejected SFTP connection, but it listens for FTP connections.
Did you want to use FTP protocol instead of SFTP? Prefer using encryption.
What's the matter?
I can succeed to ping Ubuntu in Windows.
The fact that you can ping the server has nothing to do with what protocols it supports.
The message says that the server does not listen on port 22 (SSH, SFTP), but listens on port 21 (FTP). The point of the message is that WinSCP defaults to SFTP protocol, what is not common. So it tries to help users who expect FTP to be a default. But that's not relevant to you apparently.
As #ps2goat suggested, make sure you setup SSH/SFTP server.
For more details, see the documentation for the error message The server rejected SFTP connection, but it listens for FTP connections.
If you see this error all of a sudden (when SFTP has always worked for you for this particular server), and if you are using CSF (ConfigServer Security & Firewall), then it might be that your IP was blocked for SSH access. Try flushing all blocks. Also, try restarting the SSH server.
Old question but still responding so others might get benefited.
I stumbled upon this error and the first thing I checked was if my ubuntu machine had ssh installed. It was there and the latest version and I still would get this error.
As long as you have ssh access to the target, check the ssh service status and most certainly it'd be found inactive. Turn it on using
sudo service ssh restart
and you should be back in the game.
Do check the status of the SFTP by using
sudo service ssh status
and take any corrective action.

Resources