Internet slow

Hi,

We are having issues with Internet, connecting to websites is slow, it started happening last week. We have 7 bonded T1 10 up and 10down and this issue is happening to everyone on out network, I need some help trying to figure out if it is our DNS server (windows 2003) or its ISP. I personally use chrome or Firefox and when going to any website it takes forever to load web page. Please let me know what information  you need to resolve this.
I have also ran full scan of DC, did not find anything.

Thank you for all the help.
LVL 1
Nirav04Asked:
Who is Participating?
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.

mkriszCommented:
To figure this out, please take a speed test. www.speedtest.net you can use this in order to do this. After this, we can know if your ISP is doing something wrong. If not, I would guess maybe your router/NAT is working not correctly.
0
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Try a
nslookup www.somesite.com
and measure the response time. The answer should come almost immediately. Then
ping -n 10 www.somesite.com
should start very quick with the first line, showing the resolved IP address. If this step lasts long, but the following ping times are low (<100ms), you have a DNS issue.
If only the ping times are high, you have most probably some contention or misconfigured internet line.
0
Nirav04Author Commented:
Following are the results

C:\>nslookup www.google.com
Server:  dc2.coll.inc.com
Address:  192.168.2.195

DNS request timed out.
    timeout was 2 seconds.
Non-authoritative answer:
Name:    www.l.google.com
Addresses:  74.125.45.103, 74.125.45.99, 74.125.45.147, 74.125.45.104
Aliases:  www.google.com

C:\>nslookup www.yahoo.com
Server:  dc2.coll.inc.com
Address:  192.168.253.195

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to cmdm-dc2.col.cmpminc.com timed-out

C:\>ping -n 10 www.google.com

Pinging www.l.google.com [74.125.45.99] with 32 bytes of data:

Reply from 74.125.45.99: bytes=32 time=36ms TTL=241
Reply from 74.125.45.99: bytes=32 time=37ms TTL=241
Reply from 74.125.45.99: bytes=32 time=57ms TTL=241
Reply from 74.125.45.99: bytes=32 time=37ms TTL=241
Reply from 74.125.45.99: bytes=32 time=40ms TTL=241
Reply from 74.125.45.99: bytes=32 time=41ms TTL=241
Reply from 74.125.45.99: bytes=32 time=40ms TTL=241
Reply from 74.125.45.99: bytes=32 time=36ms TTL=241
Reply from 74.125.45.99: bytes=32 time=37ms TTL=241
Reply from 74.125.45.99: bytes=32 time=38ms TTL=241

Ping statistics for 74.125.45.99:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 57ms, Average = 39ms

C:\>ping -n 10 www.yahoo.com

Pinging www-real.wa1.b.yahoo.com [69.147.76.15] with 32 bytes of data:

Reply from 69.147.76.15: bytes=32 time=39ms TTL=53
Reply from 69.147.76.15: bytes=32 time=34ms TTL=53
Reply from 69.147.76.15: bytes=32 time=34ms TTL=53
Reply from 69.147.76.15: bytes=32 time=37ms TTL=53
Reply from 69.147.76.15: bytes=32 time=34ms TTL=53
Reply from 69.147.76.15: bytes=32 time=34ms TTL=53
Reply from 69.147.76.15: bytes=32 time=34ms TTL=53
Reply from 69.147.76.15: bytes=32 time=34ms TTL=53
Reply from 69.147.76.15: bytes=32 time=36ms TTL=53
Reply from 69.147.76.15: bytes=32 time=38ms TTL=53

Ping statistics for 69.147.76.15:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 39ms, Average = 35ms


0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Nirav04Author Commented:
Some websites I cannot do nslookup

0
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
ping time is fine, <40ms is very good.

nslookup shows different IP addresses for your DNS server dc2.coll.inc.com. If the 192.168.253.195 is used, no answer comes back.

It would be important to know whether the DNS server address changes with each nslookup, or depends on the domain you ask for.
Further, do you know what both DNS server addresses mean? E.g. one RAS interface, or two NICs, or load balancing entries.
0
Nirav04Author Commented:
Please disregard previous results, I had to edit some info and made mistake following is the new results.

C:\>nslookup www.yahoo.com
Server:  dc2.coll.inc.com
Address:  192.168.2.195

Non-authoritative answer:
Name:    www-real.wa1.b.yahoo.com
Address:  69.147.76.15
Aliases:  www.yahoo.com, www.wa1.b.yahoo.com


C:\>ping -n 10 www.yahoo.com

Pinging www-real.wa1.b.yahoo.com [69.147.76.15] with 32 bytes of data:

