On the computer to which the printer is connected (in our case it was the Windows 10 laptop), share the printer as usual, and when sharing it, set up the share name that is easy to type in. For example, in our case the long name of the printer was "Epson Stylus Photo R200", but we shared it with the name EpsonR200.
On the computer from which you want to connect to this printer (in our case it was the Windows 2000 computer) use the built-in Add Printer wizard and choose the 'Add Local Printer' option.
Press Next, and on the next page choose the 'Create a new port' option and make sure the 'Local port' option is selected:
When you press Next, Windows will prompt you to enter the port name. Enter the UNC name of the shared printer, in the format: //computername/sharedname . In our case, the computer name of the Windows 10 laptop was laptop, and we had previously set up the shared name of the printer as EpsonR200 (see Step 1 above), so we entered the port name as:
If you don't know the network name of your computer, you can find it out as follows: right-click on the This PC folder (or Computer) in Explorer or some other file manager, and choose Properties from the shortcut menu. On that page, look for the 'computer name' text. That's the name you need to enter instead of 'laptop' in our example. Be sure to use the name of the computer that has the printer attached to it, not the one from which you are trying to connect to the printer through the network!
Next, Windows will probably ask you to select the printer make and model, install its drivers, etc. Keep providing the information that the wizard requires, according to your specific printer. When done, Windows should add the new printer to the computer, and you should be able to use it to print files. The procedure described above worked for us, hopefully it will work for you, too.
3
possible duplicate of Windows 7 printer sharing without homegroups?
– Keltari – 2015-08-16T22:32:55.8101Doesn't seem to behave the same as Windows 7, so no, I don't believe this is a duplicate. – Ryan – 2015-08-16T22:33:50.820
What behaves differently? Does the solution in that question work for you? – MC10 – 2015-08-16T22:37:43.337
1No, it does not. Beyond that, that question is specifically referencing Windows 7. A person looking to solve this issue with Windows 10 would likely pass it over, so I believe this question to Windows 10 is pertinent even if the steps to resolve are only slightly different. – Ryan – 2015-08-16T22:39:48.670
@miR if the answer is the same, we tend to favour either editing the original to expand the question a bit, or simply closing the new one as duplicate to act as a pointer. It does no-one any good to create a new question with every software release, unless it's significantly different. – Bob – 2015-08-16T22:48:43.780
Understood, doesn't hurt to try as Windows is still pretty similar. @Bob That answer did not work for miR. – MC10 – 2015-08-16T22:49:56.537
@MC10 I'm talking about the general case, in response to the "passing it over" argument. Not making any judgements about these two questions specifically. – Bob – 2015-08-16T22:51:48.350
@Bob - I understand and agree with 'every release' but at the same time, this isn't a service pack. Windows 10 is a pretty large release and while similar to Windows 8, it is quite a bit different cosmetically and under the hood. And from 7-10 is akin to 95-XP. Regardless, this is likely a meta discussion. – Ryan – 2015-08-16T22:59:39.970