DSL slow NYC SOHO

[jonjonhan]

Thanks again for all your help and concern. I was on the phone for over an hour with several people who were very hard to understand. Not just because of their very heavy accents, but also because their audio was so highly compressed it was nearly impossible to understand them. The last person somewhat indicated that someone would come this week and that I will be responsible for paying for a problem within my place. If and when this person shows up, I will be very emphatic that if does not understand what a home run is that he may as well not even enter my place. Is there any product that I can buy which may achieve a similar thing?

[dslr595148]

---

@jonjonhan wrote:

Is there any product that I can buy which may achieve a similar thing?

---

Between yes and no, I am thinking no.

For how to do it, I point to http://www.dslreports.com/faq/1261

[jonjonhan]

I don't think any of that will help, here's why.

Disconnected one by one, devices, and wiring, with the final configuration being ONLY the test Jack at the window small box from Verizon. Nothing else attached, no phone, all wiring past this disconnected physically at the window box.

Tried with both Ethernet (acutally slower) and wifi on the current modem, and then an older modem I still have. The older modem was worse, or at lest the few tests I did. The current newer modem yielded an average of 5megs, never going above 5.2 and dipping lower to 4 and occasionally to less than 2, but mostly around 4. Upload seemed to stay at around 56k didn't really see it going above. I'm using Ookla speedtest.net. Last night was a little better even with all wiring intact.

A DSL splitter, which is I believe what this home run is about, will only yield the above results, am I wrong?

Below is screen captures of the modem results:

Downstream Rate:	6208Kbps
Upstream Rate:	636Kbps
PPP User Name:	Newdsl
ISP Protocol	PPPoE
Encapsulation:	LLC

PPP Status

PPP Parameter Status

PPP Type:	PPPoE
LCP State:	UP
IPCP State:	UP
Authentication Failures:	0
Session Time:	0 Days, 0H:29M:53S
Packets Sent:	47953
Packets Received:	63520

Broadband Status

Broadband Parameter Status

