The server error may possibly be initiated by an error on the client (WinSCP) side. In both cases check the log file of your server to see an actual reason, it closed connection for. If the problem repeats, try turning off Optimize connection buffer size. If you are a new customer, register now for access to product evaluations and purchasing capabilities. Need access to an account? If your company has an existing Red Hat account, your organization administrator can grant you access.

Astra 3400 scanner driver. Want to improve this question? So it's for Ask Ubuntu.Closed 4 years ago.I have an issue when I'm trying to connect to a SFTP-server using FileZilla. I'm sure that the server is up and running, but I just get: Error: Server unexpectedly closed network connectionError: Could not connect to serverI'm trying to connect to a server by using sftp://WhateverLinkToServer.com and the port is 22015, tried to open the port in the firewall with no luck. I'm positive that the username and password is correct.Is there any method to debug this, a log-file or something to show if I'm missing anything, or do you have any other suggestions of how to solve my problem?Update:I was able to connect via the terminal directly to the SFTP-server.

Any suggestion on what the problem is with my FileZilla? Is there something wrong with my key fingerprint?Cheers,Magnus.

All of the sudden I'm getting the following error on my local web server (Win7 64bit, IIS 7.5). I've uninstalled & reinstalled IIS locally and it didn't fix it. IIS is set to start up automatically and I can see that the service has been successfully started. Upon a fresh reboot if I go into IIS and click on start website I get the following error:'The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020'If I try to start debugging on my local website project I get the following error:'Unable to start debugging on the web server.

The underlying connection was closed. The connection was closed unexpectedly.' Any ideas on what I can try? I've been doing research on the issue and Microsoft suggest making sure no other service is listening on the same ports.

I've verified that this isn't the issue.