Shared Printer installation issue - 0x000003e3 error?

Hi all,

I have a friend with a small business at their home that does boat repairs. I'm trying to get a receipt printer set up on one Win10 desktop PC that is shared from another Win10 computer in his shop...it used to work fine, but when I try to connect to the share, I get a 'Cannot connect to printer' (I can't remember the exact phrasing) with error 0x000003e3. I can see and access the shared printer on the PC I want to set it up on, and it will prompt to install drivers from the other PC, but it fails with that error in the middle of driver installation. Not even sure why it prompts for drivers because the correct drivers are already installed on that PC where the receipt printer USED to work fine before anyway!

Anybody know what could be going on or how I could fix this? I've tried everything I can think of off the top of my head...

I've double and triple-checked everything I know to check; the share is set up correctly, the permissions are set up correctly, both accounts on both PCs are admin accounts (not that that necessarily matters), they're on the same network, 'File and Printer Sharing' is turned on on both PCs...I KNOW one PC is running Win10 version 2004 and the other I THINK is running that same version.

Thing is, he has a lot of printers (laser, vinyl, a cash drawer shared from one PC to another for his business software that gets set up as a printer, a label printer).....is there any way I may be able to get this working without having to re-setup all his other printers as well? (The cash drawer is a PITA as it has to be manually set up as a 'printer').

Thanks for any help! :)

jimbo45 said:

Hi there
@Darkstrike

Try this -- go to post nr #6 in this thread

Print sharing



Cheers
jimbo

Hi - I had actually found and tried that method (though without enabling SMB1) and it didn't work. Does SMB1 HAVE to be enabled for that method to work?

Hi all - late reply, but just as a note, I solved this....I ended up having to share the Windows 'spooler' directory, weirdly....but hey, working now!