Windows 10: Workgroup PCs using network printers getting Access Denied

Hi all, I have a network that is a workgroup with a 2019 File and Print Server. I am having all kinds of weird issues. I can add printers to the PCs in most cases without issue and they connect and can print, but then after a day or so all of the printers connected via the print server state "Access Denied" in the Device and Printers screen. I can remove them and add them again, but the same thing eventually happens. All machines in the network are Win10, some are different versions. Does this have to do with PrintNightmare and patches? The printers on the server all have the Everyone ca

:)

 

Workgroup and Networks

Is the workgroup a subset of a network. I have 2 laptop computers and 1 wired printer which I want to be able to interface with each other . What is the best way to set up this connection? Is there a simple step by step instruction on how to set up a
connection? I am using windows 10 on 2 Dell PC's and a HP printer.

 

Home Network and shared printer access problems

Hi,



Thank you for writing to Microsoft Community Forums.



We understand your concern, as you are having issue with accessing the files and printer within the network and in order to get clarity and to assist you accordingly, please reply with the answers to the questions below.

• What is the error message you get, while accessing the file or the Printer using Windows 7 PC?
  
• Are you aware of any recent changes on the PC, prior to this issue?
  

Meanwhile, we would suggest you to perform all the steps in all the PC that are connected in the network as suggested by Roohi Taj on January 8th, 2019
in this
post.



As an additional information please refer the below articles:

File sharing over a network in Windows 10

Share files in File Explorer



We await your response.



Aditya Roy

Microsoft Community – Moderator

 

Did our Epson printer get hacked?

Another question, is this on a home network or a work network? The steps @eidairaman1 listed are always a good first step. If this is on a work network you manage, I'd be much more concerned than the home one. It is possible someone is screwing with you, but malware could also be the culprit.