Printing Directly to a default windows printer from a web page RRS feed

  • Question

  • User-1379102749 posted

    I have a web application (POS) and i need to print directly to the default windows printer .

    My application ASP.NET , running on IIS (WINDOWS 7 ,  WINDOWS server 2008)

    But it failed, (The default printer not set) , but there is already a thermal printer connected to the windows and working

    I spend days playing in IIS and POOL configurations but till now nothing getting solved

    Please some body help me in this


    Sunday, December 4, 2016 1:10 PM

All replies

  • User-2057865890 posted

    Hi Muhammed,

    To setup server-side printing you need to ensure the process under which ASP.NET is running has sufficient permissions to access Network printers. By default, ASP.NET runs with the permissions of the local machine (ASPNET account for the ASPNET worker process) account. In order to achieve network printing through IIS (Internet Information Services), the Framework should be run under the local SYSTEM account.





    Best Regards,


    Monday, December 5, 2016 9:27 AM
  • User1382931728 posted

    Here in this video you can design your application to print directly to POS printer from your website. 


    Solution will allow you to support printing on all web browser without worry of permissions.

    Sunday, March 11, 2018 10:29 AM
  • User522377968 posted

    Why are your users printing on printers that have been redirected? Why not simply mount the printer using the same community policies at the RDP end? Unless there's a very convincing explanation (and one of those will be a slow link), I still use print servers for 100 percent. All around, it's simply smoother and more seamless. No more central management of print settings is the main drawback.

    Direct printing has a lot of downsides. If you have a print job/client that is continually crashing the printer, the largest one is imo. Check here about 3d printer for cosplay at printer how. In printers with Fierys and the like, this is more of a concern, but it makes it almost difficult to really lock the culprit down. Where everyone is in the same queue on a print server. You also have to wrestle with things like different drivers, and different names. Seems like simple things to keep under control, but when you're talking 100+ machines/users, someone will have a printer named something different and then it becomes a communication nightmare.

    Saturday, January 2, 2021 3:18 AM
  • User1932145893 posted

    Like the guy who isn't said, by installing all network printers on a server and then sharing them, you can centralise your printing. It is then possible to use GPOs to connect relevant printers at topvinylcutters to various OUs/users. When it comes to clearing print queues and, in your case, making adjustments to print settings, this also makes admin much simpler.

    Saturday, January 9, 2021 2:11 PM