Windows 10: Windows clients using NTLM when connecting to print server

I've noticed spoolsv.exe is using NTLM authentication when connecting to network printers, even though when I use klist on my workstation it shows I have kerberos tickets for:cifs/192.168.1.1 ip address of print servercifs/serverNamecifs/serverName.domain.local cifs/serverCname.domain.localhost/serverName.domain.local host/serverNameAll of these kerberos tickets reference the print server, am I missing some other server nomenclature that deals specifically with printing?

:)

 

Not able to connect to print server

Hi, I am not able to connect to printers from Windows 2016 print server when a client is running Windows 2003 32 bits. I get an access denied message. Even when the user is domain admin. I get the same error message when trying to use print management
to remotely manage the server. I know that Windows 2016 has improved security but I need to know what causes the issue. Is it by design or is there a something that can be changed on the OS level to allow connection from clients running Windows 2003 32 bits.
Thank you.

 

Windows 10 Native NFS client - does any print support exist to any supported NFS servers?

Hi all,

I was wondering if the Windows Native NFS client supports connecting to print shares....(assuming print sharing is supported by any NFS Servers out there, such as the Windows Server 2012 or 2016 NFS server).

I have used the Linux SAMBA client to print to SMB Servers, so wondering if this same capability exists in the Windows Native NFS client.

Thank you for any information!

~Charlie

 

Windows 10 client doesn't load the print driver from the XP print server

Hi,

To assist you better, I would like to ask some questions:

Which Printer drivers are installed in #2 computer? Windows 10 or Windows XP?

Are you facing any issues with Printer after installing Windows XP drivers in #3 Computer?

I suggest you to Stop and Start the Print Spooler services by following the steps provided below:

• Press Windows key + R key, type services.msc
  and press Enter.
• From the list, locate Print Spooler service.
• Double click on the service and select Stop and click on
  Apply and OK.
• Restart the computer, repeat step 1&2.
• Double click on the service and check if the service is started.
  

Hope this helps. Keep us posted on the status and we'll be glad to assist you.