Connecting Issues
evad991
Enthusiast - Level 2

I currently have DSL access with a Westell A90-750015-07 router and a Cisco wireless adapter. I seem to have issues connecting at times to the Internet, especially since we had a recent storm. One night I'm able to get on, the next I can't. And when I am able to go online, it is usually after several tries. My computer is in the bedroom and the router is in the kitchen, which may have something to do with the connection issue because there is not a closer jack.

Usually what I end up doing is turning off the computer, restarting, or shutting down completely, turning off the router and taking the adapter out and turning back on. Usually I could then get back on, but seems a hassle.

Since I got on now, the connection has stayed on, thankfully. Sometimes it goes while I'm on, then will come back on. It's a pain because it's been like this consistently.

I have a networking cable, however, it's been a while since I used it. Verizon's Technical Support helped me the last time. I'm not sure if something needs to be reconfigured since the storm so this does not keep happening. They did something while the cable was plugged in, then I was able to go back to using the wireless adapter to connect. I don't suppose anyone would have instructions. I'm also unsure which one it gets plugged into. I believe it's Ethernet on my HP desktop, but on the router I'm unsure which one it goes into, like E1/Uplink, E2, E3, or E4/Data. I tried earlier with all of them, even turned the router off, then would restart the computer but nothing happened.

Any guidance would be much appreciated.

0 Likes
1 Solution

Correct answers
Re: Connecting Issues
dslr595148
Community Leader
Community Leader

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.

View solution in original post

Re: Connecting Issues
dslr595148
Community Leader
Community Leader

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


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?

Visit http://192.168.1.1/ for us and do the following:

a) If you see a Blue and White Westell page, mouse over Troubleshooting, go to DSL, and choose Transceiver Statistics. Copy and paste the information on that page.

b) If using the Red and Black Firmware: Go to System Monitoring > Advanced Monitors > Transceiver Statistics. Copy and paste the information on that page.

c) Try visiting http://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.

0 Likes
Re: Connecting Issues
evad991
Enthusiast - Level 2

Step 1:

news.giganews.com

traceroute to {edited for privacy} 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 4 ms 4 ms 4 ms
2 ash-bb1-link.telia.net (213.248.70.241) 0 ms 0 ms 0 ms
3 ash-b2-link.telia.net (213.155.137.225) 0 ms ash-b2-link.se.telia.net (80.91.245.223) 0 ms ash-b2-link.telia.net (213.155.137.225) 0 ms
4 TenGigE0-0-0-10.GW1.IAD8.ALTER.NET (152.179.50.233) 3 ms 3 ms 9 ms
5 G13-0-0.SCTNPA-LCR-02.verizon-gni.net (130.81.151.35) 13 ms 13 ms 13 ms
6 G4-1-2213.SCTNPA-HZTNPAHZ-ERXG13.verizon-gni.net (100.41.193.147) 16 ms 16 ms 17 ms
7 * * *
8 * * *
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 packets
1 vl201.gw1.ams.giganews.com (216.196.110.3) 0 ms 0 ms 0 ms
2 te7-8.ccr01.ams05.atlas.cogentco.com (149.11.104.17) 0 ms te7-7.ccr01.ams05.atlas.cogentco.com (149.11.104.9) 0 ms 0 ms
3 te0-7-0-25.mpd21.ams03.atlas.cogentco.com (130.117.0.85) 0 ms 0 ms te0-7-0-26.ccr22.ams03.atlas.cogentco.com (154.54.72.50) 0 ms
4 be2182.ccr21.lpl01.atlas.cogentco.com (154.54.77.246) 10 ms be2185.ccr22.lpl01.atlas.cogentco.com (154.54.37.106) 10 ms 10 ms
5 te0-7-0-27.ccr22.bos01.atlas.cogentco.com (130.117.0.185) 78 ms te0-3-1-0.ccr22.bos01.atlas.cogentco.com (154.54.5.122) 78 ms te0-2-0-4.ccr21.bos01.atlas.cogentco.com (66.28.4.189) 79 ms
6 be2149.ccr22.dca01.atlas.cogentco.com (154.54.31.125) 94 ms be2095.mpd21.jfk02.atlas.cogentco.com (154.54.30.37) 84 ms be2094.ccr21.jfk02.atlas.cogentco.com (154.54.30.13) 82 ms
7 be2150.mpd21.dca01.atlas.cogentco.com (154.54.31.129) 91 ms 88 ms be2151.mpd22.dca01.atlas.cogentco.com (154.54.40.73) 88 ms
8 be2122.ccr21.mia01.atlas.cogentco.com (154.54.24.194) 112 ms be2171.mpd22.atl01.atlas.cogentco.com (154.54.31.109) 100 ms be2168.ccr21.atl01.atlas.cogentco.com (154.54.31.93) 99 ms
9 be2123.ccr22.mia01.atlas.cogentco.com (154.54.24.198) 113 ms be2054.ccr21.mia03.atlas.cogentco.com (154.54.80.42) 112 ms be2123.ccr22.mia01.atlas.cogentco.com (154.54.24.198) 116 ms
10 be2055.ccr21.mia03.atlas.cogentco.com (154.54.24.234) 114 ms 0.xe-9-2-0.BR1.MIA19.ALTER.NET (204.255.168.29) 153 ms be2054.ccr21.mia03.atlas.cogentco.com (154.54.80.42) 113 ms
11 0.xe-9-2-0.BR1.MIA19.ALTER.NET (204.255.168.29) 152 ms 152 ms 152 ms
12 P11-0-0.SCTNPA-LCR-02.verizon-gni.net (130.81.27.175) 168 ms 164 ms G4-0-2213.SCTNPA-HZTNPAHZ-ERXG13.verizon-gni.net (130.81.198.27) 170 ms
13 G4-0-2213.SCTNPA-HZTNPAHZ-ERXG13.verizon-gni.net (130.81.198.27) 169 ms 167 ms *

0 Likes
Re: Connecting Issues
evad991
Enthusiast - Level 2

Step 2:

 
   
 
         
 MainWireless
Settings
      
 
   
 
  Main
  Transceiver Stats
 
 
 
 
Transceiver Statistics
Transceiver Revision A2pB020b3.d20h
Vendor ID Code 4D54
Line Mode ADSL_G.dmt
Data PathINTERLEAVED
 
Transceiver InformationDown Stream PathUp Stream Path
DSL Speed (Kbits/Sec)2528800
Margin (dB)28.910.0
Line Attenuation (dB)16.010.0
Transmit Power (dBm)16.811.9
 
 
  
 
0 Likes
Re: Connecting Issues
dslr595148
Community Leader
Community Leader

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.