1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Slow Printing across network on Windows 2K Machines

Discussion in 'Legacy Windows' started by LauraE, 2006/02/13.

  1. 2006/02/13
    LauraE

    LauraE Inactive Thread Starter

    Joined:
    2006/02/11
    Messages:
    2
    Likes Received:
    0
    I work in a small library with 6 computers that are networked to use a hp laserjet 1300 printer that is hooked to a DOT4_002 port on a Windows 2000 machine. 3 PCs run Windows 2000, 2 run Windows ME, 1 runs Windows 98. Until last week all PCs printed fine to the printer.

    For no known reason suddenly the 2 Windows 2000 PCs that are not directly connected to the printer have severly delayed printing (~2 minutes delay from last week).

    The only things that have been changed are:

    1) Ongoing upgrades to antivirus file definitions (through Authentium)
    2) Upgrades by an administrator to our firewall unit

    Could any of these changes caused delayed printing on the Windows 2000 machines and NOT on the other machines?

    Some attempts have been made to restore timely printing.

    1) Deleting and reinstalling the printer on the slow-printing Windows 2000 machines.
    2) Deleting and reinstalling the printer on the Windows 2000 machine that has a direct connection to the printer (parallel cable).

    Prior to Deleting and reinstalling the printer on the Windows 2000 machine that has the direct connection to the printer, the printer was configured to the LPT1 port. After reinstalling itself, it configured itself to use the DOT4_002 port. This required us to reinstall the printer on the Windows ME & 98 machines in order to find the printer. But still no problem with the Windows ME & 98 machines -- only with the 2 Windows 2000 machines that print through the network.

    I am a low end intermediate user, so please speak down and lead me by the hand if you have any suggestions for me. If you direct me to an article that will be over my head, please expect followup questions about it before I follow any suggestions it may offer.

    Thank you in advance for your help. LauraE
     
  2. 2006/02/16
    Dez Bradley

    Dez Bradley Inactive

    Joined:
    2004/10/11
    Messages:
    246
    Likes Received:
    0
    First thing i would try, is to disable your firewall and/or antivirus programs on all PCs, while not connected to the internet, and this is often done by right clicking on the program's icon on the system tray. Then try and print. Somewhere to start. At least may eliminate a few things and may give you something to look closer at if it works fine doing this.

    Wont be back on for 24 hours so cant follow this one up straight away if replied. Anyone?
     

  3. to hide this advert.

  4. 2006/02/17
    LauraE

    LauraE Inactive Thread Starter

    Joined:
    2006/02/11
    Messages:
    2
    Likes Received:
    0
    Slow printing, Windows 2000, across network

    Dez,

    Thank you for your reply. A "computer guy" stopped by our facility the other evening, said something about "stacks" and dynamic addressing, and suggested that we statically define our IP addresses on all 6 networked computers. This seemed to require the static designation of our DNS servers in order for us to still get to the Internet.

    It did greatly speed up our printing on the Windows 2000 machines.

    The main concern that I have now is that we will be down next time our administrators update our DNS servers on our firewall, until we redesignate the IP addresses of our DNS servers. I would rather remain dynamic, and let these things take care of themselves.

    BUT at least we are back to printing in a timely manner.

    Does anyone have other comments about why this static IP address specification would have sped up our printing?

    Thanks, LauraE
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.