1

I have a Windows Server 2016 x64 Application server. I have tested all kinds of printer and it's working fine. But when clients are trying to print from remote session, who have installed Standard TCP/IP port printers, they get error while printing from remote desktop. I have checked printer driver and that's fine. what could be the creating issue? is it in my end or in my client's end?

I have tested on:

  • Brother 5450DN(TCP/IP) printer
  • Adobe PDF
  • All other shared printers
  • all other network shared printers

The client have

  • Brother MFC 8890DW (TCP/PC) printer shared from other computer.

Hope for kindly co-operation.

Mars
  • 71
  • 1
  • 8
  • What's the error message? – Esa Jokinen Sep 03 '17 at 05:41
  • @EsaJokinen "Could not start printer. Please check your printer configuration." from -Libre Document, and "The document could not be printed" from -Adobe acrobat reader. But clients can direct print from local pc. – Mars Sep 04 '17 at 03:36
  • The problem is based in real case scenario. Rather than just down voting, it would help if you asked what confused you had in my question. or you can try suggesting answer to the question in the way you understood my issue. – Mars Sep 05 '17 at 09:44
  • Can the server print on the client ip's? Not sure how that works , but is the traffic routed through the client? – TomTom Sep 05 '17 at 09:45
  • @TomTom I am not sure yet. but, client can print pdf on their own computer from there. – Mars Sep 05 '17 at 09:54
  • 1
    That would be an obvious issue, though - direct ip, and the server can not reach the printer. I would check this. – TomTom Sep 05 '17 at 10:30
  • @TomTom i am not sure but TSPrint (https://www.terminalworks.com/remote-desktop-printing) work for me. – Mars Sep 05 '17 at 17:11

1 Answers1

2

I have worked a lot with printing issues and RDP earlier. It might be you are fooled by the fact its using TCP ports on the printers.

Make sure the print spooler service in running when you are trying to print, and make sure its running after you've tried. Many drivers are a huge piece of crap and should never be allowed to run in terminal server environments. Typically problem is they create some dialog in session 0 on the server and this is not allowed (any more) in terminal server environments and this cause the driver to crash, which might result in the print spooler service to crash and then you get errors like about.

Mr Zach
  • 247
  • 1
  • 6
  • I have to check print spooler at my end or in my client's end? can you please provide me reference URLs? – Mars Sep 05 '17 at 17:20
  • The print spooler is a windows NT service running on both clients and servers. I would start looking at the server side. – Mr Zach Sep 05 '17 at 17:46