• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Got new DSL, but things are going down the hill. Ping sucks :( *Solved*

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
okay...i guess i didnt read too closely. see if you are able to swap out the dsl modem/gateway thingie.

maybe you could borrow someone else's dsl modem.

i understand your frustration. i couldnt even deal with the 150ms pings, and you have like 200ms to 600ms.
 
Originally posted by: cerebusPu
okay...i guess i didnt read too closely. see if you are able to swap out the dsl modem/gateway thingie.

maybe you could borrow someone else's dsl modem.

i understand your frustration. i couldnt even deal with the 150ms pings, and you have like 200ms to 600ms.
Click to expand...

It's a modem router. All in one. Each modem is configured specifically for each apt so I can't use my friend's modem router to go online but I can try to borrow it and ping it to see if the problem is over on my pc or something else.
 
traceroute to an IP of a popular URL (if you dont know how to use nslookup)...try running "tracert" in DOS to 216.109.118.64

Paste your traceroute here...let us take a look at it
 
I glanced over the thread, but is 192.168.1.1 your modem / router at your physical location? If so then the sentiment is right about it being a local issue. Try a different CAT-5 cable (again, glanced at the post, if you have already tried that, then forgive me for not reading the entire post). Is the modem / router a Westell, Cayman? Unless its a bridged connection (authentication done by your NICs MAC address) you should be able to use anyones modem / router...you just need to know how to configure them.

Try new NIC
Try new CAT-5
Try new modem / router

The issue is most definitely not on the ISP's side, as your first hop has 300ms latency...typically its a physical issue between your PC and the first hop...The next step I would take would be to run an extended ping to see if you get any packet loss

ping 192.168.1.1 -n 500
and ping that second hop as well -n 500

You may also want to increase the size of the packet your pinging with (alot of times packet loss will not present itself until the packet size is higher then normal).

ping 192.168.1.1 -l 1492 -n 500

(the -l is an L)

ALSO, if you have CAT 5 to the home (apt) you either have a homerun, or fibre to the curb..its doubtful that the apt complex has 1 modem for all those connections...they probably resell access through the local ISP and get some kickback in the process. That link posted in the other thread is an actual DSL modem, not just a router. If they have installed a DSLAM in every apt block, you actually have DSL in your home, not a LAN. so 192.168.1.1 is the LAN side of that modem, and the 69 IP address in the second hop is the IP your ISP has assigned as your WAN IP (either DHCP, statically or via a pool assignment) . BTW, DSLAM = Digital Subscriber Line Access Multiplexor.
 
Originally posted by: BunLengthHotDog
I glanced over the thread, but is 192.168.1.1 your modem / router at your physical location? If so then the sentiment is right about it being a local issue. Try a different CAT-5 cable (again, glanced at the post, if you have already tried that, then forgive me for not reading the entire post). Is the modem / router a Westell, Cayman? Unless its a bridged connection (authentication done by your NICs MAC address) you should be able to use anyones modem / router...you just need to know how to configure them.

Try new NIC
Try new CAT-5
Try new modem / router

The issue is most definitely not on the ISP's side, as your first hop has 300ms latency...typically its a physical issue between your PC and the first hop...The next step I would take would be to run an extended ping to see if you get any packet loss

ping 192.168.1.1 -n 500
and ping that second hop as well -n 500

You may also want to increase the size of the packet your pinging with (alot of times packet loss will not present itself until the packet size is higher then normal).

ping 192.168.1.1 -l 1492 -n 500

(the -l is an L)

ALSO, if you have CAT 5 to the home (apt) you either have a homerun, or fibre to the curb..its doubtful that the apt complex has 1 modem for all those connections...they probably resell access through the local ISP and get some kickback in the process. That link posted in the other thread is an actual DSL modem, not just a router. If they have installed a DSLAM in every apt block, you actually have DSL in your home, not a LAN. so 192.168.1.1 is the LAN side of that modem, and the 69 IP address in the second hop is the IP your ISP has assigned as your WAN IP (either DHCP, statically or via a pool assignment) . BTW, DSLAM = Digital Subscriber Line Access Multiplexor.
Click to expand...

The router cannot be accessed by me. They password the configuration section but I could get into as an admin and not system. I can't change any settings under admin so configuring it is not an option. I've got a DSL modem from my previous DSL connection but that's a ADSL modem if that makes a difference. The line that come out from the phone jack has no ring. As I said, I believe that the company ran a dedicated line to a DSLAM and spread the connection every apt in the block. The modem router is at my physical location.

As for new NICS, I've tried 3 different pcs and all 3 gave about the same response when I used them to ping my router. 3 different cables too. A new modem/router could be arranged for. I will ask if I can get one tomorrow. Pinging EACH other is perfectly fine. I get superb latency so I don't see why my NICS or cables are causing problems here. I was asked to enable DHCP. I suppose IP is assigned to me that way. I get packet lost occasionally.

I pinged the router continuously, as you asked, for 500 times and I get latencies ranging from 40ms to 400ms. Most of the time, it's in the 200ms area.

here's the speed of my connection now which was supposed to be 768/384.
 
Originally posted by: pillage2001
Nobody?? I tried almost everything suggested in this thread. Would a faulty modem router cause this??
Click to expand...

After reading what you've tried, that's what I'm leaning toward as a theory. It's a local issue because you've disconnected the WAN cable from the router and still had the problem, and you're seeing the problem on multiple PCs on the network. As a final test, disconnect the WAN cable, then disconnect all PCs but one and try that. If you see the problem, take a note of it, then disconnect that PC from the router and connect a different one, and test that one. If the problem occurs on different PCs with different NICs, with different Cat5 cables, and if it occurs when each PC is physically isolated from the others, then the only common component is the modem/router. Can't say precisely what's wrong with it, perhaps it needs to be reset to factory defaults and reconfigured, or perhaps it needs to be replaced.

Have you verified that there are no ip address conflicts?
 
Originally posted by: Astaroth33
Originally posted by: pillage2001
Nobody?? I tried almost everything suggested in this thread. Would a faulty modem router cause this??
Click to expand...

After reading what you've tried, that's what I'm leaning toward as a theory. It's a local issue because you've disconnected the WAN cable from the router and still had the problem, and you're seeing the problem on multiple PCs on the network. As a final test, disconnect the WAN cable, then disconnect all PCs but one and try that. If you see the problem, take a note of it, then disconnect that PC from the router and connect a different one, and test that one. If the problem occurs on different PCs with different NICs, with different Cat5 cables, and if it occurs when each PC is physically isolated from the others, then the only common component is the modem/router. Can't say precisely what's wrong with it, perhaps it needs to be reset to factory defaults and reconfigured, or perhaps it needs to be replaced.

Have you verified that there are no ip address conflicts?
Click to expand...

How do I verify that there's no ip conflicts??? I'll try isolating the pc with the modem/router to see if the problem persists. Report back in the evening.
 
IP conflicts typically dont cause latency (at least on the first hop...). Typically that would result in dropped packets, not severe latency.
 
Packet storm. I've seen this before when a nic went bad on the network.

Isolate each individual device on your network and see if the ping times improve.
 
you have a lan problem.

Check and make sure you have no loops in your network (ie two ports on your router plugged into each other)
 
First of all, bandwidth and latency are completely different.
Your download speeds have nothing to do with your ping. Except that a network problem could affect both of them.
Traceroute is much better than ping for troubleshooting because it shows you exactly where the problem is.
Wherever you see a big jump in ping, there is a problem.
You should be seeing no more than 100 pings to most sites with a DSL connection.

If you are pinging 200 to the first hop, then there is a problem at that device or before.
If that means your local personal equipment, then it is up to you to fix it.
If you see big jumps in ping between your personal router and the ISP's equipment, then they have a problem and you need to make them fix it.
 
Originally posted by: Shanti
First of all, bandwidth and latency are completely different.
Your download speeds have nothing to do with your ping. Except that a network problem could affect both of them.
Traceroute is much better than ping for troubleshooting because it shows you exactly where the problem is.
Wherever you see a big jump in ping, there is a problem.
You should be seeing no more than 100 pings to most sites with a DSL connection.

If you are pinging 200 to the first hop, then there is a problem at that device or before.
If that means your local personal equipment, then it is up to you to fix it.
If you see big jumps in ping between your personal router and the ISP's equipment, then they have a problem and you need to make them fix it.
Click to expand...

I know bandwidth and latency has nothign to do with one another. I was just running some tests for fun since we're on this topic about DSL.

I brought my friend's laptop over to test it and it pings at 200ms and over too. It's clearly not a problem with my pc or any other pc. If all fails by tonight, I'm asking for a replacement modem tomorrow.
 
This is freaking me out man. I unplugged the modem, went over to my friend's place and ping it. Latency is superb. Brought it back and do the same thing with my pc, BEHOLD! SUPERB LATENCY and everything is so fast now. How? Why? Who? When? Where?? I don't know!!!!!!

Even ths speed problem is solved!
 
When you unplugged for a while it allowed the port to reset.

Here is a trick if it happens again.

Change from PPPoE to PPPoA. It causes an automatic Port reset.

Enjoy.
 
Originally posted by: dmcowen674
When you unplugged for a while it allowed the port to reset.

Here is a trick if it happens again.

Change from PPPoE to PPPoA. It causes an automatic Port reset.

Enjoy.
Click to expand...

I did unplug it but I guess it was not for more than 1 minute. I thought a simple 10second wait would be sufficient. I don't have access to the router. Can't change the settings from PPPoE to PPPoA.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top