DSL loosing connection

[Frozen001]

Hello,

May parents are experiencing recent drop out of there DSL service.  A reboot of the modem fixes it, bit it will randomly happen again later.

Transceiver Information	Down Stream Path	Up Stream Path
DSL Speed (Kbits/Sec)	3360	768
Margin (dB)	14.0	6.0
Line Attenuation (dB)	33.7	14.5
Transmit Power (dBm)	-1.-6	2.9

I have it set up like this:  DSL modem handling DHCP to a wireless 4 port router.    Modem is a westell G90-610015-20.

[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 see

---

    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: An original or very old style NID with a spark gap and ground wire can even get spiders in it that could cause an issue. Inspect the NID first before thinking of changes or wiring.

http://en.wikipedia.org/wiki/Network_interface_device

http://en.wikipedia.org/wiki/Demarcation_point

Running a good quality wire CAT5, no need for CAT6,  directly to the NID for the DSL modem jack may help. That is what I had done with mine. Depending on the number of loads or amount of wire in the house could also cause issues. But if the user's signal quality is not being pulled low due to a wiring issues, it would usually indicate a problem elsewhere. Unless there was noise being picked up on the premises wiring. Wire DSL directly to the NID and install a filter there for all other in house wiring may help. There used to be available what was called a NID Filter, and I am sure you can still get them.

Ideal Connection if house wiring is an issue, or very old, and lengthy. Install a filter / splitter at the NID.

Run CAT5 directly to the NID location, and install a dedicated jack for the DSL modem.

Remove all in house wiring from the NID.

Connect piece of CAT5 from the NID to the filter / splitter input

Connect all existing phone lines to the phone side of the filter output.

Connect the new DSL CAT5 directly to the NID before the filter / splitter, or to the DSL side of the filter / splitter, depending on the device purchased.

This will take all the existing premises wiring out of the picture unless there is a short circuit or excessive load somewhere in the house.

At this point all the single filters could be removed because the DSL is filtered at the NID.

http://www.homephonewiring.com/dsl.html

Step three: You can test outbound to Giganews. But giganews has/had a test that will check your inbound connection from their servers to you.

I heard from another user that

---

Giganews is being watched very closely because of multipart binaries, and pirated material. MP3s and Video Content. 7 years ago you could get 10-20 MP3 albums in a single day, and that was with a 15/5 fios connection. So they started providing an encrypted connection service for an added fee. I have not messed with news groups for a very long time. Now with deep packet inspection, and other enforcement, I would not even think of it. No news I want there. But there may be content that people want? They may even be checking and limiting speed from that domain. Never tested. But let me see. It looks as if reverse trace routes and speed tests are being blocked by Verizon from Giganews to my router.

        Reverse Traceroute

        Tool news.giganews.com

        traceroute to *.*.*.*, 30 hops max, 60 byte packets
        1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
        2 te0-0-0-7.mpd22.iad02.atlas.cogentco.com (38.122.67.49) 0 ms 0 ms te0-7-0-9.mpd22.iad02.atlas.cogentco.com (38.122.62.193) 0 ms
        3 te0-0-0-4.ccr21.iad02.atlas.cogentco.com (154.54.31.105) 0 ms 0 ms te0-2-0-0.ccr21.iad02.atlas.cogentco.com (154.54.31.101) 0 ms
        4 uunet.iad01.atlas.cogentco.com (154.54.13.138) 28 ms verizon.iad01.atlas.cogentco.com (154.54.10.226) 40 ms uunet.iad01.atlas.cogentco.com (154.54.13.138) 28 ms
        5 0.ae1.RES-BB-RTR2.verizon-gni.net (152.63.32.157) 41 ms 41 ms 0.ae2.RES-BB-RTR1.verizon-gni.net (152.63.34.22) 13 ms
        6 * * *
        7 * * *
        8 * * *
        9 * * *
        10 * * *
        11 * * *
        12 * * *
        13 * * *
        14 * * *
        15 * * *
        16 * * Max number of unresponsive hops reached (firewall or filter?)

---

Step 4: Have the provider run a local loop test to see if any problems are indicated. If there are, then they could run the test with everything in the house disconnected, except the new DSL modem connection. If issues are still indicated, then the DSL provider needs to make connections on the local loop. Another user told me that they had issues when it rained, and it was because construction had left a splice box open on a line somewhere.

[Frozen001]

Here is what the reverse trace route gives:

traceroute to 71.127.*.* (71.127.*.*), 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 ash-bb1-link.telia.net (213.248.70.241) 20 ms 20 ms 20 ms
3 GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (63.65.76.189) 3 ms 3 ms 3 ms
4 P14-0.LCR-01.SCTNPA.verizon-gni.net (130.81.28.185) 29 ms 29 ms 29 ms
5 P8-0.SYRCNY-SYRCNYSU-ERXG01.verizon-gni.net (130.81.35.197) 24 ms 24 ms 25 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * Max number of unresponsive hops reached (firewall or filter?)

I am guessing verizon is blocking this based on the message you showed.

Phone wire from pole to house is new within the last 5 years.  I do not know what the cable type is to the jack the DSL modem is connected to but I will check.  I suspect that it is not CAT5.

This problem is recent.  They have has DSL for over a year with no problems until I added a DD-WRT wireless client-bridge to the mix.  Long story, but I am living with them temporarily living with them while our home is built.  Rather than run a cable to our computer I am using a netgreat AP with DD-WRT installed as a wireless bridge.  Connected to that is a netgear wifi router setup as just a router, no DHCP service.  Connected to that router is a blue-ray player, and a desktop PC, neither have wifi capibilities, hence the wireless bridge and router.  I ran this setup at our home pror to the move on TWC cable with no problems.  

Just this morning I got up and no internet service.  Thing I noticed this time is that the DSL modem would not give out an IP addesss via DHCP.

I am wondering if a different DSL modem would work.  I have my old Westel 7500 still from when I had DSL service a few years ago, can I just hook that up and try it?

As a side note, I dropped DSL at my house for similar issues.

[prisaz]

I would have Verizon tech support run a line test. If there are line issues Verizon tech support should be able to see them. I know they could when I had DSL, and someone left a splice box open that filled with water. See if they will replace the modem? Seems like perhaps some issues on the down stream side, I would say Verizon needs to solve this one.