Printer not working for normal users

[Chxiz]

Hi, i have a problem with printer / printserver
I have added a printer in my printserver, but when i try to print anyting from a domain user, nothing is coming out. But when i log on with admin, then the printer works. On sicurity on the pritenr it says that everyone can use it. And when i try to add like a user from AD or a group i get this message "An object (User, Group or built-in principal) with the following name cannot be found: "username". Check the selected objetc types and locatons for accurasy and ensure thet you have typed the object name correctly, or remove this object from the selection"

 

[ChatGPT]

It seems like there may be a permissions issue with the printer for domain users. Here are a few troubleshooting steps you can try:

1. Check Printer Permissions:
   • Open the printer properties on the print server.
   • Navigate to the Security tab.
   • Verify that the "Everyone" group has the necessary permissions (e.g. Print, Manage Printers).
   []Check Group Policy Settings:
   • Run gpresult /h report.html on the client machine to generate a Group Policy report.
   • Check if there are any policies applied that might be affecting printer access for domain users.
   • Pay particular attention to policies related to printer deployment and security settings.
   []Verify AD User/Group Existence:
   • Double-check the usernames or group names when adding them to the printer's security settings.
   • Ensure that the users/groups actually exist in Active Directory.
   • Check for any typos or special characters that might be causing the error message.
   []Restart the Print Spooler Service:
   • Open the Services console on the print server.
   • Locate the "Print Spooler" service and restart it.
   • This can sometimes resolve issues with printer permissions not taking effect immediately.
   []Test with a Different Printer:
   • If possible, try adding a different printer to the print server and see if the issue persists.
   • This can help determine if the problem is specific to this particular printer or a more general issue with printer permissions.
2. Update Printer Drivers:
   • Make sure you have the latest printer drivers installed on the print server.
   • Outdated or incompatible drivers can sometimes cause printing issues. If none of the above steps resolve the issue, please provide more details about your environment, such as the Windows Server version, printer make and model, and any other relevant information that might help further diagnose the problem.

 

[Chxiz]

It seems like there may be a permissions issue with the printer for domain users. Here are a few troubleshooting steps you can try:

1. Check Printer Permissions:
- Open the printer properties on the print server.
- Navigate to the Security tab.
- Verify that the "Everyone" group has the necessary permissions (e.g. Print, Manage Printers).

2. Check Group Policy Settings:
- Run `gpresult /h report.html` on the client machine to generate a Group Policy report.
- Check if there are any policies applied that might be affecting printer access for domain users.
- Pay particular attention to policies related to printer deployment and security settings.

3. Verify AD User/Group Existence:
- Double-check the usernames or group names when adding them to the printer's security settings.
- Ensure that the users/groups actually exist in Active Directory.
- Check for any typos or special characters that might be causing the error message.

4. Restart the Print Spooler Service:
- Open the Services console on the print server.
- Locate the "Print Spooler" service and restart it.
- This can sometimes resolve issues with printer permissions not taking effect immediately.

5. Test with a Different Printer:
- If possible, try adding a different printer to the print server and see if the issue persists.
- This can help determine if the problem is specific to this particular printer or a more general issue with printer permissions.

6. Update Printer Drivers:
- Make sure you have the latest printer drivers installed on the print server.
- Outdated or incompatible drivers can sometimes cause printing issues.

If none of the above steps resolve the issue, please provide more details about your environment, such as the Windows Server version, printer make and model, and any other relevant information that might help further diagnose the problem.

Iv'e tryed almost everyting, but i dont have another printer to test with. The windows version i use is Windows server 2019. And the printer i use is a HP LaserJet 4250dtn.

 

[kemiy]

It seems like there may be a permissions issue with the printer for domain users. Here are a few troubleshooting steps you can try:

1. Check Printer Permissions:
- Open the printer properties on the print server.
- Navigate to the Security tab.
- Verify that the "Everyone" group has the necessary permissions (e.g. Print, Manage Printers).

2. Check Group Policy Settings:
- Run `gpresult /h report.html` on the client machine to generate a Group Policy report.
- Check if there are any policies applied that might be affecting printer access for domain users.
- Pay particular attention to policies related to printer deployment and security settings.

3. Verify AD User/Group Existence:
- Double-check the usernames or group names when adding them to the printer's security settings.
- Ensure that the users/groups actually exist in Active Directory.
- Check for any typos or special characters that might be causing the error message.

4. Restart the Print Spooler Service:
- Open the Services console on the print server.
- Locate the "Print Spooler" service and restart it shipping label printer.
- This can sometimes resolve issues with printer permissions not taking effect immediately.

5. Test with a Different Printer:
- If possible, try adding a different printer to the print server and see if the issue persists.
- This can help determine if the problem is specific to this particular printer or a more general issue with printer permissions.

6. Update Printer Drivers:
- Make sure you have the latest printer drivers installed on the print server.
- Outdated or incompatible drivers can sometimes cause printing issues.

If none of the above steps resolve the issue, please provide more details about your environment, such as the Windows Server version, printer make and model, and any other relevant information that might help further diagnose the problem.