VPI:	0
VCI:	35
Broadband Mode Setting:	ADSL2+
Broadband Negotiated Mode:	ADSL2+
Connection Status:	CONNECTED
Downstream Speed:	6208 Kbps
Upstream Speed:	636 Kbps
Retrains:	2
Retrain Timer:	0 Days, 0H:31M:47S
ATM QoS class:	UBR
Near End CRC Errors Interleave:	920
Near End CRC Errors Fastpath :	N/A
Far End CRC Errors Interleave :	256
Far End CRC Errors Fastpath :	N/A
30 Minute Near End CRC Interleave :	0
30 Minute Near End CRC Fastpath :	N/A
30 Minute Far End CRC Interleave :	0
30 Minute Far End CRC Fastpath :	N/A
Near End RS FEC Interleave :	0
Near End RS FEC Fastpath :	N/A
Far End RS FEC Interleave :	0
Far End RS FEC Fastpath :	N/A
30 Minute Near End FEC Interleave :	0
30 Minute Near End FEC Fastpath :	N/A
30 Minute Far End FEC Interleave :	0
30 Minute Far End FEC Fastpath :	N/A
30 Minute Discarded Packets Downstream :	0
30 Minute Discarded Packets Upstream :	0
SNR Downstream :	28 dB
SNR Upstream :	24 dB
Attenuation Downstream :	25 dB
Attenuation Upstream :	10 dB
Power Downstream	18.4 dBm
Power Upstream	12.3 dBm

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) 0 ms 0 ms 0 ms
2 216.166.96.178 (216.166.96.178) 0 ms 0 ms 216.166.96.170 (216.166.96.170) 0 ms
3 xe-3-0-1.cr1.iad1.us.as4436.gtt.net (69.31.10.121) 0 ms 0 ms 0 ms
4 144.228.205.145 (144.228.205.145) 1 ms 1 ms 1 ms
5 144.232.24.206 (144.232.24.206) 1 ms 2 ms 1 ms
6 144.232.8.210 (144.232.8.210) 0 ms 0.xe-9-3-0.BR2.IAD8.ALTER.NET (204.255.169.217) 0 ms 144.232.8.210 (144.232.8.210) 0 ms
7 B300.NYCMNY-LCR-21.verizon-gni.net (130.81.199.155) 11 ms P1-8-0-0.NYCMNY-LCR-21.verizon-gni.net (130.81.199.11) 10 ms *
8 G2-0.NYCMNY-NYCMNY56-ERXG02.verizon-gni.net (130.81.193.114) 11 ms G2-1.NYCMNY-NYCMNY56-ERXG02.verizon-gni.net (130.81.195.1) 9 ms G2-0.NYCMNY-NYCMNY56-ERXG02.verizon-gni.net (130.81.193.114) 10 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * 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 te0-0-0-27.rcr21.ams05.atlas.cogentco.com (149.11.104.17) 0 ms 0 ms 0 ms
3 be2039.ccr42.ams03.atlas.cogentco.com (154.54.36.145) 1 ms 1 ms 1 ms
4 be2275.ccr21.lon13.atlas.cogentco.com (130.117.51.253) 8 ms be2277.mpd21.lon13.atlas.cogentco.com (154.54.62.145) 8 ms be2488.ccr42.lon13.atlas.cogentco.com (154.54.39.110) 8 ms
5 be2386.ccr21.bos01.atlas.cogentco.com (154.54.44.161) 76 ms be2387.ccr22.bos01.atlas.cogentco.com (154.54.44.165) 76 ms be2386.ccr21.bos01.atlas.cogentco.com (154.54.44.161) 76 ms
6 be2062.ccr21.jfk05.atlas.cogentco.com (154.54.7.14) 80 ms be2095.mpd21.jfk02.atlas.cogentco.com (154.54.30.37) 80 ms be2061.ccr21.jfk05.atlas.cogentco.com (154.54.3.70) 80 ms
7 be2062.ccr21.jfk05.atlas.cogentco.com (154.54.7.14) 82 ms be2063.ccr21.jfk05.atlas.cogentco.com (154.54.47.58) 81 ms be2177.ccr22.dca01.atlas.cogentco.com (154.54.41.206) 93 ms
8 be2149.ccr22.jfk02.atlas.cogentco.com (154.54.31.126) 93 ms 90 ms 0.xe-10-3-0.BR2.NYC4.ALTER.NET (204.255.168.113) 81 ms
9 B1000.NYCMNY-LCR-22.verizon-gni.net (130.81.163.225) 87 ms * B400.NYCMNY-LCR-21.verizon-gni.net (130.81.199.163) 81 ms
10 * 0.xe-10-3-0.BR2.NYC4.ALTER.NET (204.255.168.113) 90 ms G2-1.NYCMNY-NYCMNY56-ERXG02.verizon-gni.net (130.81.195.1) 83 ms
11 * * *
12 * * Max number of unresponsive hops reached (firewall or filter?)

[smith6612]

Those stats actually look a lot better. The line looks clean from the Verizon demarc. Given that's the case, something is likely wrong with the wiring in your home. You can still work with the Verizon tech to see if they will install a Homerun for you using the existing wiring. Otherwise, if you want to install one yourself, there's a couple of ways to do it.

The proper way to install a Homerun, is to swap out the NID line module with one that includes an ADSL Splitter. Once done, you can either use the secondary pair in your home's wiring to connect up a dedicated jack, with the secondary pair rewired to be the primary pair in the jack. Alternatively, you can run new CAT3 cabling to where you want the modem to be.

The other ways, you can be creative with. The DSL Should run over it's own dedicated wire pair, and the signal should not travel to any device or jack but the one with the DSL modem. The rest of the house should be filtered from the DSL Signal.

One last thing, if you are running the telephone line for the modem through a power strip, please don't do that. Most power strips are not certified for ADSL or even ADSL2+ operation, and will add noise to the signal.

If you can keep your modem's SNR at 20+dB, Verizon's ASSIA optimization software should begin to crank your speed up to about 10Mbps down, 1Mbps up. From there, any further problem would likely be due to congestion somewhere, which we can troubleshoot. Let's get the line stable and running at capacity.

