HP BladeSystem bc2000 Cisco VPN Support for HP Thin Clients and Blade PCs - Page 22

the VPN tunnel.

Page 22 highlights

7. At this point, the internal network is fully accessible via IP tunnel. We can validate this initially by pinging an address from the private network. For this reference implementation, there is a Cisco NAC appliance at 10.3.3.3., so let's make sure there is connectivity by opening a command prompt and directly pinging (shown below). 8. Run the ipconfig command to verify that the new IP address of the tunnel is in the 10.2.2.x subnet, as specified in the previous CAS configuration steps. The VPN connection can be terminated via the taskbar icon. Right-click and select to disconnect the VPN tunnel. NOTE: depending on the setting chosen within the VPN configuration process, the local network may not be accessible while the VPN tunnel is active. This is actually a preferred feature to prevent inadvertently bridging public and private networks by any client. 22

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25

22
7.
At this point, the internal network is fully accessible via IP tunnel. We can validate this initially
by pinging an address from the private network. For this reference implementation, there is a
Cisco NAC appliance at 10.3.3.3., so let’s make sure there is connectivity by opening a
command prompt and directly pinging (shown below).
8.
Run the
ipconfig
command to verify that the new IP address of the tunnel is in the 10.2.2.x
subnet, as specified in the previous CAS configuration steps.
The VPN connection can be terminated via the taskbar icon. Right-click and select to disconnect
the VPN tunnel.
NOTE: depending on the setting chosen within the VPN configuration process, the local
network may not be accessible while the VPN tunnel is active. This is actually a preferred
feature to prevent inadvertently bridging public and private networks by any client.