Internet keeps going down

[Fwu193]

My internet keeps going down (It went down11 times today).

Each time the internet went down and then came back up the connection speed shown on 192.168.1.1 would get lower. I've contacted tech support about this twice over the month ,but they always say there's no problem with the line and the last time i called a representative opened a ticket to the network team but it seems it hasn't done anything.

I use a westell versalink 327W.

I've used it for 4-6 years.

[dslr595148]

Step one: Visit www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that the final hop (bottom-most line of the trace) might contain a hop with your IP address in it. Remove that line. 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.

Step two: Provide the transceiver Statistics from your modem.

Visit »192.168.1.1/ for me and do the following:

#1 If you see a Blue and White Westell page, mouse over Troubleshooting, go to DSL, and choose transceiver Statistics. Copy and then when on-line Paste the information on that page.

#2 If using the Red and Black Firmware: Go to System Monitoring > Advanced Monitors > transceiver Statistics. Copy and then when on-line Paste the information on that page.

#3 Try visiting »192.168.1.1/transtat.htm which is a direct link to the Stats on older modems.

d) If you need a Username and Password, try the following:

admin/password

admin/password1

admin/admin

admin/admin1

admin/Serial Number.

By Serial Number, I don't mean type in the words Serial Number. I mean find and type in the serial number found on the bottom of this router.

^^^^^

[Fwu193]

traceroute to BLANK, 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 te0-7-0-9.mpd22.iad02.atlas.cogentco.com (38.122.62.193) 0 ms te0-0-0-7.mpd22.iad02.atlas.cogentco.com (38.122.67.49) 0 ms
3 te0-0-0-4.ccr21.iad02.atlas.cogentco.com (154.54.31.105) 0 ms te0-2-0-0.ccr21.iad02.atlas.cogentco.com (154.54.31.101) 0 ms 0 ms
4 verizon.iad01.atlas.cogentco.com (154.54.10.226) 0 ms 0 ms 0 ms
5 0.xe-1-0-2.PHIL-BB-RTR2.verizon-gni.NET (152.63.3.126) 6 ms 6 ms 0.xe-8-1-4.PHIL-BB-RTR1.verizon-gni.NET (152.63.6.14) 5 ms
6 B100.PHLAPA-LCR-22.verizon-gni.net (130.81.209.187) 7 ms 6 ms 6 ms
7 P8-0.PHLAPA-PHLAPAMK-ERXG05.verizon-gni.net (130.81.44.229) 8 ms 8 ms 8 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * Max number of unresponsive hops reached (firewall or filter?)

_________________________________________________________

Transceiver Statistics

Transceiver Revision:	7.2.3.0
Vendor ID Code:	4
Line Mode:	ADSL2+ Mode
Data Path:	Interleaved
Transceiver Information	Downstream Path	Upstream Path
DSL Speed (Kbits/Sec)	1787	446
Margin (dB)	14.5	23.0
Line Attenuation (dB)	48.0	29.5
Transmit Power (dBm)	18.1	12.1

[dslr595148]

Ok.

#1 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

#2 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?)

---

#3 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.