Reply from 69.147.76.15: bytes=32 time=14ms TTL=54
Reply from 69.147.76.15: bytes=32 time=14ms TTL=54
Reply from 69.147.76.15: bytes=32 time=14ms TTL=54
Reply from 69.147.76.15: bytes=32 time=15ms TTL=54
Reply from 69.147.76.15: bytes=32 time=14ms TTL=54
Reply from 69.147.76.15: bytes=32 time=14ms TTL=54
Reply from 69.147.76.15: bytes=32 time=14ms TTL=54
Reply from 69.147.76.15: bytes=32 time=14ms TTL=54
Reply from 69.147.76.15: bytes=32 time=14ms TTL=54
Reply from 69.147.76.15: bytes=32 time=14ms TTL=54

Ping statistics for 69.147.76.15:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 15ms, Average = 14ms

C:\>nslookup www.google.com
Server:  dc2.coll.inc.com
Address:  192.168.2.195

DNS request timed out.
    timeout was 2 seconds.
Non-authoritative answer:
Name:    www.l.google.com
Addresses:  74.125.45.104, 74.125.45.147, 74.125.45.103, 74.125.45.99
Aliases:  www.google.com


C:\>ping -n 10 www.google.com

Pinging www.l.google.com [74.125.45.104] with 32 bytes of data:

Reply from 74.125.45.104: bytes=32 time=29ms TTL=246
Reply from 74.125.45.104: bytes=32 time=30ms TTL=246
Reply from 74.125.45.104: bytes=32 time=30ms TTL=246
Reply from 74.125.45.104: bytes=32 time=28ms TTL=246
Reply from 74.125.45.104: bytes=32 time=28ms TTL=246
Reply from 74.125.45.104: bytes=32 time=30ms TTL=246
Reply from 74.125.45.104: bytes=32 time=30ms TTL=246
Reply from 74.125.45.104: bytes=32 time=28ms TTL=246
Reply from 74.125.45.104: bytes=32 time=28ms TTL=246
Reply from 74.125.45.104: bytes=32 time=30ms TTL=246

Ping statistics for 74.125.45.104:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 28ms, Maximum = 30ms, Average = 29ms
0
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Ok, DNS server is the same. Did you notice the difference between both sites? Try again over some time. Is it the same behaviour, i.e.
  • does nslookup to the same address always come with/without timeout?
  • is nslookup of yahoo always faster then of google?
  • are the pings representative?
Again, the ping times are very good, however, the difference puzzles me (if it not depending on traffic or similar).
The different TTLs in your pings are strange. That looks like the packets are walking different router paths. Try a  tracert -w 100 to both addresses, and compare the first three hops (you don't need to post the cleartext result here).
0

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
Nirav04Author Commented:
First of all I am doing all these from my PC, no matter which site I do "NSLOOKUP" it always has "DNS request timed out.    timeout was 2 seconds" do you know why?

I did ping again and results are almost same

C:\>ping www.yahoo.com

Pinging www-real.wa1.b.yahoo.com [69.147.76.15] with 32 bytes of data:

Reply from 69.147.76.15: bytes=32 time=14ms TTL=54
Reply from 69.147.76.15: bytes=32 time=14ms TTL=54
Reply from 69.147.76.15: bytes=32 time=14ms TTL=54
Reply from 69.147.76.15: bytes=32 time=14ms TTL=54

Ping statistics for 69.147.76.15:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 14ms, Average = 14ms

C:\>ping www.google.com

Pinging www.l.google.com [74.125.45.99] with 32 bytes of data:

Reply from 74.125.45.99: bytes=32 time=29ms TTL=246
Reply from 74.125.45.99: bytes=32 time=30ms TTL=246
Reply from 74.125.45.99: bytes=32 time=32ms TTL=246
Reply from 74.125.45.99: bytes=32 time=32ms TTL=246

Ping statistics for 74.125.45.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 32ms, Average = 30ms

C:\>ping www.pcpitstop.com

Pinging pcpitstop.com [64.29.201.21] with 32 bytes of data:

Reply from 64.29.201.21: bytes=32 time=52ms TTL=244
Reply from 64.29.201.21: bytes=32 time=52ms TTL=244
Reply from 64.29.201.21: bytes=32 time=52ms TTL=244
Reply from 64.29.201.21: bytes=32 time=58ms TTL=244

Ping statistics for 64.29.201.21:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 52ms, Maximum = 58ms, Average = 53ms

Not sure TTL on yahoo is 54 and google is 246

0
ChiefITCommented:
Here is an article to understand the path a DNS query takes:

It will help you track down the problem if it is in fact DNS.

http://www.experts-exchange.com/articles/Networking/Protocols/DNS/DNS-Troubleshooting-made-easy.html

Since you are not loosing packets, it is not an MTU or Duplex setting:

I think what I would do is get a bandwidth monitor to make sure you are not under attack with a DDoS attack. Wireshark should show you if you are under attack.

Also check your network switch LEDs for excessive usage.
0
Nirav04Author Commented:
Thank you everyone for all the help, looks like after further troubleshooting issue was with ISP and it was resolved next day.
0
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
DNS

From novice to tech pro — start learning today.