Screen OS

Hello,

I am following the directions at http://kb.juniper.net/InfoCenter/index?page=content&id=KB4740 to setup a port forward for TCP port 80 to our internal web server, and TCP port 3389 for RDP to our server. Neither of which are working. For TCP port 80, when attempting to create the VIP on the Untrusted interface, I hit OK and I receive the message: http://i.imgur.com/Hs0JK.png

Then I portscan my IP from my office location and only port 80 appears to be open, but when I connect using the IP address, it times out.

For TCP 3389, I create the custom service, follow the same directions I linked above, and I still cannot see port 3389 open, nor connect via RDP from my office.

What's going on?

Config:

unset key protection enable
set clock ntp
set clock timezone -5
set clock dst recurring start-weekday 2 0 3 02:00 end-weekday 1 0 11 02:00
set vrouter trust-vr sharable
set vrouter "untrust-vr"
exit
set vrouter "trust-vr"
unset auto-route-export
exit
set service "Remote Desktop Protocol" protocol tcp src-port 0-65535 dst-port 3389-3389 
set service "Remote Desktop Protocol" + udp src-port 0-65535 dst-port 3389-3389 
set alg appleichat enable
unset alg appleichat re-assembly enable
set alg sctp enable
set auth-server "Local" id 0
set auth-server "Local" server-name "Local"
set auth default auth server "Local"
set auth radius accounting port 1646
set admin name "netscreen"
set admin password "naw-son"
set admin auth web timeout 10
set admin auth dial-in timeout 3
set admin auth server "Local"
set admin format dos
set zone "Trust" vrouter "trust-vr"
set zone "Untrust" vrouter "trust-vr"
set zone "DMZ" vrouter "trust-vr"
set zone "VLAN" vrouter "trust-vr"
set zone "Untrust-Tun" vrouter "trust-vr"
set zone "Trust" tcp-rst 
set zone "Untrust" block 
unset zone "Untrust" tcp-rst 
set zone "MGT" block 
unset zone "V1-Trust" tcp-rst 
unset zone "V1-Untrust" tcp-rst 
set zone "DMZ" tcp-rst 
unset zone "V1-DMZ" tcp-rst 
unset zone "VLAN" tcp-rst 
set zone "Untrust" screen tear-drop
set zone "Untrust" screen syn-flood
set zone "Untrust" screen ping-death
set zone "Untrust" screen ip-filter-src
set zone "Untrust" screen land
set zone "V1-Untrust" screen tear-drop
set zone "V1-Untrust" screen syn-flood
set zone "V1-Untrust" screen ping-death
set zone "V1-Untrust" screen ip-filter-src
set zone "V1-Untrust" screen land
set interface "ethernet0/0" zone "Untrust"
set interface "ethernet0/1" zone "DMZ"
set interface "bgroup0" zone "Trust"
set interface bgroup0 port ethernet0/2
set interface bgroup0 port ethernet0/3
set interface bgroup0 port ethernet0/4
set interface bgroup0 port ethernet0/5
set interface bgroup0 port ethernet0/6
unset interface vlan1 ip
set interface ethernet0/0 ip 173.188.155.73/25
set interface ethernet0/0 route
set interface ethernet0/1 ip 192.168.0.1/24
set interface ethernet0/1 nat
set interface bgroup0 ip 192.168.1.1/24
set interface bgroup0 nat
unset interface vlan1 bypass-others-ipsec
unset interface vlan1 bypass-non-ip
set interface ethernet0/0 ip manageable
set interface ethernet0/1 ip manageable
set interface bgroup0 ip manageable
set interface bgroup0 manage mtrace
set interface ethernet0/0 vip interface-ip 3389 "Remote Desktop Protocol" 192.168.1.3
set interface ethernet0/0 dhcp client enable
unset interface ethernet0/0 dhcp client settings update-dhcpserver
set interface "serial0/0" modem settings "USR" init "AT&F"
set interface "serial0/0" modem settings "USR" active
set interface "serial0/0" modem speed 115200
set interface "serial0/0" modem retry 3
set interface "serial0/0" modem interval 10
set interface "serial0/0" modem idle-time 10
set flow tcp-mss
unset flow tcp-syn-check
unset flow tcp-syn-bit-check
set flow reverse-route clear-text prefer
set flow reverse-route tunnel always
set pki authority default scep mode "auto"
set pki x509 default cert-path partial
set address "Trust" "192.168.1.3/24" 192.168.1.3 255.255.255.0
set address "Trust" "192.168.1.3/32" 192.168.1.3 255.255.255.255
set address "Untrust" "192.168.1.3/24" 192.168.1.3 255.255.255.0
set crypto-policy
exit
set ike respond-bad-spi 1
set ike ikev2 ike-sa-soft-lifetime 60
unset ike ikeid-enumeration
unset ike dos-protection
unset ipsec access-session enable
set ipsec access-session maximum 5000
set ipsec access-session upper-threshold 0
set ipsec access-session lower-threshold 0
set ipsec access-session dead-p2-sa-timeout 0
unset ipsec access-session log-error
unset ipsec access-session info-exch-connected
unset ipsec access-session use-error-log
set vrouter "untrust-vr"
exit
set vrouter "trust-vr"
exit
set url protocol websense
exit
set policy id 1 from "Trust" to "Untrust"  "Any" "Any" "ANY" permit 
set policy id 1

