I have an hp laserjet 1300 printer hard wired to my network. Prior to upgrading wo windows 10 I was able to print to this printer from all devices on my network whether they were wired or wireless. Now since upgrading to windows 10 the only way I can print to this printer is when I hard wire the device I want to print from to the network. Is this a Windows 10 issue? I also have my printer assigned to a static ip address on the network.

The Win 10 upgrade did expose some wireless problems. Go to the windows support community to review the questions and answers

You may have to redo the sharing of the printer.

I think these steps still apply to Win10: Share a printer - Windows Help

If I connect my laptop to the network via ethernet I can ping the ip address of the printer and print with no problems. However, if I unplug my laptop ethernet cable and connect to the network wireless, I am not able to ping the ip address of the printer the ping times out. The only things that have changed is that I have recently moved to a new address, but the equipment is still the same, but I upgraded from windows 7 to windows 10. When I am connected wireless, it shows the printer as offline. When I connect the ethernet cable I am able to access the printer via web browser and I can print to it.

I fixed this issue. I did some checking in the router and I realized that I had wireless isolation enabled which was only giving me internet access only and not access to other devices on the network. Thanks for everyone's responses.

Quote:

---

I realized that I had wireless isolation enabled

---

Did you figure out how that happened? I'm upgrading one of my computers to Win10 tonight.

Yeah when I was checking the settings in my router I accidentally turned on wireless isolation which gives all wireless devices access to the internet, but will not allow them to access other devices on the network such as printers and other computers. Upgrading to windows 10 should be fine, I thought my problem was related to upgrading to windows 10 but it was a setting in my router.

Ok, cool. Glad you got it sorted out, nice troubleshooting.