NTL Problems

GreeBo

Hey,
Im having real problems with my ntl 1/100 connection the last week or two
Keep getting kicked out of games and very slow browsing, but its not a constant problem, comes and goes

tonight Im getting this

ping -n 20 www.yahoo.co.uk

Pinging www.euro.yahoo.akadns.net [217.12.3.11] with 32 bytes of data:

Reply from 217.12.3.11: bytes=32 time=22ms TTL=242
Reply from 217.12.3.11: bytes=32 time=28ms TTL=242
Reply from 217.12.3.11: bytes=32 time=437ms TTL=242
Reply from 217.12.3.11: bytes=32 time=447ms TTL=242
Reply from 217.12.3.11: bytes=32 time=2541ms TTL=242
Reply from 217.12.3.11: bytes=32 time=1282ms TTL=242
Reply from 217.12.3.11: bytes=32 time=24ms TTL=242
Reply from 217.12.3.11: bytes=32 time=2749ms TTL=242
Reply from 217.12.3.11: bytes=32 time=20ms TTL=242
Reply from 217.12.3.11: bytes=32 time=24ms TTL=242
Reply from 217.12.3.11: bytes=32 time=23ms TTL=242
Reply from 217.12.3.11: bytes=32 time=22ms TTL=242
Reply from 217.12.3.11: bytes=32 time=28ms TTL=242
Reply from 217.12.3.11: bytes=32 time=22ms TTL=242
Reply from 217.12.3.11: bytes=32 time=21ms TTL=242
Reply from 217.12.3.11: bytes=32 time=27ms TTL=242
Reply from 217.12.3.11: bytes=32 time=22ms TTL=242
Reply from 217.12.3.11: bytes=32 time=25ms TTL=242
Reply from 217.12.3.11: bytes=32 time=24ms TTL=242
Reply from 217.12.3.11: bytes=32 time=25ms TTL=242

Ping statistics for 217.12.3.11:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 2749ms, Average = 390ms

ping -n 20 www.yahoo.co.uk

Pinging www.euro.yahoo.akadns.net [217.12.3.11] with 32 bytes of data:

Reply from 217.12.3.11: bytes=32 time=28ms TTL=242
Reply from 217.12.3.11: bytes=32 time=36ms TTL=242
Reply from 217.12.3.11: bytes=32 time=23ms TTL=242
Reply from 217.12.3.11: bytes=32 time=22ms TTL=242
Reply from 217.12.3.11: bytes=32 time=21ms TTL=242
Reply from 217.12.3.11: bytes=32 time=22ms TTL=242
Reply from 217.12.3.11: bytes=32 time=21ms TTL=242
Request timed out.
Reply from 217.12.3.11: bytes=32 time=23ms TTL=242
Request timed out.
Request timed out.
Reply from 217.12.3.11: bytes=32 time=37ms TTL=242
Reply from 217.12.3.11: bytes=32 time=24ms TTL=242
Reply from 217.12.3.11: bytes=32 time=22ms TTL=242
Reply from 217.12.3.11: bytes=32 time=21ms TTL=242
Reply from 217.12.3.11: bytes=32 time=22ms TTL=242
Reply from 217.12.3.11: bytes=32 time=37ms TTL=242
Reply from 217.12.3.11: bytes=32 time=22ms TTL=242
Reply from 217.12.3.11: bytes=32 time=23ms TTL=242
Reply from 217.12.3.11: bytes=32 time=21ms TTL=242

