local network web pages load too slow..

[tryllz]

Hi,

I have 2 networks, 192.168.28.0 (in VMware Workstation) and 10.0.64.0 (on a physical Dell Server). Both networks have 3 ESXi and 3 Windows VM in each. Both are behind their respective firewalls, the network between firewalls is 192.168.1.0.



I'm trying trying to access 10.0.64.0 network's ESXi login page from a Windows VM in 192.168.28.0, and vice versa and they seem to be just too slow to load. The following is the loading pages in seconds in each Windows VM.

Code: [Select]

Loading 10.0.64.74 login page on:

192.168.28.40 - 80 secs
192.168.28.41 - 110 secs
192.168.28.43 - 110 secs

Loading 192.168.28.74 login page on:

10.0.64.40 - 110 secs
10.0.64.41 - 90 secs
10.0.64.43 - 93 secs
I also checked at different times, the time to load the login page varies from time to time but takes nearly between 60 - 90 or more to load the login pages.

A trace route to see the route packets take.

ESXi Server to Windows Server

Code: [Select]

[root@esxi1s:~] traceroute 192.168.28.40
traceroute to 192.168.28.40 (192.168.28.40), 30 hops max, 40 byte packets
1 10.0.64.67 (10.0.64.67) 0.796 ms 0.869 ms 0.685 ms
2 192.168.1.21 (192.168.1.21) 2.187 ms 2.747 ms 2.874 ms
3 servermdc (192.168.28.40) 3.475 ms 3.752 ms 3.408 ms

Windows Server to ESXi Server

Code: [Select]

tracert 10.0.64.74
Tracing route to esxi1s.vlab.lab [10.0.64.74]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.28.35
2 3 ms 3 ms 3 ms 192.168.1.31
3 3 ms 3 ms 3 ms esxi1s.vlab.lab [10.0.64.74]
What else can I check in the firewall to determine the source of the problem.

Could it be the rules ?, or DNS misconfiguration ?

Thank You

[bartjsmit]

ESXi needs DNS configured correctly for speedy operation. Also make sure you are authoritative for the reverse zones of your networks and that your servers have PTR records in them.

After that, try again with https://my.esxi.fqdn/ui instead of the IP address.

Bart...

[tryllz]

ESXi needs DNS configured correctly for speedy operation. Also make sure you are authoritative for the reverse zones of your networks and that your servers have PTR records in them.

After that, try again with https://my.esxi.fqdn/ui instead of the IP address.

Bart...

The DNS is configured correctly, PTR records exist as well, and DNS can resolve both forward and reverse lookups, I tested via command in Windows and via DCUI as well.

I'll check the authoritative part.

Whether I access by FQDN or IP, either way the pages load slowly.

Thanks Bart..

[tryllz]

Seemingly I found the source of the problem by capturing packets and analyzing in WireShark.

There seem to be too many Out-Of-Order and Retransmission TCP packets, any one having any idea as to why.

https://we.tl/t-FaqwAYkBNJ