Solved: Photobooth Printer works with OSX but not with Windows

Submitted by capture on #1

Hello everybody

I stumbled across virtualhere while I was looking for a solution to wirelessly print photos from my photobooth.

I have installed the latest USB Server on an Raspberry Pi 3B+ and installed the Windows client on the booth. The printer is recognized by the client software and I can set it to "in-use".

Unfortunately, the photo is not getting printed by the printer. But: I am usually using a MacBook at home and printing from the MacBook works like a charm. 

Do you have any idea why this is the case? Any settings I could change in order to make that print work?

Best regards and thanks

Submitted by Michael on Sun, 2025/02/23 - 09:20

#2

I assume you installed the printer driver in Windows?  What printer is it?

Submitted by capture on Sun, 2025/02/23 - 16:06

#3

Thanks for the response!

Yes, the driver is installed and as soon as I connect the printer directly to the PC, the photos are getting printed.

It is a Mitsubishi CP-D70DW photo printer.

Submitted by Michael on Mon, 2025/02/24 - 08:43

#4

Can i have a quick look e.g via anydesk or rustdesk while you are there? If so email me at mail [at] virtualhere.com (mail[at]virtualhere[dot]com)

Submitted by capture on Wed, 2025/02/26 - 03:14

#5

Hi Michael

Thanks again for the answer. I will reach out to you if I can't fix the issue. At the moment, it seems like everything works fine when connecting the raspberrypi with a ethernet cable.

Will try to use another wifi router to test. I only have products from mikrotik at home and I would like to make sure, that it is not an issue with the wifi itself. 

Submitted by Michael on Wed, 2025/02/26 - 08:10

#6

Oh ok thats interesting so it was a latency issue. If everything works fine on ethernet but not wifi its network latency causing the problem with delayed packets.

Submitted by capture on Wed, 2025/02/26 - 17:47

#7

Great, thanks for your help.

Indeed, I switched to 5GHz WiFi and now it prints fine. Sorry for the inconvenience. 

SOLVED by switching to 5GHz network

It seems like the issue was related to latency. Most probably due other networks on the same channel. By switching to 5GHz, everything works fine now.