Applies to: Windows computers only. See our Mac guide if you're on a Drury-managed Mac Computer.

Drury's printers are shared through a central print server, so you don't need to install drivers manually — Windows downloads and configures everything automatically when you connect.

Step 1: Find your printer's name

Before you begin, you'll need the exact name of the printer you want to connect to (for example, Alumni_Canon_C256F or Admissions_DataTeamHP). Printer names usually reference the department and the printer model or location.

Not sure of the name? Check the label on the printer itself, ask a coworker who already prints to it, or contact the Help Desk and we'll confirm it for you.

Step 2: Open the print server

Open File Explorer and type the following into the address bar, then press Enter:

\\duprinters

Alternatively, look for the duprinters shortcut on your desktop and double-click it:

Step 3: Connect to the printer

A window will open showing all available printers, similar to this:

Find the printer name from Step 1, right-click it, and select Connect...

Windows will briefly show a progress window while it installs the printer driver. This usually takes less than a minute.

Step 4: Confirm it worked

Open Settings > Bluetooth & devices > Printers & scanners and check that the printer now appears in your list. You can right-click it and choose Print a test page to confirm it's working.

Troubleshooting

"Windows cannot access \\duprinters" or the folder won't open
Make sure you're connected to the Drury network (on-campus Wi-Fi or wired connection). This path isn't reachable from off-campus without VPN.

"Windows can't connect to the printer" error after clicking Connect
This is usually a driver issue on the print server rather than your computer. Contact the Help Desk with the exact printer name and the error message shown.

Printer connects but test page doesn't print
Check that the physical printer is powered on and has paper. If it looks fine on the printer's end, contact the Help Desk — this may be a queue issue on the server.

Still stuck? Submit a ticket or contact the Technology Services Help Desk and we'll get you connected.