View Full Version : GL52 area
Hi there,
Is anyone else been having extremely slow speeds, actually stopping alot of the time in the GL52 area?
I can't find nothing on the VM site, takes me ages to get there anyway. Its been going on for 2 days now!
Thanks
Ninko
I assume its just me then.
Ninko
go to tools, internet options, connections, lan settings, tick use a proxy server
put in webcache.blueyonder.co.uk and port 8080
Oh right, whys that then, are there Virgin Media problems?
Ninko
yeah we are having some issues
Hi there,
Still having the same problems, got an tech guy coming down as my downstream power level is 14 dB (13 dB at this min lol) which so I'm told is too high, not sure whats causing that?
Also I was looking at my modem logs and was wondering if someone could shed some light on what it all means lol...
TimePriorityCodeMessage2007-08-09 10:49:195-Warning0x040DC13CDHCP RENEW WARNING - Field invalid in response2007-08-08 21:41:133-Critical0x04E33A74Started Unicast Maintenance Ranging - No Response received - T3 time-out2007-08-07 14:36:094-Error0x041D050CSW upgrade Failed after download - Incompatible SW file2007-08-07 14:36:086-Notice0x041D0318SW Download INIT - Via Config file cm-2148-2562007-08-07 14:36:076-Notice0x045A80E4TLV-11 - unrecognized OID1970-01-01 00:00:163-Critical0x040D9A2CDHCP WARNING - Non-critical field invalid in response.2007-07-22 12:00:036-Notice0x041D0318SW Download INIT - Via Config file cm-2148-2562007-07-22 12:00:026-Notice0x045A80E4TLV-11 - unrecognized OID1970-01-01 00:00:123-Critical0x040D9A2CDHCP WARNING - Non-critical field invalid in response.2007-07-21 21:56:286-Notice0x041D0318SW Download INIT - Via Config file cm-2148-2562007-07-21 21:56:286-Notice0x045A80E4TLV-11 - unrecognized OID1970-01-01 10:13:543-Critical0x040D9A2CDHCP WARNING - Non-critical field invalid in response.1970-01-01 10:13:453-Critical0x04E33948No Ranging Response received - T3 time-out1970-01-01 10:13:283-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:12:183-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:12:153-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:12:073-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:12:063-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:11:553-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:11:553-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:11:543-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:11:543-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:11:533-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:11:533-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:11:473-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:11:413-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:11:383-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:11:333-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:11:333-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:11:323-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:10:533-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:10:493-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:09:323-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:09:273-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:09:273-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:09:253-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:09:253-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:09:203-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:06:493-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:06:423-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:06:233-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:06:163-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:05:383-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:05:383-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:05:373-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:05:363-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:05:363-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:05:333-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:05:043-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:05:013-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:05:013-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:04:573-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:04:463-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:04:403-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:04:023-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:04:013-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:04:013-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:04:003-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:593-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:583-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:583-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:573-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:483-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:473-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:463-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:463-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:423-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:423-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:363-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:363-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:353-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:343-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:333-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:333-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:323-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:313-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:313-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:313-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:283-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:283-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:263-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:253-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:233-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:223-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:133-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:123-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:103-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:103-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:073-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:063-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:03:003-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:03:003-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:02:593-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:02:583-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:02:573-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:02:573-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:02:563-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:02:553-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 10:02:553-Critical0x0501BD64SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing1970-01-01 10:02:553-Critical0x0501BDC8SYNC Timing Synchronization failure - Failed to acquire FEC framing
Thanks
Ninko
tbh, not sure what causes the high power levels, but it is def high and that will cause slow speeds.
ignore the modem logs. we never use them.
only thing we use from the config page is the siganl page to check the levels.
tech will probably just replace your modem when he comes out
if its high power levels the modem wont get replace its the green box he goes to
Green box, is that the box outside? Do you know what can cause it then vmtech?
Its strange because that high power had been like that since we joined VM broadband (about a month ago), and up untill the last 4 days the connection was fine.
Ninko
:dunce:
sorry, thats actually a valid point now that i think about it.
sorry, i meant valid point about him goin to the green box
and yeah the green box is the on eoutside though you will still have to be in when he visits.
it may not be the power level, but its is certainly out of range so beter to get that sorted and then can at least rule it out of being the problem
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.