Sharing a usb printer on a Windows 7 machine with Windows 10. [Solved/Closed]

Posts
984
Registration date
Saturday January 17, 2015
Status
Moderator
Last seen
November 17, 2018
- Jan 19, 2018 at 09:18 AM - Latest reply:
Posts
984
Registration date
Saturday January 17, 2015
Status
Moderator
Last seen
November 17, 2018
- Feb 7, 2018 at 03:23 AM
Hi All,

I only come here when Im in trouble now. Sorry guys.

I have a Windows 7 machine that has a USB printer attached to it. It is a shared printer and other Windows 7 machines can see and print to it quite happily. And then came in the new employee with a brand windows 10 machine. Why I have to suffer with this old machine is another issue, but we have tried to share this (old) printer with the Windows 10 machine. The machine can see the printer when you go to install it, but when you say to it "please do install this nice bit of old kit" and you stroke it oh so tenderly it says that the printer cannot be found - even though it found it in the previous step.

What am I doing wrong please?

I really appreciate thank you messages as a payment for solving issues   :o)
See more 

13 replies

Posts
10873
Registration date
Monday June 3, 2013
Status
Moderator
Last seen
November 20, 2018
Jan 19, 2018 at 04:53 PM
0
Thank you
Wow, its still nice to see you come around every once in a while.

Turn Off the FIREWALL on the Win7 device and see if it it sees it then.

Place the Drivers for the printer on the NEW 10 machine also. What happens if you place the printer on the 10 machine and share from there?
Posts
984
Registration date
Saturday January 17, 2015
Status
Moderator
Last seen
November 17, 2018
- Jan 22, 2018 at 08:04 AM
Hi Ac3mark,

Thanks for the suggestions. Unfortunately it isnt possible to set up the Windows 10 machine as the printers host as the room layout wont permit this. I will try the adding the drivers for the printer as soon as I can get my grubby little hands on it, but I fear that the printer might be too old ... but I will see as soon as I can. As for the firewall, would the other Windows 7 machine be able to print to this printer if the firewall was the culprit?
Posts
984
Registration date
Saturday January 17, 2015
Status
Moderator
Last seen
November 17, 2018
- Jan 22, 2018 at 08:17 AM
Tried the firewall, but still no joy :^(

I find the printer by putting the network addess of the windows 7 pc (\\windows7machine\) and then it finds the printers installed after the last back-slash. I click on the toshiba printer and ask it to install, but then there is the "This device cannot be found ..." (or some such message).
Posts
55841
Registration date
Monday February 1, 2010
Last seen
November 20, 2018
Jan 19, 2018 at 04:56 PM
0
Thank you
Greetings Brian,

What is the printer's make and model?
Posts
984
Registration date
Saturday January 17, 2015
Status
Moderator
Last seen
November 17, 2018
- Jan 22, 2018 at 08:05 AM
Hi Ambucias,

This is a Toshiba B-SA4TM

It prints sticky labels.
Posts
984
Registration date
Saturday January 17, 2015
Status
Moderator
Last seen
November 17, 2018
Jan 22, 2018 at 08:53 AM
0
Thank you
Its possible I have 1/2 resolved this - the network sharing was switched off on the Windows 10 machine, but now it comes up with a different error when finishing the installation - "the printer driver cannot connect to the network print server ..." . I have turned off the firewall and still the same message happens. BUT it says the printer is installed. When we try to print a test page from it everything seems ok, even with the firewall turned back on again, but printing real documents fails.

Any more ideas?
Posts
10873
Registration date
Monday June 3, 2013
Status
Moderator
Last seen
November 20, 2018
- Jan 22, 2018 at 04:43 PM
Are you using 64 bit or 32?
Posts
984
Registration date
Saturday January 17, 2015
Status
Moderator
Last seen
November 17, 2018
- Jan 23, 2018 at 04:26 AM
Both machines are 64 bit.
Posts
55841
Registration date
Monday February 1, 2010
Last seen
November 20, 2018
>
Posts
984
Registration date
Saturday January 17, 2015
Status
Moderator
Last seen
November 17, 2018
- Jan 23, 2018 at 04:49 PM
I also suggest that you go to the hardware manager, see if the printer is there.

Go to system settings/printer scanner, ensure the printer is listed there. It should be the default printer.
Posts
10873
Registration date
Monday June 3, 2013
Status
Moderator
Last seen
November 20, 2018
- Jan 23, 2018 at 03:15 PM
just make certain the driver is 64 bit. You describe an indication of the wrong package.
Posts
55841
Registration date
Monday February 1, 2010
Last seen
November 20, 2018
Jan 22, 2018 at 04:45 PM
0
Thank you
Hi Brian,

Do you have the latest driver installed for the printer?

Check here:

https://www.toshibatec.com/products_overseas/printer2/desktop_barcode_printer/b-sa4tm/
Posts
984
Registration date
Saturday January 17, 2015
Status
Moderator
Last seen
November 17, 2018
- Jan 30, 2018 at 03:31 AM
Hi Guys,

Sorry for not getting back to you all sooner - I have been inundated with silly jobs :^(

The plot thickens with this silly printer ...

I have been able to install the printer and make it work on my personal Windows 10 machine, so I know that the drivers are ok. So it must be a setting on the works windows 10 machine I guess. I tried making the network settings the same on both machines, but still no joy. The funny thing is thought that when I try to print a test page from the works PC (from the Printers and Devices page, right click on the printer (which is showing as installed and on line)) then it does so with no hesitation. Its just when you try to print from any program that the thing just sits there with nothing in the print queue.

I am clearly missing something elementary, but what???

Thanks for your continued support.
Posts
984
Registration date
Saturday January 17, 2015
Status
Moderator
Last seen
November 17, 2018
Feb 7, 2018 at 03:23 AM
0
Thank you
I finally found the problem. One tiny setting was set to enabled. I have no idea why, but disabling it resolved the issue. But I am sure I need to have the print service running on the client PC. Perhaps Windows 10 gets that wrong as well.

Anyway, all solved now. It must be beer time. Cheers guys.