Windows 10: One laptop in domain can't print

We have 2 HP network printers connected via ethernet with a fixed IP. These work with all users in the network (15 clients). Except by 1 user. Everything is fine with the print spooler service. In Device manager 1 of the 2 printers is not recognized. With this printer, driver error is shown in the control panel, although this have been installed several times. However, the other print does not either. After a print job, Windows does not give an error message either. I suspect that it is a general printing problem and has nothing to do with HP because both printers are of different HP type.

It is also not in the user profile. Printing is also not possible under admin account.





OS is Windows 10 Pro, the printers are HP PageWidePro 477dw and HP Officejet Pro 8620.



What I have already tried:



* Uninstall and reinstall printers (several times)

* Install the latest software from the HP site

* Have the driver updated via the internet via device manager

* use the Microsoft repair tool. => gives no errors

* Restart Printspooler (service)

* ping test to printers => OK

* check whether these KBs are included in the updates: https: //www.windowscentra...-latest-update-windows-10 => They are not included

* run HP printer diagnostic program on the PC in question => gives no errors


Do anyone recognize this problem or knows a solution?

:)

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW

 

Getting a domain name...

Just simple 3 steps to make your website glow to millions…
Step 1: Sign up now and get a FREE domain!
Step 2: Design your new website in minutes!
Step 3: You are live! Share your life online!

Click here…

 

Print Banner

Hi Terri,

Please help us with the below information to help you better.

• What is the make and model of your printer?
• Is the computer is connected to any domain network?
• Is the printer is connected locally with the system or shared printer through network?

I suggest you to try the below steps and check if it helps.

• Open Devices and Printers.
• Right-click the printer you want to manage, and then click Printer properties. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
• Disable banner sheet - in Printing Defaults (Advanced tab in printer properties).
• Also uncheck "Enable advanced printing features".

Please get back to us with the above information to help you further.