Windows 10: Problem connecting to network wireless printer.

I am trying to hook up to a wireless network printer in windows 11.I just upgraded to windows 11 and my wireless printer was visible and printed. After a couple of weeks, it does not recognize the printer any more.The printer is a Canon Maxify MB2320. It worked fine in Windows 10 and worked for a short time in Windows 11.When trying to install, it does not recognize any printer on the network.Ipads and phones easily recognize and print wirelessly to this printer.Any suggestions?Thanks for any help.

:)

 

Problems connecting to wireless printer


We have a new (albeit old) wireless printer (HP Color laserjet CP3525) with a wireless adapter card. Computers running Windows 7 or Windows 8 could see the network and connect. All computers could then print to the printer. None of our computers running Windows 8.1 could see the network. I upgraded one computer to Windows 10. It can now see the printer network but cannot connect. Any suggestions or ideas of what is wrong and/or how to fix this issue? Thanks in advance for any help.

 

Problems connecting to wireless printer

What is the brand and model of the wireless adapter card? You may have to go to the manufacturer's website and get Windows 10 supported driver or whatever latest driver they have.

 

Unable to print to a network printer when connected to both wireless and wired networks

Hi Eileen,

• As far as i'm aware nothing has changed
• i have only tried to send test pages to the network printer so im assuming so yes
• wireless printer works fine when connected to both networks. However the wifi doesn't connect auto when an Ethernet connection is established this has to be manually connected.

I have tried the following:

• updated the print driver
• changed the network port it was plugged into
• ran windows updates
• configured with a static
• changed the wifi and Ethernet priority

I will run through the trouble shoot steps as suggest and come back to you.

FYI - he has a number of extenders dotted around, a collegue mentioned it could be a subnet issue?

thanks, Ben