zNetLaB › Guided labs › Security
Troubleshoot: SRX server that does not answer
Security Advanced 4 devices 2 checked tasks 100 points Plan lab
Users get out through the SRX, but the internet host cannot reach the published server on 203.0.113.50. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
Users get out through the SRX, but the internet host cannot reach the published server on 203.0.113.50.
Your role: a security engineer. Level: Advanced Done when: all 2 goals show as passed (100 points).
Network status
Devices: 3 PCs, 1 router, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. IN is a host with 192.168.1.10/24, gateway 192.168.1.1. OUT is a host with 203.0.113.20/24, gateway 203.0.113.1. SRV is a host with 192.168.2.20/24, gateway 192.168.2.1. FW starts with an empty configuration.
Known problems
The network worked and now does not: the scenario above says what users report. The cause is a configuration fault, not a cable. Find it with show commands (interfaces, routes, neighbours, running-config) before you change anything; fix only what is wrong.
Goals
The static rule maps to the server (40 pts) The internet host reaches 203.0.113.50 (60 pts)
The activity, in order
The static rule maps to the server The rule translates to 192.168.2.21, an address nobody owns. Set static-nat prefix 192.168.2.20/32.Why: Each goal is a state the lab can check on the running device. Verify with: show security nat static rule all The internet host reaches 203.0.113.50 With the right inside address the existing policy lets it through.Why: Each goal is a state the lab can check on the running device. Verify with: show security flow session
Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong.
Why this matters
Users get out through the SRX, but the internet host cannot reach the published server on 203.0.113.50.
What you will be able to do
The static rule maps to the server
The internet host reaches 203.0.113.50
The network
PC, SRX300 — 4 devices in all, already cabled.
Fa0 ge-0/0/1 Fa0 ge-0/0/0 Fa0 ge-0/0/2 IN 192.168.1.10/24 · gw 192.168.1.1 FW OUT 203.0.113.20/24 · gw 203.0.113.1 SRV 192.168.2.20/24 · gw 192.168.2.1 Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
IN PC 192.168.1.10 / 255.255.255.0 gw 192.168.1.1
FW SRX300 configure it
OUT PC 203.0.113.20 / 255.255.255.0 gw 203.0.113.1
SRV PC 192.168.2.20 / 255.255.255.0 gw 192.168.2.1
Cabling
IN Fa0 ↔ FW ge-0/0/1
OUT Fa0 ↔ FW ge-0/0/0
SRV Fa0 ↔ FW ge-0/0/2
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
FW configure
set interfaces ge-0/0/0 unit 0 family inet address 203.0.113.1/24
set interfaces ge-0/0/1 unit 0 family inet address 192.168.1.1/24
set interfaces ge-0/0/2 unit 0 family inet address 192.168.2.1/24
set security zones security-zone trust interfaces ge-0/0/1.0 host-inbound-traffic system-services ping
set security zones security-zone trust interfaces ge-0/0/2.0
set security zones security-zone untrust interfaces ge-0/0/0.0
set security policies from-zone trust to-zone untrust policy ALLOW match source-address any destination-address any application any
set security policies from-zone trust to-zone untrust policy ALLOW then permit
set security nat source rule-set RS from zone trust
set security nat source rule-set RS to zone untrust
set security nat source rule-set RS rule R1 match source-address 192.168.1.0/24
set security nat source rule-set RS rule R1 then source-nat interface
set security nat static rule-set ST from zone untrust
set security nat static rule-set ST rule WEB match destination-address 203.0.113.50/32
set security nat static rule-set ST rule WEB then static-nat prefix 192.168.2.21/32
set security policies from-zone untrust to-zone trust policy IN match source-address any destination-address any application any
set security policies from-zone untrust to-zone trust policy IN then permit
commit
exit
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 The static rule maps to the server 40 On FW: show security nat static rule all output matches 192\.168\.2\.20.
2 The internet host reaches 203.0.113.50 60 On OUT: ping 203.0.113.50 must succeed.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
FW configure
set security nat static rule-set ST rule WEB then static-nat prefix 192.168.2.20/32
commit
exit
Related labs
Where to start
The lessons are open to everyone, all guided labs are listed by track, and
plans explains what is free and what is not.
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.
Try the simulator in your browser, no sign-up