Shared Printer Error 0x0000011b — Connect Using Credentials and a Local Port

by

When connecting to a printer shared from another Windows PC, the installation may fail with error 0x0000011b.

In this case, I first tried several commonly suggested RPC and Windows printer-sharing related settings, but the shared printer still would not connect in this environment.

Instead of continuing to modify registry values or lower Windows security settings, I eventually stored the credentials for the PC hosting the printer, created a Local Port using the shared printer path, and manually installed the printer driver on the client PC.

I confirmed this method working in the following environments:

  • Windows XP → printer shared from Windows 10
  • Windows 7 → printer shared from Windows 11

Error 0x00000709 also appeared during some troubleshooting steps.

Results may vary depending on the Windows version, update level, security policies, SMB configuration, printer model, and driver.

Before You Start

Menu names and locations may differ depending on the Windows version and installed updates.

Windows XP, Windows 7, Windows 10, and Windows 11 use different printer and network configuration screens.

Even within Windows 10 or Windows 11, wording and menu locations may change after updates.

Possible differences include:

  • Devices and Printers versus Printers & scanners
  • Different wording for The printer that I want isn't listed
  • Different steps for reaching Local Port configuration
  • Different credential-management menus
  • Different driver installation screens depending on the printer manufacturer

If the exact wording shown here is not available, look for the equivalent function.

This article is based on systems I actually worked on and does not guarantee the same result with every Windows and printer combination.

Symptoms

The printer was connected by USB or a similar connection to another Windows PC, and printer sharing was already enabled.

However, adding the shared printer through the normal Windows method failed.

The symptoms included:

  • The host PC was visible on the network
  • The shared printer could be seen
  • Connecting to the printer produced an error
  • Error 0x0000011b
  • Error 0x00000709 during some troubleshooting steps
  • Shared folders and the shared printer did not always behave the same way

Initial Suspicion

I initially suspected compatibility or security-policy differences between Windows versions.

This was especially relevant when older systems such as Windows XP or Windows 7 were connecting to printers shared from Windows 10 or Windows 11.

Several components may be involved:

  • SMB
  • Windows authentication
  • TCP port 445
  • Print Spooler
  • RPC
  • Point and Print
  • Printer drivers
  • Windows security policies

Error 0x0000011b can occur in environments affected by changes to Windows printer sharing and RPC authentication security.

What I Tried First

I first reviewed and applied several commonly suggested RPC and Windows printer-sharing settings related to 0x0000011b.

In this environment, however, those changes did not restore the shared printer connection.

Rather than continuing to change the same security-related settings, I changed the connection method itself.

The successful sequence was:

Store host credentials → Confirm access to the host PC → Create a Local Port → Set the shared printer path → Manually install the driver

This does not mean that RPC-related fixes are ineffective in every environment.

It only means that they did not resolve this particular case, while the Local Port method resulted in successful printing.

Solution

The final procedure was:

  1. Confirm printer sharing on the host PC
  2. Check the host PC name or IP address
  3. Store the host PC credentials on the client PC
  4. Test \\HostPCName or \\HostPC-IP
  5. Create a Local Port
  6. Set \\HostPCName-or-IP\PrinterShareName
  7. Manually install the printer driver
  8. Print a test page

1. Confirm Printer Sharing on the Host PC

The PC directly connected to the printer is referred to here as the host PC, while the PC using it over the network is the client PC.

On the host PC, a typical path is:

Control Panel → Devices and Printers → Right-click printer → Printer properties → Sharing

Confirm:

  • Share this printer is enabled
  • The printer share name

Example:

HP9010

2. Check the Host PC Name or IP Address

A Windows computer name may look like:

DESKTOP-AB12CD3

On Windows 10 and Windows 11, it can usually be found under:

Settings → System → About → Device name

If the host name is:

DESKTOP-AB12CD3

and the printer share name is:

HP9010

the path becomes:

\\DESKTOP-AB12CD3\HP9010

The host PC’s IP address can also be used.

Example:

\\192.168.0.20\HP9010

When Using an IP Address

If the host PC receives its address through DHCP, its IP may change later.

If the Local Port is tied to an old IP, printing may stop working.

For a more stable configuration, consider:

  • Assigning a static IP to the host PC
  • Creating a DHCP reservation on the router

3. Store Host PC Credentials

Windows 7 / 10 / 11

A typical path is:

Control Panel → Credential Manager → Windows Credentials → Add a Windows credential

Enter the host PC’s computer name or IP address.

Example:

DESKTOP-AB12CD3

or:

192.168.0.20

Enter a user account that can access the host PC.

Example:

DESKTOP-AB12CD3\printeruser

Then enter that account’s password.

These must be credentials that can access the host PC, not simply the client PC’s account information.

Windows XP

Windows XP does not use Credential Manager in the same way as newer Windows versions.

In this case, I configured the network login information through Control Panel.

A typical path is:

Control Panel → User Accounts → Select the current user → Manage my network passwords

This opens the area for managing Stored User Names and Passwords.

Add the host PC’s computer name or IP address, along with an account and password that can access it.

Menu names may vary depending on the Windows XP edition and account configuration.

In the system I worked on, the Run-command method did not work, so I located the appropriate setting directly through Control Panel.

4. Confirm Access to the Host PC

Before adding the printer, test:

\\DESKTOP-AB12CD3

or:

\\192.168.0.20

in File Explorer or the Run dialog.

If shared resources are visible, that helps confirm network connectivity and authentication.

If access fails, check:

  • Host PC power
  • Network connectivity
  • File and printer sharing
  • Firewall rules
  • User name and password
  • SMB connectivity

