Network Related Issue - Sites Initially Slow to Load

There are several workstations, not all, on the same subnet that are experiencing the same issue. We also have some servers on another subnet also experiencing this issue. Again, not all servers on this subnet. For the sake of security, I’ve changed the subnets here.

• – Offsite
• – Onsite Workstations
• – Onsite Servers

Workstations on subnet, are initially slow to load certain websites. I’ve run PING tests from several workstations and found that it takes approximately 30-45 seconds before I finally see successful PINGs. I used the “-t” and “-4” parameters during these tests. One site I noticed the issue on is Once I get a successful connection, the site is fine. After about 5 minutes, the issue surfaces once again. I see this same issue with servers on subnet to the offsite subnet If I take the same workstation experiencing this issue and place it on the subnet, the issue disappears.

This is especially critical, because backup jobs run onsite to offsite. Some jobs fail because of this issue. I have to login to the backup server on and run a PING test with the parameters “-t -4” to the repository on Once running continuously with successful PINGs, I can then run the backup job and it will run successfully.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Download a copy of Axence Net Tools and get some data
Fred MarshallPrincipalCommented:
It rather sounds like a DNS issue.  Once it's resolved and cached then it works.  Before it's resolved and cached, it's very slow.

I would run DNS Workbench:
It's easy and you get some insight into DNS performance.

Are there DNS address differences between the slow computers and the normal computers?
David FavorLinux/LXD/WordPress/Hosting SavantCommented:
What OS are you running, so people know what type of debug tools you can use.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

DP230Network AdministratorCommented:
Did you check the devices, such as Switch cor Router? Are they okay?
mario00Author Commented:
We are running Windows 7, 10, 2008, 2012. I will check out those tools and report my findings.
mario00Author Commented:
Specifically, I have two workstations that I am working on ( and is a Windows 10 64-bit. is a Windows 7 64-bit. does not experience this issue, while does. I swapped the cables on the switch for the two workstations, and the issue does not follow. still has the same issue. Now, while on the subnet, the issue disappears. This tells me it cannot be a DNS issue, nor a switch issue. Furthermore, we do have other Windows 7 64-bit workstations that do have this issue. So, it is not related to the OS.
Fred MarshallPrincipalCommented:
You tell us that there is a computer with IP address that has the problem.
Then you say:
while on the subnet, the issue disappears
But exactly HOW did this computer "get on the subnet".  I am focused on DNS here and interested in knowing the DNS addresses that are in use.  So knowing the NIC settings in both subnet cases could be revealing.
mario00Author Commented:
To answer your question, the jack feeding the workstation was moved from the subnet to the subnet on the switches. The is a different switch than the subnet.

A new development - I statically assigned a new IP address for four workstations experiencing this issue to different addresses on the subnet (e.g., became The issue disappeared. Then, I statically assigned to a workstation on the same subnet NOT experiencing the issue, and the issue followed.
mario00Author Commented:
All workstations are using the same DNS servers, and there are no duplicate entries for different workstations.
Fred MarshallPrincipalCommented:
I remain confused about this because I can't tell which addresses are being used overall.
I don't see how moving a cable to a different subnet than that which matches the NIC settings can work at all.  
There may be some routing ... ?
It appears that has a problem but I don't know how it's connected and still don't know its DNS address - only that they are "all the same" which isn't much help for *me*.
It would really help if the information for the errant computers were more complete:
- which physical subnet is it connected to and what is the subnet network address?
- what are the ipv4 settings for IP, subnet mask, gateway, DNS servers?
mario00Author Commented:
This image shows the actual IPs and subnets, DNS servers, and DHCP server. Also, to the right of the IPCONFIG output is the associated PING test.
mario00Author Commented:
We created a new scope in our DHCP server that excludes the problematic IPs. Forced each workstation to grab a new one.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mario00Author Commented:
Hearing of possible DNS issue led us to look into the DHCP server as well, which is where we found and fixed the problem.
Fred MarshallPrincipalCommented:
Good to hear it's fixed!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.