[jonjonhan]

Thanks a lot, this is good information.

I've taken a lot of the internal wiring out, cleaned it up a bit. I then used a more recent wire and used a jack splitter there, one for the phone with 2 dsl filters chained, and one for the modem. It works as well as the window connection test point.

The home run is a great idea, but, given that I was using the incoming line exclusively for the modem during the test, it's effectively the same thing. Now that I've put it into the house wiring is when such a splitter can come in. The sppedtest by ookla got up to at most 5.2mb and .53kbs, never anything close to 8mb nor .75kbs.

I'm just using a wall house current outlet for now.

I'm baffled by your statement pasted below:

If you can keep your modem's SNR at 20+dB, Verizon's ASSIA optimization software should begin to crank your speed up to about 10Mbps down, 1Mbps up.

What is Verizon's ASSIA optimization software?

Stats from the new location inside wiring using a simple jack splitter, phone on 2 filters chained.

############### 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 216.166.96.166 (216.166.96.166) 0 ms 216.166.96.178 (216.166.96.178) 0 ms 216.166.96.182 (216.166.96.182) 0 ms
3 xe-3-0-1.cr1.iad1.us.as4436.gtt.net (69.31.10.121) 0 ms 0 ms 0 ms
4 144.228.205.145 (144.228.205.145) 7 ms 4 ms 4 ms
5 144.232.24.206 (144.232.24.206) 4 ms 4 ms 4 ms
6 144.232.8.210 (144.232.8.210) 4 ms 0.xe-9-3-0.BR2.IAD8.ALTER.NET (204.255.169.217) 11 ms 11 ms
7 B100.NYCMNY-LCR-21.verizon-gni.net (130.81.209.103) 12 ms B300.NYCMNY-LCR-21.verizon-gni.net (130.81.199.155) 14 ms 14 ms
8 G2-0.NYCMNY-NYCMNY56-ERXG02.verizon-gni.net (130.81.193.114) 15 ms 15 ms 13 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * Max number of unresponsive hops reached (firewall or filter?)

news-europe.giganews.com

##################### 30 hops max, 60 byte packets
1 vl201.gw1.ams.giganews.com (216.196.110.3) 1 ms 1 ms 1 ms
2 te0-7-0-27.rcr21.ams05.atlas.cogentco.com (149.11.104.9) 0 ms 0 ms 0 ms
3 be2039.ccr42.ams03.atlas.cogentco.com (154.54.36.145) 1 ms be2038.ccr41.ams03.atlas.cogentco.com (154.54.36.133) 1 ms 1 ms
4 be2183.ccr22.lpl01.atlas.cogentco.com (154.54.58.69) 11 ms be2488.ccr42.lon13.atlas.cogentco.com (154.54.39.110) 8 ms 8 ms
5 be2490.ccr22.jfk02.atlas.cogentco.com (154.54.42.85) 80 ms be2489.ccr42.par01.atlas.cogentco.com (154.54.39.114) 89 ms be2490.ccr22.jfk02.atlas.cogentco.com (154.54.42.85) 81 ms
6 be2150.mpd21.dca01.atlas.cogentco.com (154.54.31.129) 87 ms be2148.ccr21.dca01.atlas.cogentco.com (154.54.31.117) 88 ms be2149.ccr22.dca01.atlas.cogentco.com (154.54.31.125) 86 ms
7 be2176.ccr41.iad02.atlas.cogentco.com (154.54.41.53) 91 ms be2149.ccr22.dca01.atlas.cogentco.com (154.54.31.125) 88 ms be2112.ccr41.iad02.atlas.cogentco.com (154.54.5.233) 86 ms
8 be2176.ccr41.iad02.atlas.cogentco.com (154.54.41.53) 91 ms verizon.iad01.atlas.cogentco.com (154.54.12.46) 89 ms be2177.ccr41.iad02.atlas.cogentco.com (154.54.41.205) 92 ms
9 B100.NYCMNY-LCR-21.verizon-gni.net (130.81.209.103) 93 ms verizon.iad01.atlas.cogentco.com (154.54.10.226) 90 ms B100.NYCMNY-LCR-21.verizon-gni.net (130.81.209.103) 90 ms
10 be2177.ccr41.iad02.atlas.cogentco.com (154.54.41.205) 99 ms P1-0-0-0.NYCMNY-LCR-21.verizon-gni.net (130.81.151.229) 96 ms G2-1.NYCMNY-NYCMNY56-ERXG02.verizon-gni.net (130.81.195.1) 93 ms
11 G2-1.NYCMNY-NYCMNY56-ERXG02.verizon-gni.net (130.81.195.1) 93 ms * verizon.iad01.atlas.cogentco.com (154.54.12.46) 100 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * * Max number of unresponsive hops reached (firewall or filter?)

