Differences

This shows you the differences between two versions of the page.

--- remote_service_access [2018/12/07 15:33] – [Adding a VPN connection in service PC's OS] emozolyak
+++ remote_service_access [2022/07/14 13:24] (current) – [Troubleshooting VPN connection for PC with Windows 10] emozolyak
@@ Line 7: / Line 7: @@
 In case the equipment uses a serial port instead of Ethernet, it is enough to install the virtual COM port driver on the computer and use the built-in WebHMI function Virtual COM port. The user can either setup his own VPN network or use the network provided by the Level2 system (recommended).
-{{ ::remoteaccess_jpg.jpg?direct&600 |}}
+{{ network:remoteaccess_jpg.jpg?direct |}}
+===== Connection example =====
 The steps required to implement remote service access are:
@@ Line 20: / Line 22: @@
 First you need to create an account (node) for service PC in Level2 system:
+{{network:create_node_l2_link.png?direct}}
-{{add_and_check_remote_pc.gif}}
+{{network:add_and_check_remote_pc.gif}}
 and make (and then check) its settings:
@@ Line 27: / Line 30: @@
   *mark the //VPN// checkbox in Services tab
   *Remember VPN //login / password// in the Information tab - for further PC VPN connectoin
-  *In the Routing tab, set the node(s) the PC can access and add Virtual IP if you want to access equimpent "behind" the WebHMI (//System with S7-1200 PLC//)
+  *In the Routing tab, set the node(s) this service PC can access and add Virtual IP if you want to access equimpent "behind" the WebHMI using Ethernet interface (//System with S7-1200 PLC//)
 ==== Adding a VPN connection in service PC's OS ====
@@ Line 33: / Line 36: @@
 In Windows 10, press **Win** key and type 'VPN':
-{{ ::vpn_win10_add_1.png?direct&300 |}}
+{{ network:vpn_win10_add_1.png?direct&300 |}}
 Press 'Add a VPN connection':
-{{ ::vpn_win10_add_2.png?direct&912 |}}
+{{ network:vpn_win10_add_2.png?direct&912 |}}
 Edit its settings according to Level2 settings:
-{{::vpn_win10_add_3_modifyed.png?direct}}
+{{network:vpn_win10_add_eng.png?direct}}
 And check adapter properties:
-{{ ::vpn_win10_add_4m.png?direct&600 |}}
+{{ network:vpn_win10_add_4m.png?direct&600 |}}
-{{ ::vpn_win10_add_7_edited.png?direct&600 |}}
+{{ network:vpn_win10_add_7_edited.png?direct&600 |}}
 After checking adapter settings try to connect and then check the connection status:
-{{ ::vpn_win10_connect_arrows.png?direct&400 |}}
+{{ network:vpn_win10_connect_arrows.png?direct&400 |}}
-{{ ::vpn_win10_connected.png?direct&400 |}}
+{{ network:vpn_win10_connected.png?direct&400 |}}
-After connecting PC to the VPN, check
+After connecting the PC to the VPN, "ping" the remote WebHMI node(s), which were allowed to access to in Routing tab:
+{{ network:routing_target_1.png?direct&600 |}}
+You can check its IP in the node's (//System with S7-1200 PLC//) Information tab:
+{{network:check_routing_target_ip.gif}}
 ===== Establishing communication with remote devices behind the gateway via TCP / IP =====
@@ Line 61: / Line 69: @@
 The application structure is given below:
-{{::remote_access_tcp.png?direct}}
+{{network:remote_access_function_tcp_eng.png?direct}}
-You must enable the Virtual IP address function for the specified WebHMI node. Go the Setup / Level2 menu and switch Virtual IPs lever on:
+You must **enable the Virtual IP address function** for the specified WebHMI node. Go the __WebHMI's__ Setup / Level2 menu and switch Virtual IPs lever on:
   -input the remote PLC's IP address it was assigned in that local network (192.168.0.210)
   -save the changes, after that a new VPN IP address for the PLC will be created (10.0.0.206).
-{{::turn_virtual_ip_from_webhmi.png?direct}}
+{{network:turn_virtual_ip_from_webhmi.png?direct}}
 Now when you want to access the remote PLC (in the example we use Siemens S7-1200 PLC), connect your PC to VPN and you should be able to connect your PLCs via these Virtual IPs.
 Here is example how to connect to PLC S7 1200 from TIA Portal.
-Connect your PC to VPN and set the your Virtual IP in the PLC's Ethernet properties:
+Connect your PC to VPN and __type in your Virtual IP in the advanced download/online access dialog box__, as the access Address (in our example, it is 10.0.0.157):
-{{::new_vpn_in_tia.png?direct}}
+{{network:connection_via_subnet.png?direct}}
-  Warning! Don't write this IP address in the HW config of the PLC, you may lose access to it. Only temporarily
+Before this step, check you have a subnet configured for the PLC in its HW Config:
-  change IP for establishing remote session.
+{{network:subnet_in_the-plc.png?direct}}
 ===== Establishing communication with remote devices behind the gateway via a virtual COM port =====
@@ Line 88: / Line 96: @@
 The application structure is given below:
-{{::new_virtual_com_port.png?direct}}
+{{network:new_virtual_com_port.png?direct}}
 Suppose you have some PLC connected to the WebHMI RS-485 port. Go to the connection properties and switch its mode to //Virtual UART//. Remember the TCP port that was assigned to the connection (8001) and VPN IP address of this WebHMI (10.0.0.204).
-{{turn_on_virtual_uart.gif}}
+{{network:turn_on_virtual_uart.gif}}
 Download and setup the driver [[http://www.perle.com/downloads/trueport.shtml | Perle TruePort]] for your OS.
@@ Line 98: / Line 106: @@
 Setup new virtual COM port in your system with the TruePort Management Tool:
-{{perle_mngmt_software.png |}}
+{{network:perle_mngmt_software.png |}}
-{{configuring_virtual_uart.gif}}
+{{network:configuring_virtual_uart.gif}}
 Check this virtual port settings in the Device Manager:
-{{ ::commgr_perle_com2_ed.png?direct&300 |}}
+{{ network:commgr_perle_com2_ed.png?direct&300 |}}
 Connect your PC to the VPN, and use "virtual" __COM2__ as a communication port in the PLC programming software.
-{{ ::commgr_perle_com.png?direct&400 |}}
+{{ network:commgr_perle_com.png?direct&400 |}}
+===== Troubleshooting VPN connection for PC with Windows 10 =====
+VPN connection problems were reported sometimes from the Windows 8/10 users. These problems were caused mainly by the following reasons:
+  * Firewall settings.
+  * Security policy for certain types of VPN traffic in corporate networks.
+  * Windows policy for L2TP connections withoun encryption. This one can be fixed with the following registre keys:
+{{ :network:vpn:vpn-w10-faq.png?direct&800 |}}