Skip to main content

How to solve Canon Multi-Functional Printer unable to print with PIN Management via Print Server?

By
Last fews ago, I've got one task that to setup one Printer Server for another VMware View Project.

So, I've setup Print Management Server on Windows Server 2008 Standard Edition R2 Service Pack 1.

After Server Setup and Printers Setup done on Server, I tried test print on Workstation and the result is no issue when print out documents directly.

But when I choose with Department PIN to print out documents for billing and secure purpose, it's not working.

I've tried several methods what I knew based on my knowledge and Google Results, but still not resolve the issue till some time.

After digging many resources on Google few days and found out one method to resolve the issue and it's resolved my issue.

So, I'd like to share my experience to others who might facing this issue to resolve with east and less time consuming.

The steps are as below,

1) Download Latest Driver for Your Canon Multi-Functional Printer/Copier on Your Server. But your drive should be some sort of UFRII.
2) After downloaded, you should see "misc" folder inside it and install "DIASsetup.exe" on server.
3) Once installation is done, you can try to print documents with PIN or query device information on Workstation and you will see it's working.

Main reason is we need to install Network Assistant Application of Printer/Copier to working well.

May you all be happy.
(Be knowledgeable, pass it on then)

Labels:

Comments

  1. Laura BushJanuary 19, 2021 at 6:34 AM

    It is truly a well-researched content and excellent wording. I got so engaged in this material that I couldn’t wait to read. I am impressed with your work and skill. Thanks. free standing display units

    ReplyDelete
  2. studioprintingFebruary 2, 2021 at 11:00 AM

    I read this article, it is really informative one. Your way of writing and making things clear is very impressive. Thanking you for such an informative article. digital printing uk

    ReplyDelete
  3. The Ink SuppliesJune 21, 2021 at 12:56 PM

    Printers are one of the most important devices for home offices, thank you for sharing this colour printer. Your article isn’t only useful but it is additionally really informative. As a seller of premium remanufactured toner cartridges and Printer ink in Delaware, I am glad to come across this, great blog.

    ReplyDelete
  4. Hijabi GirlJuly 31, 2021 at 2:31 AM

    Wow, cool post. I'd like to write like this too - taking time and real hard work to make a great article... but I put things off too much and never seem to get started. Thanks though. Epson ink cartridges

    ReplyDelete
  5. Hijabi GirlJanuary 18, 2022 at 9:41 AM

    Pretty good post. I just stumbled upon your blog and wanted to say that I have really enjoyed reading your blog posts. Any way I'll be subscribing to your feed and I hope you post again soon. Big thanks for the useful info. Compatible hp 12a black toner

    ReplyDelete

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

By
I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...
Post a Comment
Read more

Why do we need network virtualization?

By
We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...
144 comments
Read more

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

By
Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Soc...
7 comments
Read more