ZTE MF286D - Admin Web Interface Hangs / Crashes - ERR_CONNECTION_REFUSED

[DarrenJackson]

Hi

I have a new ZTE MF286D 4G Hub but I am finding the web user interface especially temperamental. It will frequently become unresponsive and then the browser (Chrome or Edge, PC or Android) reports ERR_CONNECTION_REFUSED and I am chucked out. Literally sometimes just logging in to the front page and then selecting Logout.

A network scan tool shows no response from the router having a web interface after this point either; whereas before the scan tool reports availabilty of a web interface. Presumably the scan tool does a quick scan of the LAN checking each device's basic capability / services.

The only solution is to turn the hub off and on again... which is rather disruptive.

Surely this is a very basic requirement and it concerns me if this is a software bug in the router what more serious issues are lurking in there?

My understanding is the router is running the latest software... I'll check when I can get back to the user interface.

Are there any other users with this issue and any known resolution / fix please.

Regards, Darren Jackson

[Darren_Jackson]

@PeteG the crashing user interface on the ZTE M286D router continues to be an issue as previously raised. I am hugely disappointed with Three being unable to acknowledge / respond / investigate this matter. Have you followed this up with ZTE? Have you tried to reproduce this problem? Why no support for your customers?

If you cannot resolve this please send me a newer model router free of charge that will be more suitable, future proof and reliable. There is also the issue of DHCP requests originating on the WiFi not passing to the wired LAN which means I cannot host my own DHCP server and use the ZTE for WiFi - hence WiFi is turned off on the ZTE. This was the subject of another thread that was also completely ignored.

https://community.three.co.uk/t5/Broadband/ZTE-MF286D-DHCP-Server-Disabled-Blocking-Access-to-Altern... <<< absolutely ignored outright...!

What's the solution please?

[PeteG]

Hi, Darren. 

The crashing issues isn't one I'm completely familiar with and seems to be quite isolated as far as I can tell. On this post, it looks like the user also had success in accessing the page through another device instead, so it's quite strange. 

I'm not sure what would be stopping DHCP requests going through, maybe having DHCP enabled is a requirement to successfully assign IP addresses to devices connecting directly to its Wifi. I'm not a member of the broadband team and don't have the ability to test or diagnose the issue, sadly. I also can't arrange to send you anything new as I don't have access to that kind of thing from here. 

My recommendation would be to speak to the broadband team about both issues and make a request for a replacement Hub. Hopefully they are able to supply a replacement. 

Pete.

[PeteG]

Hello. 

Oh, that's a strange issue to be having, especially since it's a local connection rather than a internet connection, there really shouldn't be anything getting in the way. It sounds like maybe the software on the hub is acting up? 

It might be worth trying a factory reset of the router instead, and then trying to run with it for a while on the default settings to see how it reacts. 

Pete. 

[Klaus-Ludwig]

I have a similar issue. I can log on to the user interface and make selections, but if I select "Access device" I get an empty blue box (instead of a list of devices), the interface system then hangs and becomes unresponsive. I can still select the home page, but no longer can I access any options and the home page data is missing. Rebooting the router enables me to log onto the user interface again and select any options apart from "Access device"

[KateS]

Hey @Klaus-Ludwig,

Can I check what it is you're trying to do on the 'Access device' option?

Could you also confirm the make/model of the router, please?

Thanks,
Kate

[DarrenJackson]

@Pete for now I am avoiding using one particular PC to access the ZTE web interface and sticking tentatively to an alternative in case the firewall on the particular PC is somehow blocking responses from the web interface - which would be very weird as it's just a browser interface?!