Differences

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

--- remote_service_access [2020/03/17 09:51] – [Establishing communication with remote devices behind the gateway via TCP / IP] 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:
-{{create_node_l2_link.png?direct}}
+{{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 34: / 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_eng.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 the PC to the VPN, "ping" the remote WebHMI node(s), which were allowed to access to in Routing tab:
-{{ ::routing_target_1.png?direct&600 |}}
+{{ network:routing_target_1.png?direct&600 |}}
 You can check its IP in the node's (//System with S7-1200 PLC//) Information tab:
-{{check_routing_target_ip.gif}}
+{{network:check_routing_target_ip.gif}}
 ===== Establishing communication with remote devices behind the gateway via TCP / IP =====
@@ Line 67: / Line 69: @@
 The application structure is given below:
-{{::remote_access_function_tcp_eng.png?direct}}
+{{network:remote_access_function_tcp_eng.png?direct}}
@@ Line 75: / Line 77: @@
   -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.
@@ Line 81: / Line 83: @@
 Here is example how to connect to PLC S7 1200 from TIA Portal.
-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):
+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):
-{{::connection_via_subnet.png?direct}}
+{{network:connection_via_subnet.png?direct}}
 Before this step, check you have a subnet configured for the PLC in its HW Config:
-{{::subnet_in_the-plc.png?direct}}
+{{network:subnet_in_the-plc.png?direct}}
 ===== Establishing communication with remote devices behind the gateway via a virtual COM port =====
@@ Line 94: / 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 104: / 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 |}}