can't connect to remote server FATAL ERROR Connection reset by peer - ssh

Hi Everyone I am trying to access my server remotely by either ssh or ftp/sftp but when ever I try I get this error "FATAL ERROR: Connection reset by peer" I have read that I has something to do with the connection being dropped but I haven't found much on how to fix this issue. thank you!

Related

WSAECONNREFUSED: Connection Refused error in AIX server

I'm seeing this WSAECONNREFUSED: Connection Refused error when i'm launching my Smarterm terminal emulation session on a IBM AIX server.
Not sure as to what could be the reason behind this. Any help on this would be appreciated.

Local SQL connection timeout

For the past couple of weeks at exactly 6 AM all connection to the DB are stopped. I assumed this was a network error, but the error happens when using management studio on the machine where the DB is installed, i.e. NO NETWORK it is the local SQL. The error is connection timeout.
Does anyone have any suggestions on what could cause this?
Thanks
Chris

A connection attempt failed because the party did not properly respond?

I am trying to remotely connect to a Database and every time I try I get the error:
A connection attempt failed because the party did not properly respond
First thing, Please recheck the connection string: server, database and user used to connect it.
Secondly, make sure user you are using for connection is having sufficient permission over database.

ERROR: SERVER CLOSED THE CONNECTION UNEXPECTEDLY

When i connect to the server on PostgreSQL i get this error:
Server closed the connection unexpectedly.
This probably means the server termitate abnormally before or
while processing the request
If someone could help me i would appreciate it.
Thank you
This problem occurs when running postgres locally on win2k
see here

Connecting to my remote SqlServer database

Im currently making a wpf Windows Application, and it withdraws data from a database, so it is needed that I setup a connection to my remote servers SQL Server Database. Now i am getting a couple errors. When I first of all try to connect to my remote servers Sql Server using management studio, just to test if I could actually make a connection, I get the following error.
A connection was successfully established with the server, but then an error occured during the login process. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.)
(Microsoft SQL Server, Error: 233)
And ovcourse, I did try my best to do my research, and I found out a few things talking about allowing the SqlBrowser in firewall properties, done that...
allowing a connection to port 1433 and port 1434 through windows firewall, done that both.
Is there something Im missing or not doing?
Also it says "a connection was succcessfully established with the server" which means that It is able to connect, but something is going wrong somewhere. Also where it says "error occured during login process" could it simply mean I entered the wrong credentials?
I mean, when installing the SQLExpress I chose Windows Authentication so I never really got a username and password, So i just used the username and password for the Administrator account I use to connect to my server itself. Dont know It could have something to maybe just do with my login.
Could anyone please point me in the right direction as to why Im getting that error, even though I have enabled the TCP Connections and allowed SqlBrowser.
Any help would be greatly appreciated.
Thanks.
This is a bad certificate-related error, probably caused by different operating systems/environmental differences. If this is for testing purposes I'd disable the certificate, or you can configure it here (which is probably a good idea if you're creating a real application and not just playing around with it).
Please run the sql service and agent service by creating new id and start the service with that like ea admin or any other.
The port error will continue to show even if you fix the port ,check telnet configuration and enabled/open port via it.
I had similar problems so i created a virtual server installed sql server2008 r2 and then started it worked fine.
There are possibilities of error and authentication problems since we reuse the server by formatting it .