jpbarnard2019
Active Member
- Joined
- Oct 5, 2019
- Messages
- 45
- Reaction score
- 21
My DSTV Explore 2 Remote Record feature has broken. Previous time I used the feature, about 2 months ago, it still worked. Last week, after switching from ADSL to fibre (and from an ADSL modem/router to a fibre modem + separate router), the service has become troubled. I can confirm with certainty that the switch over is not the cause, because I have tested the feature with both ISPs and both routers (new router and old ADSL modem/router).
Symptoms:
When one attempts to schedule a recording of a DSTV program via one's DSTV Now app on a cell phone, the response is Service Error. However, the Explora 2 Connection Checker returns OK status for Remote Record feature. All connection items return OK status. To add confusion, upon inspection of the recording schedule on the decoder, the remote scheduled recording occasionally appears in the schedule, but not consistently so. A similar thing happens when one attempts to schedule a program via guide.dstv.com.
Configuration:
Fibre service by SADV is served by their fibre modem. Routing into my home network is done by Afrihost's D-Link DIR825AC G1 WiFi router (firmware 3.0.6). The router connects via LAN cable from its WAN port to the fibre modem's LAN 1.
I have assigned a static IP to the decoder, which connects via WiFi 2.4GHz to the router. In order to get OK status on all features from Explore 2 Connection Checker, I forward the port used by the decoder to the external IP of Multinet. I have retrieved the external IP and port by inspecting the current WiFi client table via the router's management console.
My cell phone is a BlackBerry DTEK50 running Android 6. As mentioned, the DSTV Now Remote Record did work before my switch over to fibre. So, it is unlikely to be the phone.
Some things I have tried in vain:
Resolution:
The issue remains frustratingly unresolved. Are there special settings for the D-Link DIR825AC G1 that fixes this issue? Why does the request/response exchange function up to the final confirmation message, which haplessly fails.
Symptoms:
When one attempts to schedule a recording of a DSTV program via one's DSTV Now app on a cell phone, the response is Service Error. However, the Explora 2 Connection Checker returns OK status for Remote Record feature. All connection items return OK status. To add confusion, upon inspection of the recording schedule on the decoder, the remote scheduled recording occasionally appears in the schedule, but not consistently so. A similar thing happens when one attempts to schedule a program via guide.dstv.com.
Configuration:
Fibre service by SADV is served by their fibre modem. Routing into my home network is done by Afrihost's D-Link DIR825AC G1 WiFi router (firmware 3.0.6). The router connects via LAN cable from its WAN port to the fibre modem's LAN 1.
I have assigned a static IP to the decoder, which connects via WiFi 2.4GHz to the router. In order to get OK status on all features from Explore 2 Connection Checker, I forward the port used by the decoder to the external IP of Multinet. I have retrieved the external IP and port by inspecting the current WiFi client table via the router's management console.
My cell phone is a BlackBerry DTEK50 running Android 6. As mentioned, the DSTV Now Remote Record did work before my switch over to fibre. So, it is unlikely to be the phone.
Some things I have tried in vain:
- Logged out of DSTV Now, rebooted cell phone. Logged in to DSTV Now app.
- Rebooted router after configuration change.
- Rebooted Explora 2.
- Contacted DSTV via Twitter.
- Found and forwarded the port range 9000 to 55555 for the remote IP that the decoder uses (197.80.203.24:55555). Here I have tried as alternative to forward the port for the entire segment 197.80.203.0/24, but to no avail. The IP and port can be found at the DSTV client session in the D-Link admin console under Statistics/[Clients and Session].
- Disabled the Firewall DoS Protection
Resolution:
The issue remains frustratingly unresolved. Are there special settings for the D-Link DIR825AC G1 that fixes this issue? Why does the request/response exchange function up to the final confirmation message, which haplessly fails.
Last edited: