when we try to connect to a SFTP server we INTERMITTENTLY get the ff. error:
"No connection could be made because the target machine actively refused it".
I've been trying to search but i cannot find a similar case where this happens randomly - sometimes we can successfully connect and sometimes we encounter this error. We turned on the verbose log and this is part of what we read:
"2017-03-15 07:24:38.833 INFO SshSession(1)[8] SSH: Connecting to
sftp.igxfer.com:22 using SshSession 3.0.5885.0.
2017-03-15 07:24:39.926 ERROR SshSession(1)[8] SSH: Rebex.Net.ProxySocketException:
No connection could be made because the target machine actively refused it. --->
Rebex.Net.ProxySocketException: No connection could be made because the target
machine actively refused it.
---> System.Net.Sockets.SocketException:
No connection could be made because the target machine actively refused it 52.33.119.6:22
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)"
Any thoughts? TIA!
Related
I'm having a hell of a hard time trying to figure out why I can connect to my SQL Server using Management Studio using my local ip or local computer name or sql instance name but I can't connect to the same SQL Server using my public ip address.
I have tried all of the below steps but nothing seems to fix the Wait Operation Timed Out error message:
Disabled firewall on the SQL Server and the computer I'm trying to use to connect with.
Port forwarding is enabled for the port I'm using which is the default 1433
Ran the telnet command: telnet publicip port from a computer outside of my network and it was successful
Restarted the SQL Server plenty of times
Enabled remote connections for the server and enabled tcp/ip for the 1433 port
I also enabled port forwarding for the sql browser service using the recommended port of 1434 via udp
Tried to connect with named instance but only works with local ip and not public ip
I am pretty much out of ideas at this point so any help is greatly appreciated
Here is the full error message just in case anyone needs to see it:
Cannot connect to XX.XX.XXX.XXX,1433.
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The wait operation timed out.) (Microsoft SQL Server, Error: 258)
Getting error while deploying:
Verbose: Pre-authenticating to remote agent URL 'https://server:8172/MsDeploy.axd' as 'someuser'.
Error: Could not complete the request to remote agent URL 'https://server:8172/MsDeploy.axd'.
Error: The underlying connection was closed: An unexpected error occurred on a send.
Error: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Error: An existing connection was forcibly closed by the remote host
Error count: 1.
I can telnet on 8172 port, have installed web management/web deployment services and they are running. Even its not giving authentication error if i give incorrect creds, so assuming its failing before authentication.
Destination Server is 2016 Datacenter
Enable TLS 1.0 and 1.1 on Destination server
Middleware: Oracle HTTP Server(OHS)
Version: 12.2.1.3
Configured Oracle HTTP Server(OHS) in standalone mode. Node manager is running perfectly. While starting "./startComponent.sh ohs1" i am getting the below error,
"""
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
Error: Error occurred while performing nmConnect : Cannot connect to Node Manager. : Unrecognized SSL message, plaintext connection?
"""
The solution found in internet is to changing the SecureListener to false in Nodemanager properties file.
When i did that i got the below error,
"""
weblogic.nodemanager.NMConnectException: Connection refused (Connection refused). Could not connect to NodeManager. Check that it is running at localhost/XXX.0.X.X:XXXX.
Error: Error occurred while performing nmConnect : Cannot connect to Node Manager. : Connection refused (Connection refused). Could not connect to NodeManager. Check that it is running at localhost/XXX.0.X.X:XXXX.
"""
And the solution for this is Setting the SecureListener to true in node manager properties file.
I am confused. Can someone help in resolving these errors?
Installed Oracle Access Manager(OAM) and OHS on same machine, but installed OHS in Standalone mode in different folder. After that, uninstalled OHS and Installed OHS in the same folder where i installed OAM, It worked.
when i try to make a ssh connection (port 22) connection to a server in my college it's giving "network error- connection timed out" error. I'm connected to internet through my home wifi. Then, I went to my friend's home any tried to establish the same connection, it worked fine. Is This the problem with my router or internet connection. please help me in troubleshooting.
PS. None of my roommates were able to establish the ssh connection in my home wifi.
"network error- connection timed out" I usually get either when I am not able to ping the SSH Server(connectivity issue) or IPtables on server is blocking my connection.
I've setup ApacheDS on my windows7 machine. It was working fine but suddenly it says connection refused.
Server is up but when trying to connect it gives below error. Please help
Error while opening connection
- Cannot connect on the server: Connection timed out: no further information
org.apache.directory.ldap.client.api.exception.InvalidConnectionException: Cannot connect on the server: Connection timed out: no further information
at org.apache.directory.ldap.client.api.LdapNetworkConnection.connect(LdapNetworkConnection.java:564)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$1.run(DirectoryApiConnectionWrapper.java:227)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1174)
It says connection refused.
No it doesn't. It says 'connection timed out'. It's not the same thing.
You have a connectivity problem or a firewall problem between the client and the server.