AX866U issue with certain devices not able to connect to printer

[lcalamar]

Some (but not all) of my devices that are connected to my RT-AX86U router lose the ability to connect to my wifi connected Brother printer.

Because some (my android devices and my linux computers) do NOT lose connection - and can print at anytime... so there is no issue with the printer>Router connection.

The devices that lose the ability to connect are IOS and a Windows PC...

I've put in a work-around by rebooting my RT-AX86U every morning at 6am...

I've looked at a number of 'solutions', changed several router settings based on other people's experiences - but this seems to be a router issue?

Anyone had any success with a real fix?

 

[degrub]

Can you ping the printer's IP address from those devices ?

What printer driver is IOS using ?

Apple requires a flat network e.g. all devices on the same subnet.

Is Bonjour protocol enabled on the networking page somewhere ( i don't know where this is in ASUS GUI) ?

Did you load the Brother printer APP on the IOS devices ?

 

[lcalamar]

Can you ping the printer's IP address from those devices ?

What printer driver is IOS using ?

Apple requires a flat network e.g. all devices on the same subnet.

Is Bonjour protocol enabled on the networking page somewhere ( i don't know where this is in ASUS GUI) ?

Did you load the Brother printer APP on the IOS devices ?

I can currently ping the printer - but the router rebooted last night so that may not be indicative... I won't reboot the router tonight and try pinging tomorrow when we can't print from that device.

No idea what printer driver IOS is using... not an IOS capable admin!

All devices are on the same subnet.

Not sure about Bonjour - I'll have to research that a bit.

Since the problem happens on both the IOS and Windows devices... and rebooting the router always resolves the issue... I'm less inclined to think the problem resides on the client side... but I could certainly be wrong... Note: doing research I've found a number of online threads that pretty much identify this is a router issue...