Hi
Hope you can give me some advice / pointers. My dad recently purchased Telkom's SmartBroadband Wireless Uncapped service and it has been running well until this morning.
Last night he had a power failure for a few hours and after everything came back on, he has no internet access.
The router is lit up normally in terms of lights on the front and he is able to access it (the B525).
However, when looking at the "Current Connection" setting it is showing an IP address in the 192.168 range.
Is this normal? Should that field not show a publicly routable WAN IP?
If he drops to command prompt on his directly connected PC, he just gets "destination net unreachable" when trying to ping google's 8.8.8.8 DNS.
Regards,
Peter
P.S. We have tried Telkom tech support but we're in a bit of a holding pattern given the response was "it is because you were throttled to 2Mbps" at which point my dad's protest resulted in them "logging a complaint which will be attended to within 72 hours".
Hope you can give me some advice / pointers. My dad recently purchased Telkom's SmartBroadband Wireless Uncapped service and it has been running well until this morning.
Last night he had a power failure for a few hours and after everything came back on, he has no internet access.
The router is lit up normally in terms of lights on the front and he is able to access it (the B525).
However, when looking at the "Current Connection" setting it is showing an IP address in the 192.168 range.
Is this normal? Should that field not show a publicly routable WAN IP?
If he drops to command prompt on his directly connected PC, he just gets "destination net unreachable" when trying to ping google's 8.8.8.8 DNS.
Regards,
Peter
P.S. We have tried Telkom tech support but we're in a bit of a holding pattern given the response was "it is because you were throttled to 2Mbps" at which point my dad's protest resulted in them "logging a complaint which will be attended to within 72 hours".


Probably sign into router and in settings make the necessary change. Power outage probably had a slight surge that wiped the settings