Why doesn't the HW100 VIPNet Coordinator work in the ISP's VLAN?

Question

Network administration

After replacement at one of the remote points (conditionally: point 1) of the VIPNet coordinator HW100C due to a boot disk failure, another replacement HW100C coordinator does not connect to the VIPNet network. The connection is made via vlan leased from the provider. Physically, the connection from the remote point is provided by an adsl modem. From the server side - optics. Without a coordinator at point 1, there is a connection with the server.
At the same time, about 20 HW100C coordinators normally work through the same vlan, through adsl modems, but at other points.
What was checked:

• Checked firmware versions in a working at another point and a replacement HW100C. Everything matches.
  
• Checked the iplir config differences between the HW100C running at a different point and the replacement HW100C. No differences found. Of course, besides the fact that they are different VIPNet nodes.
  
• Replacement HW100C in the local network of the organization (in the server) works without problems. It performs all its functions with the settings of the VIPNet node of point 1.
  
• The replacement HW100C connected to another remote point with an adsl modem and a working coordinator. The result is the same - there is no connection to the central coordinator
  
• On the central coordinator to which all other coordinators connect in Wireshark, packets were viewed from the replacement coordinator without any errors and to the correct port 55777. There was no packet fragmentation. At the same time, packet fragmentation is not prohibited by the provider.
  
• For the experiment, different coordinator connection settings were tested: direct connection, with static firewall, dynamic firewall, direct all traffic through the central coordinator - no connection to the coordinator
  

Are there any solutions to the problem, or recommendations what else can be checked?

Answer 1

Although the question was asked more than a year ago, since there was no answer, I recommend checking the time difference for PAKs, this often has problems ...