Same issue here , we are dropping DSl on friday we have had no luck with verizon on fixing the issue it has been ongoing
and they keep sending us modem after modem and I know its not the modem
we are giving up we called our local cable provider and are having faster and more reliable internet services installed
To all who need help
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 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 it: 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?
Our DSL is constantly dropping. Please review and advise. Thank you.
We are using a Netgear DM111PSP v2 Modem and an Asus dual band 3x3 router.
news.giganews.com
traceroute to {edited for privacy}30 hops max, 60 byte packets1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms2 216-166-96-101.fwd.datafoundry.com (216.166.96.101) 0 ms 216-166-96-105.fwd.datafoundry.com (216.166.96.105) 0 ms 216-166-96-117.fwd.datafoundry.com (216.166.96.117) 0 ms3 ash-b1-link.telia.net (62.115.42.153) 0 ms 0 ms 0 ms4 ash-b2-link.telia.net (213.155.130.89) 0 ms ash-b2-link.se.telia.net (80.91.245.223) 0 ms 0 ms5 TenGigE0-0-0-10.GW1.IAD8.ALTER.NET (152.179.50.233) 0 ms 9 ms 0 ms6 P11-0-0.SCTNPA-LCR-02.verizon-gni.net (130.81.27.175) 12 ms 12 ms 12 ms7 P12-0.SCTNPA-HZTNPAHZ-ERXG02.verizon-gni.net (130.81.136.5) 14 ms 15 ms 15 ms8 * * *9 * * *10 * * *11 * * *12 * * *13 * * *14 * * *15 * * *16 * * *17 * Max number of unresponsive hops reached (firewall or filter?)
news-europe.giganews.com
traceroute to {edited for privacy}, 30 hops max, 60 byte packets1 vl201.gw1.ams.giganews.com (216.196.110.3) 0 ms 0 ms 0 ms2 te0-0-1-3.nr11.b015583-1.ams03.atlas.cogentco.com (149.11.104.17) 0 ms 0 ms 0 ms3 154.25.2.121 (154.25.2.121) 0 ms 154.25.2.125 (154.25.2.125) 0 ms 0 ms4 be2440.ccr42.ams03.atlas.cogentco.com (130.117.50.5) 1 ms be2434.ccr41.ams03.atlas.cogentco.com (130.117.2.242) 1 ms be2440.ccr42.ams03.atlas.cogentco.com (130.117.50.5) 1 ms5 be2275.ccr21.lon13.atlas.cogentco.com (130.117.51.253) 8 ms be2183.ccr22.lpl01.atlas.cogentco.com (154.54.58.69) 10 ms be2276.ccr22.lon13.atlas.cogentco.com (154.54.36.57) 8 ms6 be2349.mpd21.jfk02.atlas.cogentco.com (154.54.30.177) 81 ms be2347.ccr21.jfk02.atlas.cogentco.com (154.54.27.141) 80 ms be2350.mpd22.jfk02.atlas.cogentco.com (154.54.30.185) 80 ms7 be2150.mpd21.dca01.atlas.cogentco.com (154.54.31.129) 86 ms be2149.ccr22.dca01.atlas.cogentco.com (154.54.31.125) 88 ms be2096.ccr22.jfk02.atlas.cogentco.com (154.54.30.41) 82 ms8 be2176.ccr41.iad02.atlas.cogentco.com (154.54.41.53) 87 ms be2149.ccr22.dca01.atlas.cogentco.com (154.54.31.125) 91 ms be2148.ccr21.dca01.atlas.cogentco.com (154.54.31.117) 88 ms9 verizon.iad01.atlas.cogentco.com (154.54.12.46) 87 ms verizon.iad01.atlas.cogentco.com (154.54.10.226) 88 ms 88 ms10 verizon.iad01.atlas.cogentco.com (154.54.10.226) 88 ms G13-0-0.SCTNPA-LCR-02.verizon-gni.net (130.81.151.35) 89 ms verizon.iad01.atlas.cogentco.com (154.54.12.46) 89 ms11 G13-0-0.SCTNPA-LCR-02.verizon-gni.net (130.81.151.35) 94 ms P9-0.SCTNPA-HZTNPAHZ-ERXG02.verizon-gni.net (130.81.44.19) 102 ms 101 ms12 * * *13 * * *14 * * *15 * * *16 * * *17 * * *18 * * *19 * * *20 * * Max number of unresponsive hops reached (firewall or filter?)
I have the same problem. I waited 1/2 hour on the phone before someone that cant speak english tells me it is my router/modem. i lose internet every 10 to 20 minutes. I have shut off my router and it still wil not connect. I called again and told them to fix the line comming into the house or I will switch to Comcast. The lady still going on about my route'r it new and every time they send a signal to the house they find out it was something with the line. I guess they want me to switch to someone else
@Styp wrote:My internet keeps dropping. It will connect for 10-15minutes and then stop. Is there a problem with Verizon service?
#1 To access the modem combo, by default..
a) ..it's LAN IP is 192.168.0.1
b) ..user name is admin
c) ...password is password
#2 Once in,
a) Under Maintance click on ADSL Line Status
b) Show what you see in there
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_devicehttp://en.wikipedia.org/wiki/Demarcation_pointRunning 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 inputConnect 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.
