Windows Server 2008 32bit, VPN slow printing

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Hansoon
    Field Supervisor

    Site Contributor
    2,500+ Posts
    • Sep 2007
    • 3347

    #1

    Windows Server 2008 32bit, VPN slow printing

    Windows Server 2008 32bit, VPN-tunnel slow printing with MFP Bizhub350

    Notebook to Bizhub350 prints fine directly connected with crossover cable,
    Workstation through Server and VPN-Tunnel to 3rd party printer prints fine.
    However, Workstation through Server and VPN-Tunnel to Bizhub350 in the same location prints extremely slow.

    Any idea's where to look?

    Hans
    “ Sent from my Intel 80286 using MS-DOS 2.0
    https://www.copytechnet.com/images/smilies/biggrin.png
  • MFPTech
    Trusted Tech

    250+ Posts
    • Nov 2010
    • 486

    #2
    Re: Windows Server 2008 32bit, VPN slow printing

    Have you tried different drivers, different ports, packet capture?

    Comment

    • TheOwl
      Service Manager

      Site Contributor
      1,000+ Posts
      • Nov 2008
      • 1732

      #3
      Re: Windows Server 2008 32bit, VPN slow printing

      What about printing to the copier directly over the VPN?

      Konica Minolta drivers have alot involved with them and have a tendancy to inflate print jobs a little bit. Also, the Bizhub 350's weren't a great machine network wise any way as they are actually NEC's.

      One other thing to try is using an HP LaserJet driver to print to the copier such as a LaserJet 4 or 5Si which are both PCL which the machine will understand anyway. This will tell you for sure if it is a driver issue or something going on with the VPN tunnel.
      Please don't ask me for firmware or service manuals as refusal often offends.

      Comment

      • MaineCopyTech
        Technician
        • Aug 2011
        • 11

        #4
        Re: Windows Server 2008 32bit, VPN slow printing

        Maybe having both spooling and ripping at the same time don't work as good over VPN. Try changing the spool setting under the advanced tab of the printer properties to "Start Printing After Last Page is Spooled". Most default to "Start Printing Immediately". Or even try "Print directly to printer" and remove the spooling operation altogether.


        Did yo try toggling form LPR to port 9100 or vice versa?

        Another thing to try is installing the optional component "Print Services for Unix" LPR port.

        Comment

        • TheOwl
          Service Manager

          Site Contributor
          1,000+ Posts
          • Nov 2008
          • 1732

          #5
          Re: Windows Server 2008 32bit, VPN slow printing

          I just had another thought on this:

          Make sure that the TCP/IP port settings are to disable SNMP communication.

          This also means turning any SNMP communication off in the driver as well.
          Please don't ask me for firmware or service manuals as refusal often offends.

          Comment

          • Captain Scott
            Trusted Tech

            100+ Posts
            • Dec 2008
            • 166

            #6
            Re: Windows Server 2008 32bit, VPN slow printing

            Originally posted by TheOwl
            I just had another thought on this:

            Make sure that the TCP/IP port settings are to disable SNMP communication.

            This also means turning any SNMP communication off in the driver as well.
            Hi Owl man,

            Interested to know if you have run into many issues relating to this setting with Server 2008 and Win7? I am finding it is starting to pop up often when MFP\printer hits an issue eg out of paper. Need to restart spooler to recover. Sorry don't mean to hijack this thread.

            Comment

            • TheOwl
              Service Manager

              Site Contributor
              1,000+ Posts
              • Nov 2008
              • 1732

              #7
              Re: Windows Server 2008 32bit, VPN slow printing

              Turn off the SNMP Status within the Standard TCP/IP port and this will stop Windows from checking the status of the machine.

              When Windows find that a cassette is out of paper, or toner is out on the machine, it will stop sending print jobs to the device. Windows doesn't understand that there are other paper trays or that the machine can manage it's own print queue.

              Restarting the Print Spooler forces a re-check via SNMP and even if there is still an issue, you get an amount of time whereby Windows thinks everthing is all good and releases the print jobs.
              Please don't ask me for firmware or service manuals as refusal often offends.

              Comment

              Working...