TP-Link BE930 - can't print (but can can connect to the printer)
I've upgraded my old TP-Link Archer router to new Archer BE930. I've set up the wifi to be exactly the same and mapped DHCP static leases to be the same as in the old router, so that I don't have to reconfigure my network.
Now my Xerox WorkCentre 6515 usually works without any issues from any device in the network. After the router replacement I can't print to the printer.
I can connect to printer's web interface via IP-address, I can add printer manually via IP address in Xerox software, I can SCAN from it by using Xerox Software
but Windows does not see it as a printer and can't print to it.
Also when I try to start a scan from the printer to upload scanned files to FTP Server (yes, I know!), that upload is blocked. The FTP is up and available, I checked.
So something in the new router is blocking traffic from the printer, but not all traffic. HTTP and scan requests are allowed, but not printing or FTP.
Can't print:
I can reach printer via HTTP:
SPI Firewall is turned off on the router:
AP Isolation is also off:
What else is causing this in the router?
Many thanks!
Max
@Joseph-TP, thanks for looking into this.
I have just tried auto-update, and there was no new version found.
Here it the topology:
[ISP Modem (192.168.1.1)] ----- (LAN Cable) ----- [(192.168.1.204)TP-Link Router(192.168.0.0/24)] --- (WiFi)--- [Printer (192.168.0.134), other clients].
The TP-Link router is ethernet-cable connected to ISP router/modem. ISP router is using 192.168.1.1/24.
TP-Link router is in routing mode, using 192.168.0.0/24 network. Printer's IP address is fixed, printer is connected via WiFi.
No OpenVPN, enabled MLO Network, but printer is few years old and is connected to 5G WiFi.
Here is how routing table looks:
I've not done any changes to it - auto-generated.
I have a PiHole DNS server running and the router's configured to use that as a primary DNS server:
Are you looking to see if anything specific is turned on?
Again, thanks for helping!