MPC3002 printing from vm

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Keegan Chetty
    Trusted Tech

    Site Contributor
    100+ Posts
    • May 2015
    • 113

    #16
    Re: MPC3002 printing from vm

    Originally posted by slimslob
    I was hoping you would come to help explain things. I haven't worked with client/host systems using remote desktop for over 10 years. Does the driver on the client need to be the same as on the server or an added driver to the server such as a X86 driver on a 64 bit server, in order for redirection to occur? And what rights is the copier tech going to need to have in order to check on that?
    so with the user that can print from the server, I have downloaded the same drivers on both the local and virtual machine

    Comment

    • Keegan Chetty
      Trusted Tech

      Site Contributor
      100+ Posts
      • May 2015
      • 113

      #17
      Re: MPC3002 printing from vm

      Originally posted by luca72
      Try to change the phisical Door printer on the switch, and if possibile try using a long new ethernet cable, to make a connection more short possibile, directly to switch, for skip eventualy junction connection, for a temporany test.
      If you want, install in parallel, a new Copy of that printer driver, with a new TCP/ip Port with freshed driver
      Thank you will try this

      Comment

      • Keegan Chetty
        Trusted Tech

        Site Contributor
        100+ Posts
        • May 2015
        • 113

        #18
        Re: MPC3002 printing from vm

        Originally posted by rthonpm
        For redirection there doesn't need to be any kind of driver on the remote system, and printing is entirely platform independent. What the TS (terminal server) ports do is redirect the print job back to the local machine so any redirected printer is just an abstracted instance of a printer so that the remote system can interact with it.

        It's no different than how many features of a local machine are abstracted through: like a server being remoted to magically understands touch input because the local machine has a touch enabled display.

        I generally turn off printer redirection for my RDP sessions as I may not necessarily be on the same network as the remote system, or want the ability to access my local printers from it.

        In this instance, if the remote server is being configured as a print server for the local network, will need to be configured to allow traffic over at least TCP ports 9100 (RAW) and 515 (LPR) from the server to the printers and TCP port 445 (SMB) from the local clients to the server to access the print queues.

        This should be done by someone familiar with the overall network to prevent a misconfigured setting that could expose the customer's network to unauthorised access. Adding the server in some way to the local network, either through a VPN or other means, can also make configuration much easier. This isn't something configured on each workstation, rather it needs to be set at the network level.

        Sent from my BlackBerry using Tapatalk
        thank you, please excuse my ignorance but is it possible to do all this if the client is not using the virtual server as a print server? I'm not sure exactly what they use it for, but they just need to print from it

        Comment

        Working...