Main question: Do I need a new modem, or is this some maintenance (or other) being performed by Verizon?
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?
Sorry, all I could get on the previous response was the traceroute. "Unresponsive hops?" That's a new one on me.
The modem. Here's all the info I have on it; no separate router attached.
Modem: D-Link Model: DSL 27508 (B?)Firmware version: VZ_1.32D-LINKModel DSL-2750BPN: BSL2750BAVZ02T1Shipped Firmware version: VZ_1.32{edited for privacy}
Hope this helps. And thanks so much for the quick response and solid guidance!
Forgive me two mistakes.
First, I should have explained I'm using a MacBook Pro, without Windows. OS 10 Mavericks keeps me running.
And I didn't realize it would be a problem to include an "image' -- but that was the easiest way to capture the traceroute. Will try it again another way. Stay tuned . . .
@cafox513 wrote: Forgive me two mistakes.First, I should have explained I'm using a MacBook Pro, without Windows. OS 10 Mavericks keeps me running.And I didn't realize it would be a problem to include an "image' -- but that was the easiest way to capture the traceroute. Will try it again another way. Stay tuned . . .
You should be able to copy and paste the traceroute from the Terminal. I happen to have a Mac handy. Here's what a traceroute looks like when copied:
<machinename>:~ <myusername>$ traceroute www.yahoo.com
traceroute: Warning: www.yahoo.com has multiple addresses; using 98.139.183.24
traceroute to ds-any-fp3-real.wa1.b.yahoo.com (98.139.183.24), 64 hops max, 52 byte packets
1 192.168.3.1 (192.168.3.1) 1.334 ms 1.004 ms 0.812 ms
2 10.41.13.1 (10.41.13.1) 305.305 ms 511.520 ms 332.611 ms
3 p0-0-1-1.bflony-lcr-22.verizon-gni.net (130.81.136.28) 281.923 ms 409.290 ms 409.512 ms
4 ae6-0.ny325-bb-rtr2.verizon-gni.net (130.81.209.36) 307.215 ms 409.851 ms 408.966 ms
5 0.xe-9-1-0.br1.nyc1.alter.net (152.63.4.241) 512.351 ms 409.575 ms 409.274 ms
6 * * 204.255.173.54 (204.255.173.54) 340.792 ms
7 vlan52.ebr2.newyork2.level3.net (4.69.138.254) 411.978 ms 409.302 ms 409.739 ms
8 ae-4-4.ebr1.newyork1.level3.net (4.69.141.17) 306.878 ms
ae-46-46.ebr2.newyork1.level3.net (4.69.201.29) 409.497 ms
ae-46-46.ebr1.newyork1.level3.net (4.69.201.41) 410.238 ms
9 ae-61-61.csw1.newyork1.level3.net (4.69.134.66) 307.040 ms
ae-91-91.csw4.newyork1.level3.net (4.69.134.78) 306.689 ms
ae-71-71.csw2.newyork1.level3.net (4.69.134.70) 400.946 ms
10 ae-4-90.edge4.newyork1.level3.net (4.69.155.210) 306.933 ms
ae-3-80.edge4.newyork1.level3.net (4.69.155.146) 511.655 ms
ae-1-60.edge4.newyork1.level3.net (4.69.155.20) 411.678 ms
11 yahoo-inc.edge4.newyork1.level3.net (4.28.130.82) 306.965 ms 409.531 ms 409.354 ms
12 ae-5.pat2.bfz.yahoo.com (216.115.96.67) 418.117 ms
ae-2.pat2.bfz.yahoo.com (216.115.100.74) 409.593 ms
ae-2.pat1.bfz.yahoo.com (216.115.100.26) 307.026 ms
13 ae-4.msr1.bf1.yahoo.com (216.115.100.25) 407.566 ms
ae-3.msr1.bf1.yahoo.com (216.115.100.29) 175.162 ms 409.087 ms
14 xe-7-0-0.clr2-a-gdc.bf1.yahoo.com (98.139.128.19) 307.353 ms
xe-2-0-0.clr2-a-gdc.bf1.yahoo.com (98.139.232.97) 409.333 ms
xe-10-0-0.clr2-a-gdc.bf1.yahoo.com (98.139.232.107) 409.181 ms
15 et-17-1.fab8-1-gdc.bf1.yahoo.com (98.139.128.51) 409.403 ms
et18-25.fab7-1-sat.bf1.yahoo.com (98.139.128.105) 409.539 ms
unknown-98-139-128-x.yahoo.com (98.139.128.99) 409.295 ms
16 po-16.bas2-7-prd.bf1.yahoo.com (98.139.130.3) 306.611 ms
po-14.bas1-7-prd.bf1.yahoo.com (98.139.129.225) 409.321 ms
po-16.bas2-7-prd.bf1.yahoo.com (98.139.130.3) 307.053 ms
17 * * *
18 * * *
^C
<machinename>:~ <myusername>$
@cafox513 wrote: The modem. Here's all the info I have on it; no separate router attached.Modem: D-Link Model: DSL 27508 (B?)Firmware version: VZ_1.32D-LINKModel DSL-2750BPN: ********************Shipped Firmware version: VZ_1.32S/N: ***********WPA Key: ***********SSID/MAC: ***************User name: adminPassword: ****************Hope this helps. And thanks so much for the quick response and solid guidance!
Modem: D-Link Model: DSL 27508 (B?)Firmware version: VZ_1.32D-LINKModel DSL-2750BPN: ********************Shipped Firmware version: VZ_1.32S/N: ***********WPA Key: ***********SSID/MAC: ***************User name: adminPassword: ****************
#1 When you look for the transceiver Statistics, this text gives to you an idea of what to look for:Line Mode, Data Path:, transceiver Information Down Stream Path Up Stream Path, DSL Speed (Kbits/Sec), Margin (dB), Line Attenuation (dB), and Transmit Power (dBm).#2 As where the transceiver Statistics are located in the DLink 2750:To my knowledge, no one has managed to find and report the location of the transceiver Statistics page on the D-Liink modem, so we'll need Verizon to grab the stats from the DSLAM, and while they're at it, check the logs on their end to see if the line is dropping out physucally, or is dropping out on another sense.
Bingo! It was the modem indeed. Verizon came out, checked out my system, and within minutes knew where the problem lay. Swapped the modem for a new one. Ahhhh.
