How to Force a TCP IP Port Reuse on a Renamed Printer in Windows 11

Quick fix: When you rename a network printer, Windows creates a new TCP/IP port but keeps the old one referenced by other queues. Open Print Management (printmanagement.msc), expand Print Servers → Local Server → Ports, delete the orphaned port, then re-bind the renamed printer to the existing port via Properties → Ports tab.

You renamed a network printer in Settings (or someone did via Active Directory). The printer still works, but now you have two TCP/IP ports in Print Management pointing to the same IP — one for the old name, one for the new. Print queues from before the rename still use the old port. New queues use the new port. Eventually the port list grows clutterful, and a removal mistake breaks half the print queues.

Why ports duplicate on rename

Windows binds print queues to a port by name, not by IP. When you rename the printer, the port name stored with the queue becomes orphaned (it still exists, still points to the right IP, but the queue thinks it’s offline). Windows auto-creates a new port matching the new name. Now you have two ports for the same printer, neither cleanly removable without breaking something.

Method 1: Re-bind queues to a single port via Print Management

1. Press Win + R, type printmanagement.msc, press Enter.
2. Expand Print Servers → (your PC) → Ports. Note the duplicate TCP/IP ports for the same IP.
3. Expand Printers. For each queue using the old port name, right-click and choose Properties → Ports tab.
4. Select the desired single port (the one you’ll keep) and click Apply.
5. Repeat for all queues until no queue references the orphaned port.
6. Return to Ports. Right-click the now-orphaned port and choose Delete.

This cleans up the duplicates. The remaining single port serves all queues.

Method 2: Script the cleanup via PowerShell

1. List ports: Get-PrinterPort | Where-Object {$_.PrinterHostAddress -eq “192.168.1.50”}.
2. Note the names of duplicate ports.
3. Repoint printers to the canonical port:
   
   Set-Printer -Name “OldPrinterQueue” -PortName “CanonicalPort”
4. Delete the orphan:
   
   Remove-PrinterPort -Name “OrphanedPort”

PowerShell scales the fix across many queues. Wrap into a script that runs on logon to keep clutter from accumulating.

Method 3: Use hostname instead of name-based ports

For long-term resilience, configure printers by hostname rather than name.

1. Set a static DNS record for the printer (or static IP).
2. In Print Management, create a new TCP/IP port using the hostname (e.g., printer-floor3.local).
3. Re-bind queues to the hostname-based port.
4. Future renames at the printer level don’t affect Windows’ port mapping because the hostname stays stable.

This is the right setup for enterprise environments where printers get renamed for organizational reasons but their network identity stays put.

How to verify the fix worked

• Print Management → Ports shows one port per physical printer IP, not two.
• All print queues function correctly.
• Run Get-PrinterPort — no duplicates for the same IP.

If none of these work

If a port refuses to delete with “Port is in use,” a queue still references it — check all queues including hidden ones via PowerShell. For ports stuck because a Windows service has them locked, restart the Print Spooler. For chronic naming drift on managed environments, use Group Policy Preferences to deploy printer connections by canonical name across the fleet.

Bottom line: Re-bind queues to one port, delete orphans, and consider hostname-based ports for stability against future renames.