Good morning gurus, I have a weird problem.
I have a client on a 2 meg adsl line who has been having 3 months of grief trying to get their internet to work. Multiple calls to 10210 and multiple technician visits have failed to sort the problem.
Client has a telkomsa account which appears to connect, pings to google or telkom are successful, some sites load (very slowly), most timeout. Account is 40 Gb softcap, useage is 3 gb, so it's not capped. 10210 says account is paid up, in good standing, and there are no issues their side.
I was only called in yesterday. I look at various things: SNR, attenuation, noise, etc, all good. Tried 2 different modems, same issue. Then I put a vox account on the modem. Internet flies - 100% working. Tried an Mweb account - ditto. Afrihost free - ditto. Back to client's telkomsa account - dead.
Called 10210 again. They did a port re-create and changed the password. No difference, internet dead. The said internet username and password works as it logs in to the various telkomsa portals like titracker and password management, although only when the internet is connected with an isp account other than a telkom account.
I even tried my own telkom internet account and the same, which really messed with my head as now it looks like the line just doesn't like telkomsa accounts.
WTF can this be? line is connected to the Pine Lake Marina remote isam 2km outside of town. SNR was 36 downstream and attenuation 21, which is about right as there is about a km and a half of copper between the isam and the premises. Telkom call centre has admitted the issue requires specialist attention but they couldn't say when, how or where this would come from.
My theory is that there is some sort of radius authentication issue somewhere, maybe at the isam, that is having hissy fits with telkomsa accounts. AFAIK there are minimal users on this isam, possibly less than a dozen.
Ranger? MickeyD?
In the meantime I have left my own vox account on their modem so they at least have internet for a week or two until the problem can get sorted.
Thanks for reading.
I have a client on a 2 meg adsl line who has been having 3 months of grief trying to get their internet to work. Multiple calls to 10210 and multiple technician visits have failed to sort the problem.
Client has a telkomsa account which appears to connect, pings to google or telkom are successful, some sites load (very slowly), most timeout. Account is 40 Gb softcap, useage is 3 gb, so it's not capped. 10210 says account is paid up, in good standing, and there are no issues their side.
I was only called in yesterday. I look at various things: SNR, attenuation, noise, etc, all good. Tried 2 different modems, same issue. Then I put a vox account on the modem. Internet flies - 100% working. Tried an Mweb account - ditto. Afrihost free - ditto. Back to client's telkomsa account - dead.
Called 10210 again. They did a port re-create and changed the password. No difference, internet dead. The said internet username and password works as it logs in to the various telkomsa portals like titracker and password management, although only when the internet is connected with an isp account other than a telkom account.
I even tried my own telkom internet account and the same, which really messed with my head as now it looks like the line just doesn't like telkomsa accounts.
WTF can this be? line is connected to the Pine Lake Marina remote isam 2km outside of town. SNR was 36 downstream and attenuation 21, which is about right as there is about a km and a half of copper between the isam and the premises. Telkom call centre has admitted the issue requires specialist attention but they couldn't say when, how or where this would come from.
My theory is that there is some sort of radius authentication issue somewhere, maybe at the isam, that is having hissy fits with telkomsa accounts. AFAIK there are minimal users on this isam, possibly less than a dozen.
Ranger? MickeyD?
In the meantime I have left my own vox account on their modem so they at least have internet for a week or two until the problem can get sorted.
Thanks for reading.
