Hot answers tagged connection-refused
Have you checked that your my.cnf settings are correct? If you have specified "bind-address = 127.0.0.1" in the my.cnf Then your MySQL - server only listens localhost and does not allow remote-connections. It is the default settings in modern MySQL installions.
But I don't understand, a server by definition shouldn't have any closed port and I can't find a way to see if they are. I think you are slightly mistaken. A server, by definition, serves. What it serves is chosen by the server administrator. Technically, a server can have all of its ports closed, although that wouldn't be a very useful server... ...
It looks like there is something upstream of your VPS that is blocking access except for the ports noted. You should contact your VPS provider and ask them about it.
As others have already suggested make sure your cassandra instance is running ps axu | grep cassandra If the output tells you that it is running you can check what ports it is listening on: netstat -tulpn | grep -i listen | grep <pid> where is the process id of your cassandra instance which you can get from the output of the first command. You ...
The PREROUTING chain doesn't apply to local (loopback) traffic. You will need a redirect rule in the OUTPUT chain for it to work on the local system. For example: iptables -t nat -A OUTPUT -i lo -p tcp --dport 80 -j REDIRECT --to-port 8000
Yes. You can set the maximum number of simultaneous users who can connect to the Share. You can do this in the properties of the Share. Have a read here: http://technet.microsoft.com/en-us/library/cc753521.aspx Not that these settings exist in every version/edition of Windows that I'm aware of (since you didn't specify it in your question).
To view your firewall settings in a terminal perform the following: - sudo iptables -L -n you looking for somehting ike this # iptables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp -- anywhere anywhere tcp dpt:ssh DROP all -- anywhere anywhere if no ...
Port 22: Connection Refused This message indicates that a firewall is actively blocking your connection attempt or alternatively that sshd is not listening on that port. Verify that: The iptables rules applied on boot allow traffic on port 22 sshd is set to start on boot
Okay, to make things clear - if you are running CentOS, chances are that you are at release 5 with sendmail as the default. In that case, you will not be to connect externally, because sendmail will only listen to localhost by default. To make it listen on the main IP, you will need to disable the line in /etc/sendmail.mc from this: ...
Only top voted, non community-wiki answers of a minimum length are eligible