Ir al contenido

Troubleshooting and Error Resolution in Hybrid Printing

Incident diagnostic matrix and rescue commands for the deployment of the Proxmox/Server Core hybrid print server.

0views

This technical guide consolidates the incidents detected during the design and deployment phases of the Hybrid Print Server (Proxmox / Windows Server / Universal Print), accompanied by their respective diagnostic workflows and immediate operational resolutions.


Error SymptomTechnical Root CauseImmediate Resolution Action
The Windows installer does not detect the virtual diskThe VirtIO paravirtualized driver is missing in the native installation wizard.Load the ISO virtio-win.iso into the second virtual drive and select the path viostor\2k22\amd64.
The disk appears in the list but reports an “Offline” errorRestrictive SAN policy in Windows Server Core.Open console (<kbd>Shift + F10</kbd>) ➔ Start diskpart ➔ Select disk and run: attributes disk clear readonly ➔ online disk.
The sconfig tool does not detect network cardsThe VirtIO paravirtualized network adapter has no driver.Run in PowerShell:pnputil /add-driver "D:\NetKVM\2k22\amd64\netkvm.inf" /install.

2. Connectivity and Remote Administration Errors (WinRM & RPC)

Sección titulada «2. Errores de Conectividad y Administración Remota (WinRM & RPC)»
Error / Error SymptomTechnical DiagnosisImmediate Resolution Action
“Access Denied” when connecting remotelyThe Windows network local UAC filter blocks elevated tokens in a Workgroup.Create registry key on the server: LocalAccountTokenFilterPolicy = 1 in the path HKLM:\...\Policies\System.
The Print Console freezes when connectingLocal Firewall policies block RPC/DCOM dynamic port ranges.Enable the interface network profile as Private on the print server using Set-NetConnectionProfile.
Failed resolution of TrustedHostsThe client PC does not trust the remote server identity without Kerberos.Run on the client PC: winrm set winrm/config/client '@{TrustedHosts="w-server-2022,192.168.10.22"}'.
CredSSP negotiation error (0x80090350)Lack of mutual credential delegation between the Azure AD client and the Workgroup server.Enable and initialize the CredSSP protocol on both ends by running: Enable-WSManCredSSP (with role Server and Client respectively).
“Incorrect credentials” when launching the MMC consoleWindows attempts to automatically use the unified Microsoft Entra ID corporate credentials.Launch the console by forcing the local server administrator's network credentials: runas /netonly /user:w-server-2022\usuario.demo "mmc printmanagement.msc".

Error SymptomTechnical Root CauseImmediate Resolution Action
Access denied error when loading the driver from the clientPoint and Print restrictions are active in the server policies.Relax Point and Print security restrictions by editing the server registry in the key Printers\PointAndPrint (Set Restricted to 0).
The '+ Add' button is missing from the Universal Print portalMicrosoft 365 license without an active monthly print volume.Purchase additional volume licenses or wait for the monthly quota reset.
The Connector installer hangs or fails in Server CoreDesign Limitation: Universal Print Connector lacks an unattended CLI and requires a GUI for the interactive Microsoft Entra ID web login.Absolute Incompatibility. The server hosting the Universal Print Connector must be deployed on a Windows Server with Desktop Experience (graphical interface / GUI).
Connector installer fails (MSI) when starting in GUIThe native print queue services role is missing from the operating system.Enable the print role before running the installation with:Install-WindowsFeature Print-Services.

Execute from PowerShell / CMD depending on the test endpoint:

Immediately displays security audit logs to detect network blocks or incorrect passwords:

Ventana de terminal
Get-WinEvent -LogName Security -FilterXPath "*[System[EventID=4625]]" -MaxEvents 5 | Format-List

Validates basic network connectivity of the TCP remote administration listening port:

Ventana de terminal
Test-NetConnection -ComputerName 192.168.10.10 -Port 5985

Allows low-level auditing of whether remote administration TCP packets are reaching the virtual machine's physical interface:

Ventana de terminal
tcpdump -i vmbr0 host 192.168.10.10 and port 5985