Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Network Connect users cannot access internal resources

0

0

Article ID: KB11568 KB Last Updated: 11 Aug 2010Version: 3.0
Summary:
Network Connect clients are unable to access internal resources if the IP pool defined on IVE for network Connect users is on a different subnet compared to IVE's internal interface subnet.
Symptoms:
Network Connect clients are unable to access internal resources if the IP pool defined on IVE for network Connect users is on a different subnet compared to IVE's internal interface subnet. This is because when the internal resources may not know how to route packets back to IVE 's internal interface.

Solution:
To work around this, add a static route to the router between the internal interface’s network and the internal resource network. This static route will route packets destined for the IVE’s Network Connect IP Pool to the IVE’s internal interface.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search