![]() ![]() ![]() |
|
How could they mind just posting a street name? It's just a street name I am not asking for complete address and credit card number and bank account number and PIN number
Linux
Without knowing a rough location and sync rates there absolutely nothing anybody on here can offer in the way of advice.
Are they on a VDSL2 connection? I'm surprised they can even sync at such a low speed.
Assuming they are on VDSL2 my pick right now with fairly high certainty would be a slowish VDSL2 connection that's being saturated on the upstream by the user uploading data (such as torrent uploads) that's causing the slow speeds and high latency.
cheers sbiddle. well both the account, the sign up form and chorus say VDSL. are you familiar with that router? The red and silver ones. Ill try to talk them through it tomorrow.
is there a link to the cabinet map?
Until you provide further INFO as requested we can't help you any further, If they have been connected to VDSL then it seems like they have a major house wiring issue or need to be moved to ADSL2+
Linux
Ok I know the cabinet was upgraded during the 2011 Urban ADSL2+ upgrade. Im asking more detail about their internal wiring. Being an older farm house who knows what condition its in.
Thanks all for the help, I dont think there is much anyone else on here can do that I dont know. Ill get onto it tomorrow for them. Appreciate the help.
Then it's down to a few options! They were connected to VDSL and they are too far from the serving exchange / cabinet or they have real bad bad house wiring
Until you get the xDSL line stats from the modem and post them we are working blind
Linux
Cheers mate but I think ive solved it ROFL, the clown hasnt set their router up correctly. sorry for the post.
Nope actually that didnt fix it, Ill get into the router tomorrow and get the sync rate. Just looking for another street for ya. But ive used Chorus lookup etc. Not sure what else there is to check as there is no cabinet maps.
Ill have someone test the line.
Few situations this could be..
a, they have have line fault
b, they realistically should not have vdsl - regardless of what the websites say, that is a calculated value not an actual value.
c, The modem is incorrectly setup
d, Their internal wiring is trash, vdsl is more sensitive to this.
Unless you provide further details nobody here can answer whats best
however; the customer should be speaking to their rsp, who will have raw access to all the little details to obviously answer this most effectively.
As to the actual question, are they being ripped off.
In a customer satisfaction sense, sure. their wallet is being hit the same as those who pay for fibre.
in a legal, reallife standpoint. no, they pay for a service that is best effort.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
cheers hio, you get it mate.
im not working in telco right now so there is no testing i could do even if they were closer.
ive ran them through their setup, i thought it was because they had no filter on, but it made no difference.
so ill get them to ring 2degrees faults. knowing the area, the copper is subject to being not well maintained and weathered. i also cant garuntee their own internal wiring isnt at fault, but from a testing perspective i know thats piece of cake to sus out remotely where the fault lies, if its internal they are more than willing to fix it as its essentially spending $80 a month for nothing. if its not their fault, they clearly wont be too happy as the service is unusable for todays content.
TeaLeaf:
cheers hio, you get it mate.
im not working in telco right now so there is no testing i could do even if they were closer.
ive ran them through their setup, i thought it was because they had no filter on, but it made no difference.
so ill get them to ring 2degrees faults. knowing the area, the copper is subject to being not well maintained and weathered. i also cant garuntee their own internal wiring isnt at fault, but from a testing perspective i know thats piece of cake to sus out remotely where the fault lies, if its internal they are more than willing to fix it as its essentially spending $80 a month for nothing. if its not their fault, they clearly wont be too happy as the service is unusable for todays content.
simply being in the rsp space does not mean testing makes a fault a piece of cake to resolve, faults can still fall into a few categories..
a, an obvious line fault, shows up on a NTS
b, an line fault evident from further deep analysis
c, user assumptions.
Being that i'm on the side where we spend a fair bit of time narrowing down logic calls to the nth degree before flagging faults, this can be a bit more of a structured situation.
i'll be honest though, i don't think i said anything different to anyone else simply wording.
Also remember faults could be on both sides
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
yeah i know mate, use to do it 20 years ago, i just meant at least the old guy will be able to find out where the fault lies. thanks for the help.
Is it a IP address or a webpage to access these fritzbox admins so I can run the old guy through it to get this Sync info asked for by Linux?
There mate 100m down a side road is getting 15Mbps down and 6Mbps up haha, must be frustrating.
My gut feeling is its a line fault, but Ive advised them they may need to rewire their housing wire (or Ill come down and do it for them). They have no issue with that, they just want to know where the fault is so it can be fixed.
It was only due to them skyping they realised their net was slow (skype just wont work at all even just voice). So the son gave me a call as hes not technical at all either.
Ive never seen one of these fritzbox so this should be fun.
Edit: NVM it seems to be "http://fritz.box or the address 169.254.1.1"
|
![]() ![]() ![]() |