Broadband Status

Broadband Parameter Status

VPI:	0
VCI:	35
Broadband Mode Setting:	ADSL2+
Broadband Negotiated Mode:	ADSL2+
Connection Status:	CONNECTED
Downstream Speed:	6208 Kbps
Upstream Speed:	636 Kbps
Retrains:	1
Retrain Timer:	0 Days, 4H:37M:8S
ATM QoS class:	UBR
Near End CRC Errors Interleave:	1330
Near End CRC Errors Fastpath :	N/A
Far End CRC Errors Interleave :	0
Far End CRC Errors Fastpath :	N/A
30 Minute Near End CRC Interleave :	0
30 Minute Near End CRC Fastpath :	N/A
30 Minute Far End CRC Interleave :	0
30 Minute Far End CRC Fastpath :	N/A
Near End RS FEC Interleave :	0
Near End RS FEC Fastpath :	N/A
Far End RS FEC Interleave :	0
Far End RS FEC Fastpath :	N/A
30 Minute Near End FEC Interleave :	0
30 Minute Near End FEC Fastpath :	N/A
30 Minute Far End FEC Interleave :	0
30 Minute Far End FEC Fastpath :	N/A
30 Minute Discarded Packets Downstream :	0
30 Minute Discarded Packets Upstream :	0
SNR Downstream :	28 dB
SNR Upstream :	23 dB
Attenuation Downstream :	27 dB
Attenuation Upstream :	11 dB
Power Downstream	21.4 dBm
Power Upstream	12.3 dBm

Gateway Memory

MemoryStatus

Total Memory:	59MB RAM
Memory Used:	46%
Memory Status:	OK
Recommended Action:	NONE

Gateway Sessions

SessionStatus

Maximum Number of Sessions:	4032
LAN TCP Sessions:	10
LAN UDP Sessions:	19
Gateway Sessions:	0
Total Open Sessions:	29
Session Status:	OK
Recommended Action:	NONE

[smith6612]

Here is what ASSIA is: http://www.assia-inc.com/

In short, it is a product that was developed, which Verizon licenses out to automatically manage their DSL network. ASSIA is designed to continuously monitor DSL connections. Based on both the billing package, and based on line conditions, ASSIA will make adjustments to the speed in an effort to maintain a balance between performance and stability. Many of us who are on touchy setups, like I am, or for those who have just had bad luck with ASSIA (like I have), opt to have Verizon turn it off and perform work manually.

What will happen is, now that your noise margin is at 28dB downstream and 23dB upstream, so long as you do not shut your modem off or your line begins to misbehave again, your speed will start to go up. This may take sometime from tonight, to even the next two days to happen. ASSIA should continue to crank the speed up until your connection is either at 15Mbps down, 1Mbps up, or it maxes out and nears the edge of stability.

In short, sit tight and see if the connection performs any better over the next few days.

[jonjonhan]

Aha!

So to be clear, I do not need to purchase nor download any software, correct?

The software will be automatically downloaded to the modem by itself, correct?

Is there a way I can check to see if the software is installed and working?

The link you gave to the company indicates software for the iphone/android, do I need it?

[smith6612]

There is no software on your end of things that need to be downloaded. This is a software solution that works with the DSLAM on Verizon's backend.

Has the speed gone up?