I have a Win10 computer with two printers configured. One user cannot print to one of the printers. I have set up another user in that computer and it has no problem printing. I have the print queue displayed and when the other user tries to print, say, a Word document, the print job shows up momentarily in the queue and then disappears without the job actually getting to the printer. This user can print reliably to another printer in my network but not the one the user would like to use, the one in the room with the computer. I've spent hours watching HP and MS support people deleting and reinstalling the printer's software and driver without success. This started happening about a month ago right after a Windows update. One MS support person reinstalled Windows over the old (without removing apps or data) and that cured the problem for this user. (Seems to me to be like using a sledge hammer to fix a small problem) However, along came another Windows update and the problem reappeared. AAARRRRGGGHHH!!! Ok, now I feel better but I still need to

fix this problem. The printer manufacturer support folks threw in the towel and punted to MS. The MS engineer suggested that the unfortunate user's profile is somehow corrupted? I'm trying to avoid just creating a new user account because of all the configuring needed, mapping drives, MS Office account, etc. although I do have the user's data backed up a couple of times.



Does anyone have any idea how to r.epair this software issue?

 

[ChatGPT]

Hi kemiy,
Thanks for providing the details about your setup (Windows Server 2019 and the HP LaserJet 4250dtn). Since you've gone through most of the steps and testing another printer isn't currently an option, let’s try a few additional steps to pinpoint and resolve the issue.

Additional Troubleshooting Steps:​

1. Remove and Re-add the Printer to the Server:
   • Sometimes, the printer installation on the server can get corrupted. Remove the printer from the Print Management console, then re-add it.
   • Steps:
     1. Open Print Management (printmanagement.msc) on the server.
     2. Find your HP printer under Printers, right-click it, and select Remove Printer.
     3. Reinstall the printer using updated drivers.
2. Reinstall or Update HP Universal Print Drivers:
   • Incompatible or outdated drivers could be causing this issue. The HP Universal Print Driver (UPD) is a reliable choice for many HP printers.
   • Steps:
     1. Download the latest UPD for PCL6 or PostScript from the HP website.
     2. During installation, select "Dynamic Mode" or "Traditional Mode," depending on your environment.
     3. Assign this driver to the HP LaserJet 4250dtn in the printer properties on the server.
3. Test Printing from Another Domain Admin Account:
   • Try printing from another domain admin and compare the behavior with a standard domain user. If it works for admin but fails for standard users, the issue is likely permission-related.
4. Enable Printer Auditing for Logs:
   • If discrepancies remain, enable Print Auditing to monitor what happens when normal users try printing.
   • Steps:
     1. Go to the Security tab in the printer properties.
     2. Click Advanced, then Auditing.
     3. Add groups like Everyone or specific domain users and allow auditing for "Print" permissions.
     4. Check the Security logs in the Event Viewer for any errors or denied access attempts (Eventvwr.msc → Security Logs → Filter for "Print").
5. Check Print Isolation Mode:
   • Ensure that Printer Driver Isolation is enabled for the HP LaserJet 4250dtn.
   • Steps:
     1. Open Print Management.
     2. Right-click your printer driver in Print Servers > Drivers.
     3. Choose Set Driver Isolation and select Isolated.
6. Verify and Reset User-Specific Print Permissions:
   • Sometimes, permissions at the user or group level can conflict.
   • Steps:
     1. On the server, go to the printer’s Security tab.
     2. For testing, temporarily grant Everyone full permissions (Print, Manage Printers, Manage Documents).
     3. If it works, narrow the permissions to specific groups like Domain Users.
7. Test the Spooler and Print Path:
   • Some older HP printers can face compatibility issues with newer Windows Servers due to changes in the spooler.
   • Disable spooling:
     1. Right-click your printer → Properties → Advanced Tab.
     2. Select Print directly to the printer instead of Spool print documents.
     3. Test if it works for normal users.
8. Driver Isolation Issues with HP Printers:
   • HP printers sometimes have driver dependencies that conflict with Windows. You can try using a Generic/Text Only Driver for testing purposes:
     • Go to Add Printer Wizard → Select Generic/Text Only Driver.
     • Map this "printer" to your HP device and test printing basic text files. If successful, roll back to your preferred drivers with updated settings.

If the Problem Persists:​

• HP Firmware Updates:
  Check if there’s a firmware update available for the HP LaserJet 4250dtn. Older firmware could cause compatibility issues with Windows Server 2019.
• Consider Alternate Testing:
  Borrowing another printer temporarily (even from another office) could help confirm if the issue is isolated to your current model.
• Windows Print Management Queue Reset:
  • Completely clear the spooler queue, and reset the print server configuration using:
    

     net stop spooler del %systemroot%\System32\spool\PRINTERS\* /Q net start spooler

    This clears backed-up spooler jobs which might be choking user printing permissions.

If None of the Above Work:​

You can escalate to HP support or Microsoft support as you’re dealing with a combination of a specific server/printer environment. Let me know if you’d need help with reaching out or if anything else comes up. Good luck!