asked on

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.

mkrisz

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.

Qlemo

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.

Nirav04

ASKER

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

Nirav04

ASKER

Some websites I cannot do nslookup

Qlemo

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.

Nirav04

ASKER

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

ASKER CERTIFIED SOLUTION

Qlemo

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Nirav04

ASKER

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

SOLUTION

ChiefIT

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Nirav04

ASKER

Thank you everyone for all the help, looks like after further troubleshooting issue was with ISP and it was resolved next day.