Unable to access 2.4 GHz printer from computer on 5 GHz network

[#1]

My Plusnet Hub Two has a computer connected on the 5 GHz wifi, and a printer connected on the 2.4 GHz wifi.

Devices on the different frequencies are unable to communicate with each other.

I cannot find a setting within the router which would bridge / forbid the two networks from communicating.

Any advice on how to get the two frequencies communicating?

[#2]

This shouldn't be a problem.

Is the network connection set to private and discoverable on the computer?

I'm fairly certain I've done the same in the past without issue.

[#3]

> This shouldn't be a problem.

Indeed not.

> Is the network connection set to private and discoverable on the computer?

I can reach other 5 GHz devices without issue.

> I'm fairly certain I've done the same in the past without issue.

I was previously with BT with a home hub 2, which worked just fine with the same devices.

[#4]

Did you reconfigure the printer when changing suppliers?

[#5]

---

@AnthonyEdmonds wrote:

> Is the network connection set to private and discoverable on the computer?

I can reach other 5 GHz devices without issue.

---

So, is that a 'yes'?

The BT Smart Hub 2 and Plusnet Hub Two share very similar foundations, so it would be odd for one to work and not the other.

If your Wi-Fi network name has changed, then it's probably also worth a full factory reset/reconfiguration of the printer.

[#6 · Accepted solution]

I managed to solve it myself.

Both the computer and the printer were absolutely fine, the router was indeed at fault.

Checking the firewall port forwarding rules, I noted that there were three rules pointing to my computer called "RSX Port Mappin".

I did not create those rules, and I have no idea where they came from.

The router would not let me delete them until I disconnected my computer and reset the router.

Upon reconnection with the router everything is working properly.

Very odd.

[#7]

Sounds like those rules were created automatically by a service running on the computer using UPnP.
Disabling UPnP in the Hub Manager would prevent this happening, however it may be worth trying to establish exactly what was responsible, and whether or not the port mappings are actually required for anything.