exit
set policy id 2 name "Test" from "Untrust" to "Trust"  "Any" "192.168.1.3/24" "HTTP" permit 
set policy id 2
exit
set policy id 3 name "RDP" from "Untrust" to "Trust"  "Any" "192.168.1.3/24" "Remote Desktop Protocol" permit 
set policy id 3
exit
set nsmgmt bulkcli reboot-timeout 60
set ssh version v2
set config lock timeout 5
unset license-key auto-update
set telnet client enable
set ntp server "192.168.1.3"
set ntp server src-interface "ethernet0/6"
set ntp server backup1 "192.168.1.2"
set ntp server backup1 src-interface "ethernet0/6"
set ntp max-adjustment 90
set snmp port listen 161
set snmp port trap 162
set vrouter "untrust-vr"
exit
set vrouter "trust-vr"
unset add-default-route
exit
set vrouter "untrust-vr"
exit
set vrouter "trust-vr"
exit

For the port 80 issue, you could unset management on the untrust interface:

unset interface ethernet0/0 ip manageable

 -- or --

You can leave management enabled on the untrust interface, and just set a different port number for web management (other than 80).

For the policy issue, you just need to change the security policies to reference the interface VIP as the destination address, not the internal IP.

So, instead of this:

set policy id 3 name "RDP" from "Untrust" to "Trust"  "Any" "192.168.1.3/24" "Remote Desktop Protocol" permit

You would have this:

set policy id 3 name "RDP" from "Untrust" to "Trust"  "Any" "VIP(ethernet0/0)" "Remote Desktop Protocol" permit

Thanks! That worked. Though for the TCP port 80 issue, I still had to change the management port to 8080 using the web gui for it to allow me to add the VIP service. It's working now, though.

Also, do you recommend upgrading my SSG5 to ScreenOS 6.3?

Will it reset any settings that would cause me to need to be onsite to reset? I am currently remotely managing the device via the Windows Server at their location.

---

@TC10284 wrote:

Also, do you recommend upgrading my SSG5 to ScreenOS 6.3?

Will it reset any settings that would cause me to need to be onsite to reset? I am currently remotely managing the device via the Windows Server at their location.

---

6.3 is the current JTAC recommended release.  I try to stay within recommended releases as much as possible, however, there's a strong case for "if it ain't broke, don't fix it."

I would recommend you review the release notes for the 6.3 release and see if it adds any features that you feel you need to have. Also check the End Of Life date for the version that you're running to see when the version you're running is being retired. If the version of ScreenOS that you're running meets your needs and is not nearing or past EOS or EOL, then perhaps there's really no reason to upgrade it.

Upgrades always carry some risk.  In most cases, ScreenOS upgrades go smoothly in my experience, but you should always have a backup plan in place in case something goes wrong.