If you're experiencing issues with your NG Firewall and it is not passing any traffic, run these tests to see where we can narrow down the issue:
On The NG Firewall
- Use the connectivity test, Does it succeed?
- Using the ping test, can it ping NG Firewall's gateway?
- Using the ping test, can it ping 220.127.116.11?
- Using the ping test, can it ping google.com?
- Using the connection test, can it connect to google.com port 80?
On a Client Behind NG Firewall
- Can the PC ping NG Firewalls internal IP? (doesn't apply for bridge mode)
- Can the PC ping NG Firewall's external IP?
- Can the PC ping NG Firewall's gateway?
- Can the PC ping 18.104.22.168?
- Can the PC perform DNS lookups? (Open a command window and run 'nslookup google.com' or 'host google.com')
- Can the PC ping google.com?
- Can the PC open a browser to google.com?
- Can the PC open a browser to NG Firewall's internal administration interface?
On a Machine Outside the Network (if available)
- Can the machine ping NG Firewall's gateway IP?
- Can the machine ping NG Firewall's external IP?
- Can the machine open a browser to the https administration on NG FIrewall(if enabled)?
You can use these tests to narrow issue down to an issue that is either caused on the internal side of NG Firewall or the external. Once you have determined which side of the NG Firewall that issue is coming from, take a step-by-step approach and test each networking device for functionality in that direction (i.e. upstream or downstream). If you're having issues finding the issue, feel free to contact support and we'll do what we can to help. But please make sure you have the answers to these questions as these will be the first questions asked.