I have 2 SMSC connections, the first works fine, i can send and receive messages, however the second returns the error below....not sure what am not doing right...
2012-09-29 09:00:24 [9921] [7] ERROR: connect failed
2012-09-29 09:00:24 [9921] [7] ERROR: System error 111: Connection refused
2012-09-29 09:00:24 [9921] [7] ERROR: error connecting to server 10.*.*.* at port 5019
2012-09-29 09:00:24 [9921] [7] ERROR: SMPP[smsc_hope]: Couldn't connect to server.
2012-09-29 09:00:24 [9921] [7] ERROR: SMPP[smsc_hope]: Couldn't connect to SMS center (retrying in 10 seconds).
It seems like your kannel cannot connect to SMSC due to "connection refused" reason.
Can you do the "telnet" from the same machine to the specified IP address and port - I guess not ?
There might be some firewall misconfiguration either on your side or on SMSC side, making the target IP and port not reachable. If there is VPN tunnel between, is it up and running ?
Are you using correct IP address and port ?
If there is no obvious reason on your side, you should contact support staff from the "SMSC_HOPE" and describe them the problem.
Related
Pusher error: cURL error 7: Failed to connect to local.zts.com port 6001: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://local.zts.com:6001/apps/1407161/events?auth_key=9f72eeb7d24761835162&auth_timestamp=1656943955&auth_version=1.0&body_md5=5281128b393b7c73bb20514e675cf3d9&auth_signature=d033743a711c8372d8b5437f6296cf05b1a4c0f150e8a7136a3f3f17171b8ed4.
I am trying to access PhpMyAdmin on my browser through an SSH tunnel on mac OS high sierra for setting up AWS Lightsail. I've downloaded my default SSH key pair and have adjusted permissions using
chmod 600 KEYNAME.PEM
I've tried ports 80 and 81 and have tried using port 1025. I do not get any errors in Terminal, but when launching via the URL: http://127.0.0.1:8888/phpmyadmin as suggested in Bitnami docs (with port adjusted to 1025 if 1025 is running), I get the error: "This site can’t be reached
127.0.0.1 refused to connect." and in Terminal: "channel 2: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused"
I'm using Google Chrome, 64-bit. I've tried turning firewall off, as well.
Any suggestions would be greatly appreciated! I'm new at this. Thank you!
I figured it out! I'm not sure what did it, but I added a slash at the end of the URL I was accessing, i.e. localhost:8888/phpmyadmin/ instead of localhost:8888/phpmyadmin. I also installed Cyberduck for mac and turned started/stopped my local servers with MAMP. Hoping this is helpful for someone else.
I have two virtual servers with Ubuntu 16.04 hosted by different providers. After I migrated my desktop from Win7 to Win10 I can not connect to the servers via SSH (see the error messages below). I have tried other operating systems as well:
Windows 10 and ChromeOS: connection refused
Windows 7, Android 8, Ubuntu 16.04 (on desktop): connection works
The same application (JuiceSSH) can connect on Android, but returns 'connection refused' on ChromeOS.
The error messages:
1. Gitbash (Windows 10)
$ ssh user#myhost
ssh: connect to host myhost port 22: Connection refused
2. Secure Shell (ChromeOS, with -vvv)
Connection with user#myhost is established...
Loading NaCl plug-in... Finished
OpenSSH_7.6p1, OpenSSL 1.0.2k 26 Jan 2017
debug2: resolving "myhost" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to myhost [myip] port 22.
debug1: connect to address myip port 22: Connection refused
ssh: connect to host myhost port 22: Connection refused
NaCl plug-in ended with the status code"255".
3. Bitwise SSH Client (Windows 10)
...
06:34:46.871 Connecting to SSH2 server slejska.de:22.
06:34:47.918 Connection failed. FlowSocketConnector: Failed to connect to target address. Windows error 10061: No connection could be established because the target computer refused the connection.
06:34:47.949 The SSH2 session has been terminated.
Remarks:
I regenerated OpenSSH host keys on the servers, but without any effect.
I deactivated the Windows Defender Firewall, but also without any effect.
Solution:
The port 22 was for some computers blocked on the router. It had nothing to do with the operating system. After opening the port for all computers, works everyting perfect. Thanks to #Nathan-McCoy
Just making my original comment more visible.
Not all systems allow TCP port 22 by default, which is the default port for ssh.
Here are some things to try and help find the source of the issue.
Suggestions
Check for open port on client
Run nmap <server> on the client which wants to connect via ssh.
If port 22 is not shown as open, this may be a firewall issue.
Check for open port on server
Run netstat on the server to see which ports are open.
If port 22 is not LISTENING then the ssh daemon is not setup properly.
I am unable to connect to Secured FTP server Using Filezilla and psfTP too.
While connecting one popup message comes for Certification, then I find this error
Error Message:--
Status: Connecting to idx.XYZ.com...
Response: fzSftp started
Command: open "abc_mnp#idx.XYZ.com" 22
Command: Pass: ****
*Error: Network error: Connection reset by peer
Error: Could not connect to server*
Any Idea guys..
I feel this is an Issue with Server.
I am using Blat that is command line tool for sending the mail from command.
First I run the install command to store the mail server which create the entry in registry like that.........
First I was set the SMTP server to smtp.mail.yahoo.com but the error was same.
After that I execute
blat C:\temp.txt -to abcdef#gmail.com -superdebug
After that this error I got.......
C:\blat310\full>blat C:\temp.txt -to abcdef#gmail.com -superdebug
Blat v3.1.0 (build : Feb 2 2013 11:00:32)
32-bit Windows, Full, Unicode
Checking option -to
superDebug: init_winsock(), WSAStartup() returned 0 (NO_ERROR)
superDebug: Hostname <smtp.mail.apac.gm0.yahoodns.net> resolved to ip address 10
6.10.167.87
superDebug: Official hostname is smtp.mail.apac.gm0.yahoodns.net
superDebug: Attempting to connect to ip address 106.10.167.87
superDebug: ::connect() returned error 10060, retry count remaining is 1
superDebug: ::connect() returned error 10060, retry count remaining is 0
superDebug: Connection returned error 10060
Error: Can't connect to server (timed out if winsock.dll error 10060)
superDebug: ::say_hello() failed to connect, retry count remaining is 1
superDebug: init_winsock(), WSAStartup() returned 0 (NO_ERROR)
superDebug: Hostname <smtp.mail.apac.gm0.yahoodns.net> resolved to ip address 10
6.10.167.87
superDebug: Official hostname is smtp.mail.apac.gm0.yahoodns.net
superDebug: Attempting to connect to ip address 106.10.167.87
superDebug: ::connect() returned error 10060, retry count remaining is 1
superDebug: ::connect() returned error 10060, retry count remaining is 0
superDebug: Connection returned error 10060
Error: Can't connect to server (timed out if winsock.dll error 10060)
Error 10060 means that your connection times out, which is because there's nothing listening on port 995 on either smtp.mail.yahoo.com or smtp.mail.apac.gm0.yahoodns.net. Why do you try to connect to that port anyway? It's used for POP3 over SSL (i.e. mail retrieval), not for SMTP (mail submission).
Try either port 25 or (more likely) port 587. The latter is the default port for message submission (see RFC 4409 for details).
Your 10060 timeout error is most likely being caused by your mail server not listening to the
Blat default SMTP port # 25.
Many ISP mail servers have switched to SSL encryption for authenication. This switch means using SMTP port # 465. HOWEVER, Blat currently doesnot support SSL.
You will either have to:
ask your ISP mailserver to open non-SSL communication, or
get an SSL wrapper for Blat( like Stunnel ), or
find another command line mailer program that does support SSL.