You are viewing limited content. For full access, please sign in.

Question

Question

Weblink High Latency after Server moved to DMZ

asked on July 5, 2016

I setup the Weblink server in our local Server VLAN.  We tested it for a few weeks with no problems.  I moved the Weblink server to our DMZ VLAN for public access.  I had to add several servers to the Weblink HOSTS file to ensure proper routing.  After updating the HOSTS file the "Test Connection" option began to connect.  Extremely high latency errors now pop up.

I found a Laserfiche article regarding High Latency Environments.  I disabled the reverse DNS lookup as mentioned in the article.  I saw no immediate improvement.  The servers remained up over the three day weekend.  Today the Test Connection shows significant reduction in latency connecting back to the main server.  Many tests now simply show Successful.  

When I launch Weblink on the Weblink server, I receive a “Could not Connect to Sever” Weblink error page.  I've moved the Weblink server back into our Server VLAN.  Commented out the HOSTS file.  All works normally as before.  I move Weblink back into the DMZ VLAN.  Re-enable the HOSTS listings (nothing works without them).  Same Could not Connect to Server error message.

Using ICMP Pings at 1500kb packets at 100 count between servers.  I see sub 5ms trips.  There is only one hop between servers.  The firewall is not blocking traffic.  Testing with telnet on port 80 and 5051. (I never setup HTTPS 443 is not listening on the main server).

I am at a loss to explain why this is not working. The IP ranges are different between the two VLANS.  Was there something in the initial setup on the Weblink Server that I am missing?

0 0

Replies

replied on July 5, 2016

I don't know what could be wrong with your setup, but a tool like Wireshark can give you some more insight into why connections are failing.  Running a capture on WebLink and LFS at the same time can show if the latency is introduced by the network.

1 1
replied on April 9, 2020

did you ever find a fix to this?? Having the same issue out of no where. This has been working for years..

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.