New answers tagged ports
There are a few things that can cause this. Connection problems can be caused by a firewall which blocks all ports beside some that have explicitly been enabled. This is called whitelisting and can possibly cause this problem. Two other posibilities that came to my mind are: In the new network you got an new IP but the socket tries to bind itself to the ...
Well they could hit you with an HTTP attack. They could hit you with a Layer 4 attack, which would drop you even if they hit a closed port. Closing a port does nothing to protect you from DDoS. How can you defend against DDoS attacks? Get a real time WAF such as by http://DDoS-Protection.io (it's free for personal use websites).
An attacker can still use the full range of attacks on the webserver: everything from password guessing to code injection to buffer overflows to path traversal to who-knows-what. The only thing closing non-HTTP ports does is prevent the attacker from going after other programs that might be listening for incoming traffic (eg. a mailserver).
This could be a risk if the telnet service exposed has any vulnerabilities. An example of one here, although the specific vulnerability will depend on the version of telnet used by your router. Another possibility is if the telnet service has any backdoors or default passwords enabled. Similar goes for the DNS service - you shouldn't expose services to the ...
Using the telnet interface over an insecure link (the Internet) is insecure, but simply having it there won't do much harm. The insecurity of telnet comes from its lack of encryption, but it's not an issue if you don't send anything sensitive through it in the first place. However, what is more concerning is the DNS port that is open - it could be abused to ...
The main problem I see is that MySQL does by default not use any enctiption so your username and password will be transfered in plaintext every time your or any application using the MySQL Server connects to the database. You can use MySQL with SSL Support but that whould require some extra work. You can have a look at this to determine if its worth the ...
Have you considered simply blocking the relevant ports at the firewall? Deny access from all external hosts. Using the "Windows Firewall with Advanced Networking" window (wf.msc), edit a rule, go to the Scope tab, and either set it to only work on local IP address 127.0.0.1, or to nor accept connections from any remote computers (or both). You could also add ...
NAT is often misunderstood because in todays "office routers" there is as good as in every case a combination of NAT/PAT and a firewall which isn't the same. Also when you say NAT most people really mean NAT/PAT which is a combination of Network Address Translation and Port Address Translation. This means that the router which is providing NAT/PAT ...
You must think this because NAT is used by a device, which can be a firewall, router or computer that sits between an internal network and the rest of the world. The one main reason to use NAT is the shortage of IP addresses, but I can't recall that security is another reason for using NAT.
NAT does not provide security, it merely allows many private IPv4 address to use one public IPv4 address. It is not a security mechanism. It may provide some obfuscation of internal addresses and assets. But I still would not define it as security layer.
Top 50 recent answers are included