2 Replies Latest reply on Jun 19, 2012 4:15 PM by lylacinc

    Printing Very Slow

    lylacinc

      I have a client on FileMaker Pro Server 11 Advanced, users are using FileMaker Pro 11, all windows machines. Everything was running fine for about a year. A few days ago the users reported that printing had slowed tremendously. At about the same time, I lost access to FileMaker Server Admin Console getting a message stating "The admin server process may not be running, a required port may not be available, or your machine may be running slowly."

       

      I am working with the client's IS department to try and resolve this. I am low on their priorty list...

       

      This morning, someone in IS reported to me that "we do make network/port changes all the time". I assume that is why Admin Console is no longer working. However, I'm wondering if this is what is affecting the printing?

       

      Thanks for any insight.

       

      Lynda

        • 1. Re: Printing Very Slow
          Stephen Huston

          If the printers are also networked instead of wired into local clients, it is possible that network changes could be affecting print speed, but this is a really tough call to make without being inside the loop about what changes are actually being made to the network.

           

          That fact that multiple users are reporting the issue suggests that those users, if they are all  on a specifc part of the network, may have been affected by a  network change to that node/branch of the network.

           

          Have any network printers been added, removed, or relocated on the network?

          • 2. Re: Printing Very Slow
            lylacinc

            Hi Stephen:

             

            I just heard from another person in IS that they are in the process of changing the IP's of the printers, and I believe changing printer names also,    Because the users print to different printers based on the function they are peforming (might be creating a label, then printing a report), we hard coded the printer settings into our print scripts.

             

            I think we've found the problem...   

             

            Thank you for your help!

             

            Lynda