LANCOM 7111 VPN – LANCOM 8011 VPN
Chapter 5: Linking two networks
46
EN
DNS access to the remote LAN
Thanks to DNS, it is not only possible to access remote computers in a TCP/IP
network via their IP address, but also by using freely defined names.
For example, the computer with the name 'pc1.branch.company' (IP
10.0.2.10) will not only be able to access the server of the head office via its
IP address, but also via its name, 'server.head.company'. The only precondi-
tion: the domain of the remote network in the wizard must be specified.
The domain can only be specified in the LANconfig wizard. In
WEBconfig, enter the appropriate information later in the expert con-
figuration. For more information, see the LANCOM router reference
manual.
Extranet VPN
Finally, one can decide whether access to local stations is permitted. In this
'Extranet VPN' operating mode, the IP stations do not expose their IP address
to the remote LAN, rather they will be hidden behind the VPN gateway's IP
address instead.
Therefore, the stations within the remote LAN cannot access IP stations in the
other LAN directly. For example, if a headquarters. LAN in 'Extranet VPN'
mode is hidden behind its gateway's address '10.10.2.100', and on of its IP
stations (e.g. '10.10.2.13') accesses the IP station '10.10.1.2' of the branch
office, then the branch office.s IP stations deems to be a accessed by
'10.10.2.100'. The true IP address of the accessor ('10.10.2.13') is hidden.
If two LANs shall be coupled in Extranet mode, please ensure to enter the
'outbound' Extranet IP address of the remote site, not its Intranet address.
According to the example, this was '10.10.2.100'. The appropriate netmask
for the Extranet IP address would be '255.255.255.255' then.
5.1.3
Settings for the IPX router
The coupling of IPX networks via VPN cannot be configured using the
wizard. It can only be set up in the expert configuration. For details,
please see the reference manual.
Coupling two typical IPX networks to form a WAN requires three IPX network
numbers:
