Network & Connectivity
Port Blocked by Firewall
When a network port is blocked by a firewall (host-based, network, or ISP-level), services listening on that port become unreachable from the blocked direction. This can prevent web servers (port 80/443), email (port 25/587), databases, and other services from accepting connections. Port blocking can be intentional (security) or accidental (misconfigured firewall rules).
Symptoms
- Connection refused or timed out to specific ports
- Service works locally but is unreachable from the internet
- telnet to host:port hangs with no response
- Application works on one port but not another
- ISP blocking standard service ports like 25 or 80
Common Causes
- Host firewall (iptables, Windows Firewall) blocking the port
- Cloud security group or network ACL not allowing the port
- ISP blocking common ports (25 for SMTP, 80 for HTTP)
- Intermediate firewall/IDS dropping packets to the port
- Service not actually listening on the expected port
Step-by-Step Troubleshooting
- 1
- 2
Test TCP connectivity
Grab the service banner to verify the service is responding.
- 3
Test from multiple locations
Check if the port is blocked from specific networks or universally.
Use Ping & Traceroute → - 4
Check firewall rules
Review host firewall, cloud security groups, and network ACLs for blocking rules.
- 5
Contact ISP if needed
If the ISP is blocking the port, request an unblock or use an alternative port.
Recommended Diagnostic Tools
Monitor Port Availability
Track critical ports and get alerts if they become blocked.