Ping statistics for 217.12.3.11:
    Packets: Sent = 20, Received = 17, Lost = 3 (15% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 37ms, Average = 25ms

and also from the diagnostics

Downstream Lock : 	Locked
Downstream Channel Id : 	40
Downstream Frequency : 	402000000 Hz
Downstream Modulation : 	QAM64
Downstream Symbol Rate : 	5056.941 Ksym/sec
Downstream Interleave Depth : 	taps32Increment4
Downstream Receive Power Level : 	-18.9 dBmV
Downstream SNR : 	21.3 dB

looking at ntl.com I saw that

Downstream SNR: should be 30 dB or higher: the higher the better. As the SNR decreases below 30 dB, performance will steadily decrease, and errors will increase. The cable modem might stop working properly if the SNR drops below 23.5 dB.
Downstream Received Power: the DOCSIS specification requires cable modems to function correctly with downstream power levels in the range -15 dBmV to +15 dBmV: power readings at or close to those extremes are likely to be unacceptable.

Has anyone else had any problems?
Ive rebooted the modem but the problems still come back..
And I was so bloody happy with ntl.

kin9pin

No problems here in Sandyford:

Downstream Lock : Locked
Downstream Frequency : 402000000 Hz
Downstream Modulation : QAM64
Downstream Interleave Depth : 32
Downstream Receive Power Level : 4.1 dBmV
Downstream SNR : 36.1 dB


Ping:

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=23ms TTL=50
Reply from 82.133.85.65: bytes=32 time=23ms TTL=50
Reply from 82.133.85.65: bytes=32 time=22ms TTL=50
Reply from 82.133.85.65: bytes=32 time=22ms TTL=50

Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 23ms, Average = 22ms

The tax man

What's your upstream transmit level?
Your downstream SNR is crap.

Drapper

D15

PING WWW.ESAT.IE

Pinging WWW.ESAT.IE [193.95.153.20] with 32 bytes of data:

Reply from 193.95.153.20: bytes=32 time=9ms TTL=117
Reply from 193.95.153.20: bytes=32 time=10ms TTL=117
Reply from 193.95.153.20: bytes=32 time=9ms TTL=117
Reply from 193.95.153.20: bytes=32 time=10ms TTL=117

Ping statistics for 193.95.153.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 10ms, Average = 9ms

GreeBo

The tax man wrote:

What's your upstream transmit level?
Your downstream SNR is crap.

Upstream transmit Power Level : 36.0 dBmV
yeah I noticed that allright

The tax man

GreeBo wrote:

Upstream transmit Power Level : 36.0 dBmV
yeah I noticed that allright

Well the nearer to 61dBmV the harder the modem is working to reach the network.So you'd think 36.0dBmV seems great but I'm afraid not.(norm would be high 40s to mid 50s)
Sounds like your levels are way too high in the area and this is causing noise,hence the poor SNR reading.
Best ring NTL if it keeps up.
If you can check it mid day tomorrow and see what you get.

GreeBo

Yeah, I popped off a mail (eventually) with some details (pings, tracerts and modem diag's)
Ive also noticed that my teletext is not coming through 100% anymore also.
I wonder could something have happened somewhere along the line and screwed it all up?

The tax man

Yeah it would alright. I was going to ask about the TV reception alright.
Sometimes it can look alright but if your text is acting up I'd say it's a noisy signal due to high levels.
Are you seeing any noisy TV pictures??
Whitish lines over pictures?
Some TVs can handle such levels and give fine pictures put the text thing says otherwise.

DingDong

Your problem is down to the signal level being too low. It should be around
-5dBmV at most. On a side note NTL digi boxes work down to -15dBmV. Their must be a line fault possible the drop or further back


Downstream Receive Power Level : -18.9 dBmV

iluvbeer

Noticed a few problems myself over the last few days too, Im in Manorfields Clonee, where are you located GreeBo?

Random drops on connection, I thought it was my wireless connection for a while but going directly through the modem showed that it was coming from the line itself. Power-cycling the modem doesn't seem to work as the connection comes back itself anyway after a few moments.

Where did you get the diagnostics from? I'll check those out when I get home.

GreeBo

Im in Knocklyon..
if you go to 192.168.100.1 you are basically connecting to your modem and there are various options there
Login is root/root

iluvbeer

Cheers GreeBo, I'll post back this evening with a summary.

I haven't noticed any problems with the TV reception in the last few days but I'll check the teletext reception to be sure. It was all going so well with NTL so far, hope this is sorted out quick, very annoying when you con't complete a big upload/download without at least one drop in connection.

Freddie59

DingDong wrote:

Your problem is down to the signal level being too low. It should be around
-5dBmV at most. On a side note NTL digi boxes work down to -15dBmV. Their must be a line fault possible the drop or further back


Downstream Receive Power Level : -18.9 dBmV

You car can also clock 160 Kph - but you NEVER run anything flat out. Mid range is always best. That box will go ballistic as it's on the extreme. If you have even a minor fluctuation it will go belly-up.:eek:

iluvbeer

Downstream Lock : Locked
Downstream Channel Id : 1
Downstream Frequency : 418750000 Hz
Downstream Modulation : QAM64
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : -8.2 dBmV
Downstream SNR : 36.9 dB

Upstream transmit Power Level : 53.0 dBmV

Everything here seems to be in order according to the comments above,
however I've had 5-6 drops in connection since I logged on at 7pm -ish.

Will the event log show anything useful or is there something in particular that I should be looking for?

Gibber

My line signals are fine but tonight I've had absolutely horrendous connections, but its been getting steadily worse for the last few weeks. WoW is now impossible to play, I'm getting disconnected every 5-10 minutes (if I'm lucky). I've tried streaming a net radio station and thats freezing in the same time period.

Until now I've been very happy with NTL - I'll give them a buzz tomorrow and find out what's happening. I'm out near sandymount.