I installed CUPS from dietpi-software and installed my printer driver. I can print from my phone on android but when I try from windows PC the printer is show but just hangs on “connecting” . Any help appreciated please.
Required Information
DietPi version | G_DIETPI_VERSION_CORE=8 G_DIETPI_VERSION_SUB=16 G_DIETPI_VERSION_RC=2 G_GITBRANCH='master' G_GITOWNER='MichaIng' G_LIVE_PATCH_STATUS[0]='not applicable'
Was the software title installed freshly or updated/migrated? Fresh Install
Can this issue be replicated on a fresh installation of DietPi?
← If you sent a “dietpi-bugreport”, please paste the ID here →
Bug report ID | echo $G_HW_UUID
Hi Filled in as much as I can. Printer is Ricoh SP213 w and everything works OK via Android but windows (on 2 systems) hangs for ages “connecting” then says something like too many connectionsn
Hi Filled in as much as I can. (See original post) Printer is Ricoh SP213 w and everything works OK via Android but windows (on 2 systems) hangs for ages “connecting” then says something like too many connectionsn
Im having no sucess with this at all. I have uninstalled /reinstalled Cups., reflashed the SD card witha new copy of Dietpi and installed again from scratch. What am I missing ? Shouldnt it just work? Windows just cant see the printerand now I tried setting the Cups config to “defaults” and that has locked me out of the GUI all together. I just dont know where to go from here. I tried journalctl - u cups but that didnt show anything. Im not experienced with linux so thought Dietpi would be a good way to go but Im baffled.
for me this sounds more an issue wich your client and not something with CUPS. I did a test on one of my demo system and was able to create a fake printer, which was automatically detected by my W11 system. As well test prints succeeded.
Hi Thanks for your reply. If this is a client issue it is affecting TWO Windows 11 PC’s I’ve tried. One is a brand new unit with a clean new install of Win11. Both detect the printer but neither will connect to it. Like you I created a fake printer and the same issue .
Anything more I can try ?