Did NAT-T actually kick-in when you were being NAT-ed to the 192.168.x.x alone? You can verify it by checking the 'get sa' output. The port number would show 4500, instead of 500.
You may want to enable NAT-T on the remote peer device as well.
↧
Channel:
All ScreenOS Firewalls (NOT SRX) posts
X
Are you the publisher?
Claim or
contact us
about this channel.
X
0
Channel Details:
- Title: All ScreenOS Firewalls (NOT SRX) posts
- Channel Number: 58457488
- Language: English
- Registered On: January 22, 2016, 8:28 pm
- Number of Articles: 2577
- Latest Snapshot: October 21, 2020, 2:51 am
- RSS URL: http://forums.juniper.net/jnet/rss/boardmessages?board.id=firewalls
- Publisher: https://forums.juniper.net/t5/ScreenOS-Firewalls-NOT-SRX/bd-p/Firewalls
- Description: All ScreenOS Firewalls (NOT SRX) posts
- Catalog: //screenos5.rssing.com/catalog.php?indx=58457488
© 2026 //www.rssing.com