Connection problems hi-speed internet

[OCPoppy]

Since replaceing my old modem with a DLink 2750B., I am having frequent disconnects. The internet reconnects with a power down reset, and runs fine. This happens a least several times a day, with no pattern as to time between drops. Have called support and been told to use Verizon In Home Agent. Have Win8.1 but there doesnt appear to be support fo Win or DLink 2750.

[dslr595148]

Step one: Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that your non-bogan public IP Address will show up.  It might shown up as the final hop (bottom-most line of the trace)  might contain a hop with your IP address in it. Either remove that line or show only the first two octets. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.

For example this what I saw when I was using Verizon

---

news.giganews.com

    traceroute to 71.242.*.* (71.242.*.*), 30 hops max, 60 byte packets
    1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 13 ms 13 ms 13 ms
    2 ash-bb1-link.telia.net (213.248.70.241) 39 ms 7 ms 7 ms
    3 TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (63.125.125.41) 4 ms 4 ms GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (63.65.76.189) 4 ms
    4 so-7-1-0-0.PHIL-CORE-RTR1.verizon-gni.net (130.81.20.137) 6 ms 6 ms 6 ms
    5 P3-0-0.PHIL-DSL-RTR11.verizon-gni.net (130.81.13.170) 6 ms 6 ms 6 ms
    6 static-71-242-*-*.phlapa.east.verizon.net (71.242.*.*) 32 ms 32 ms 33 ms

---

Step two: Can you provide the Transceiver Statistics from your non D-link older DSL modem?

#3 If you don't know how to get that info:

a) What is the brand and model of your modem?

b) If you have a RJ-45 WAN port router connected to the D-link: What is the brand and model of the RJ-45 WAN port router?

#4 If you have a RJ-45 WAN port router connected to the modem, even if you know how to get the Transceiver Statistics from the modem: What is the brand and model of the RJ-45 WAN port router?

[OCPoppy]

Included is Giganews trace:

news.giganews.com

traceroute to 108.25.120.181 (108.25.120.181), 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 216-166-96-162.fwd.datafoundry.com (216.166.96.162) 0 ms 216-166-96-166.fwd.datafoundry.com (216.166.96.166) 0 ms 216-166-96-174.fwd.datafoundry.com (216.166.96.174) 0 ms
3 ash-b1-link.telia.net (62.115.42.153) 0 ms 0 ms 0 ms
4 ash-b2-link.telia.net (213.155.130.89) 0 ms 0 ms 0 ms
5 TenGigE0-0-0-10.GW1.IAD8.ALTER.NET (152.179.50.233) 2 ms 2 ms 2 ms
6 T0-0-1-0.ATCLNJ-LCR-22.verizon-gni.net (130.81.209.79) 14 ms 17 ms 17 ms
7 P8-0.ATCLNJ-PSVLNJPL-ERXG02.verizon-gni.net (130.81.46.197) 13 ms P9-0.ATCLNJ-PSVLNJPL-ERXG02.verizon-gni.net (130.81.46.199) 14 ms P8-0.ATCLNJ-PSVLNJPL-ERXG02.verizon-gni.net (130.81.46.197) 14 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * Max number of unresponsive hops reached (firewall or filter?)

Directly connected to DL2750B modem.  Speed dropped this AM from normal 12-13MP to 2. Now apprears to be back to normal.

[smith6612]

With the D-Link modems, we don't have a known way to pull the Transceiver statistics from them. Unfortunate, but we can still make do without them. If you visit http://192.168.1.1/ and log into the D-Link, somewhere on the main page you should see your connection speed. Check this periodically, both when your connection is up to speed and when it is not. This value should NOT change. If it does change, we have a line problem.

If the value is not changing, your problem may be due to a congestion problem I'm all too familiar with, having dealt with a similar problem in the past for a relative. At around the afternoon time, their Internet would start to get slow. Towards the evening hours when everyone was on, the connection got unbearable and to the point where the line was phyically re-syncronizing. I found out that the trunk line back to the CO (my relative was virtualy served) was running well past 90% utilization, and that is where no one should ever run a network.

We'll figure out whether or not this is congestion in a bit, though.