5. Check TCP Port 445

Modern Windows SMB commonly uses TCP port 445.

On Windows 10 or Windows 11:

Test-NetConnection DESKTOP-AB12CD3 -Port 445

or:

Test-NetConnection 192.168.0.20 -Port 445

If you see:

TcpTestSucceeded : True

TCP port 445 is reachable.

If it is False, troubleshoot the network or firewall first.

However, an open TCP 445 port does not guarantee that printer sharing itself will work, because printer sharing may also involve authentication, Print Spooler, RPC, drivers, and security policies.

6. Add the Printer Using a Local Port

On the client PC:

Control Panel → Devices and Printers → Add a printer

Instead of selecting the automatically detected shared printer, choose:

The printer that I want isn’t listed

or the equivalent manual-add option.

Then use:

Add a local printer or network printer with manual settings

Select:

Create a new port → Local Port

For the port name, enter:

\\DESKTOP-AB12CD3\HP9010

or:

\\192.168.0.20\HP9010

7. Manually Install the Printer Driver

Install the driver directly on the client PC.

If Windows includes the printer model, select it from the list.

Otherwise use the manufacturer’s driver and, where applicable, Have Disk to select the appropriate INF file.

In general:

  • 32-bit Windows → 32-bit driver
  • 64-bit Windows → 64-bit driver

Older systems such as Windows XP may not have official drivers for newer printer models.

8. Print a Test Page

After installation:

Printer properties → Print Test Page

If the physical page prints, the shared-printer connection is working.

This was confirmed in the systems described in this article.

Why Store Credentials First?

Windows file sharing and printer sharing both involve accessing resources on another Windows PC.

Modern SMB communication generally uses TCP port 445.

Conceptually:

Client PC
   ↓
Connect to host PC
   ↓
Authenticate using stored credentials
   ↓
SMB session
   ↓
Access shared resources

In this case, successful printing was confirmed after storing the host credentials and configuring the Local Port.

This suggests that successful host authentication may have contributed to the result.

However, printer sharing does not depend on SMB alone.

Print Spooler, RPC, Point and Print, drivers, and Windows printer security policies may also be involved.

Therefore, stored credentials alone cannot be confirmed as the sole cause.

Why Can a Local Port Help With 0x0000011b?

A normal shared-printer installation may involve retrieving printer information or drivers from the host.

This can involve Point and Print, Print Spooler, RPC authentication, and driver-installation permissions.

In this environment, several RPC-related settings were checked first, but the printer still would not connect.

With the Local Port method, the driver is installed directly on the client and the port points to:

\\HostPCName-or-IP\PrinterShareName

Conceptually:

Client PC
   ↓
Driver installed locally
   ↓
Local Port
   ↓
\\HostPC\SharedPrinter
   ↓
Print through host PC

This can bypass some problems in the normal Point and Print and driver-installation path.

Therefore, this method should be considered:

a way to bypass the normal shared-printer connection path where 0x0000011b occurs

rather than:

a direct fix for the root cause of 0x0000011b.

Important — Prefer Direct Network Printing When Possible

A Windows-hosted printer looks like this:

PC 1 ─┐
PC 2 ─┼── Windows host PC ── USB printer
PC 3 ─┘

The host PC must remain available.

Power loss, Windows errors, account changes, firewall changes, sharing changes, or security-policy changes can affect every client PC.

Windows has also continued to tighten security around older or weaker sharing methods such as SMB1, guest authentication, and unauthenticated access.

Long-term maintenance may therefore be difficult in environments such as:

  • Windows XP communicating with newer Windows
  • SMB1-dependent configurations
  • Passwordless sharing
  • Guest-authenticated sharing
  • Old Windows versions acting as printer hosts
  • Setups requiring one Windows PC to stay powered on

If the Printer Supports Ethernet or Wi-Fi

If the printer itself supports network connectivity, direct network printing is generally preferable.

For example:

Add printer → Add a printer using a TCP/IP address or hostname → Standard TCP/IP Port

The structure becomes:

PC 1 ─┐
PC 2 ─┼── Network ── Printer
PC 3 ─┘

This avoids dependence on a specific Windows host PC.

The credentials + Local Port method can be useful for keeping an older USB-only printer in service, but if the printer itself supports Ethernet or Wi-Fi, direct network printing should generally be considered first.

Result

Several RPC and printer-sharing related settings commonly associated with 0x0000011b were checked first, but they did not restore the connection in this environment.

The final successful method was:

Store host credentials → Confirm host access → Create Local Port → Set shared printer path → Manually install client driver

The method was confirmed in:

  • Windows XP → Windows 10
  • Windows 7 → Windows 11

Actual printing was successful in both cases.

Field Notes

Symptom: 0x0000011b; 0x00000709 also appeared during troubleshooting

Initial suspicion: Windows version differences, authentication, SMB, RPC, and printer security policies

Tried first: Several RPC and printer-sharing related settings, without success in this environment

Final method: Store host credentials → Confirm host access → Create Local Port → Set shared-printer path → Manually install driver

Tested environments: Windows XP → Windows 10 / Windows 7 → Windows 11

Result: Physical printing confirmed

Possible cause: Successful host authentication and bypassing the normal Point and Print connection path may have contributed

Note: Menu names and steps may differ by Windows version, update level, printer manufacturer, and driver

Recommended configuration: If Ethernet or Wi-Fi is available on the printer, direct network printing should generally be considered first

Not fully confirmed: Because multiple sharing and security settings were tested during troubleshooting, no single setting can be confirmed as the sole cause of the successful connection