Juniper (NetScreen) Firewall, PPTP stopped working after upgrade

You should be using the NetScreen-Remote client. But you might be using PPTP since the VPN client does not yet support Vista.

Anyway, in the upgrade to v5.4.0R6, I found that PPTP into a MIP of the Firewall was no longer working.

PPTP is a service installed by default. I created a new service called pptp-custom and put in the correct definition, which is: TCP port 1723, and IP protocol 47. After I replaced the NetScreen "PPTP" with my own "pptp-custom" in the inbound rule, PPTP was able to work again.

I guess the service definition had changed in the upgrade.

Juniper (NetScreen) Firewall - How to configure a traffic shaping policy

1.       You can create a high priority traffic policy for specific
traffic. Please refer following document:
http://Kb.juniper.net/KB4201

2.       You should set the external interface bandwidth to match the internet
pipe (even if there's another 100mbit router hop). Setting up BW greater than or lower than the actual BW can cause
drop in packets due to calculation mismatch. This is how the fw knows what the external limit is.

keywords: bandwidth shaping, QoS, bandwidth limit, guaranteed bandwidth, ScreenOS

"inbound packet failed validation" netscreen

Connecting to NS25 running 5.4R6 using NetScreen-Remote VPN client 8.x.

Seen on NetScreen-Remote log viewer:
"inbound packet failed validation" netscreen

But pings into the network work fine...

Persistent connection from Windows XP home to a domain share

C:\> net use P: \\mydomain\sharename /user:jsmith /savecred /persistent:yes