testing for network lag...

Collapse
X
Collapse
+ More Options
Posts
 
  • Time
  • Show
Clear All
new posts
  • n25an
    Service Manager

    Site Contributor
    1,000+ Posts
    • Jul 2008
    • 1030

    #1

    testing for network lag...

    Is there any software utility that I can throw on a thumb drive or a pc that will test for network lag... and can tell me if I will have issues printing files such as large tiffs and pdfs and the like...
    Sad To Say I Don't Have a Life
    I do this stuff on the weekends too
  • zed255
    How'd ya manage that?

    1,000+ Posts
    • Dec 2009
    • 1024

    #2
    A simple ping will tell you how quick you get a response from the network. Otherwise try Angry IP Scanner. Angry IP

    Comment

    • OMD-227

      #3
      One that I am familiar with and have used in the past to prove a point was Wireshark Wireshark
      It's free, used for network troubleshooting & packet analysis.

      From memory, it was very full-on! Lots to read about first as it is a very thorough program. Otherwise, I totally agree with Zed. A ping of the network with a '-t' after the IP address will give you a continuous ping test. You will see any network issues there.

      Printing speed for large files is primarily dependant on network speed, quality of cabling & network devices, processing speed of the printer and spooling speed of the computer printing the file. There are alot of items which could cause slower than normal printing. Always connect your laptop directly to the printer with x-over cable and print the clients 'problem' document from there to sort out if it is the file or the network or the printer causing it to be slow.

      Comment

      • unisys12
        Trusted Tech

        250+ Posts
        • Jul 2007
        • 490

        #4
        Originally posted by wazza
        Otherwise, I totally agree with Zed. A ping of the network with a '-t' after the IP address will give you a continuous ping test. You will see any network issues there.
        I agree totally. It is sometimes easier to show a IT person the results of a ping -T test and say that is the problem, rather than show them a Wireshark capture.

        Why?

        Because ping (IP Address of MFP) -t will show the time it takes for a response from the host (your PC where you perform PING) and the client (the MFP). My general rule of thumb - If I see less than a 3-5 millisecond responses, I will disregard. Over that though, I will point it out and it cannot be denied or brushed off as a MFP issue. It can only be a network issue.
        sigpic
        The first law states that energy is conserved: The change in the internal energy is equal to the amount added by heating minus the amount lost by doing work on the environment.

        Comment

        • RRodgers
          Service Manager

          1,000+ Posts
          • Jun 2009
          • 1947

          #5
          Yeah, as said above.... do a ping and use the -t watch it for a while. You "should" get a nice constant solid number. If not you have a problem. The problem I had was a Linksys router that was going out.
          HTH and GL!
          Color is not 4 times harder... it's 65,000 times harder. They call it "TECH MODE" for a reason. I have manual's and firmware for ya, course... you are going to have to earn it.

          Comment

          • D_L_P
            Self Employed

            1,000+ Posts
            • Oct 2009
            • 1196

            #6
            I agree, ping is very good for detecting lag. Use the -l switch to ping with bigger packets if you want to simulate bigger pdf's or tiff's, example: "ping -t -l 1400 102.168.xxx.xxx". 1400 will give you a bigger packet to test with (default is 32) but not so big it gets fragmented. Max mtu is 1500, technically 1492 due to header info but could be 1472 or lower depending on their network or routers.

            IMHO lag is usually on their end. LPR byte counting in port settings can slow it down, changing the print processor can speed it up, once though I turned off the spooler on the copier and it spped things up. In my experience setting up network printers "locally" has always been faster than a shared or "networked" printer, if the printer icon doesn't have that little bar under it that's good.

            Check out

            Comment

            Working...