Symantec 360R Administration Guide - Page 97

Understanding Client-to-Gateway VPN tunnels

Page 97 highlights

Establishing secure VPN connections 97 Configuring Client-to-Gateway VPN tunnels Understanding Client-to-Gateway VPN tunnels Symantec Gateway Security 300 Series supports Client-to-Gateway VPN tunnel configurations. A Client-to-Gateway configuration is created when a workstation, running Symantec Client VPN software, connects to the security gateway from either inside the protected network or from a remote location through the Internet. Note: Wireless clients can use client-to-gateway tunnels to secure their connections. See Symantec Gateway Security 300 Series Wireless Implementation Guide. Once a VPN tunnel is established, remote users can connect to and safely access the resources of the private network, through the Internet, as if the remote workstation was physically located inside the protected network (see Figure 62). Figure 6-2 Client-to-Gateway VPN tunnel configuration Symantec Client VPN (LAN) Symantec Client VPN (WAN) Internet Symantec Gateway Security 300 Series Symantec Client VPN (LAN) Symantec Client VPN (LAN) In this diagram, there is a client that establishes a tunnel remotely (WAN) and three internal clients establishing a tunnel internally (LAN). For each VPN group, you can define network settings to download to the client during Phase 1 configuration mode. The settings include the primary and secondary DNS servers, the WINS servers, and the primary domain controller. By pushing this information to the clients during configuration mode, each client will not have to configure that on his or her own, saving management time, and reducing the possibility of error.

  • 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
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218

97
Establishing secure VPN connections
Configuring Client-to-Gateway VPN tunnels
Understanding Client-to-Gateway VPN tunnels
Symantec Gateway Security 300 Series supports Client-to-Gateway VPN tunnel
configurations. A Client-to-Gateway configuration is created when a
workstation, running Symantec Client VPN software, connects to the security
gateway from either inside the protected network or from a remote location
through the Internet.
Note:
Wireless clients can use client-to-gateway tunnels to secure their
connections. See
Symantec Gateway Security 300 Series Wireless Implementation
Guide
.
Once a VPN tunnel is established, remote users can connect to and safely access
the resources of the private network, through the Internet, as if the remote
workstation was physically located inside the protected network (see
Figure 6-
2
).
Figure 6-2
Client-to-Gateway VPN tunnel configuration
In this diagram, there is a client that establishes a tunnel remotely (WAN) and
three internal clients establishing a tunnel internally (LAN).
For each VPN group, you can define network settings to download to the client
during Phase 1 configuration mode. The settings include the primary and
secondary DNS servers, the WINS servers, and the primary domain controller.
By pushing this information to the clients during configuration mode, each
client will not have to configure that on his or her own, saving management
time, and reducing the possibility of error.
Symantec Client VPN (WAN)
Internet
Symantec Client VPN (LAN)
Symantec Gateway
Security 300 Series
Symantec Client VPN (LAN)
Symantec Client VPN (LAN)