can;t print large jobs to printer with ping -l 1500 failed from remote.

Unanswered Question
Aug 19th, 2007

Hi Experts,

Anyone face with this problem before? When printing to a printer with a large job,it is not able to reply back.

Eg: when ping to the printer using

-l 1452,it managed to get a reply.But when ping to -l 1500 , There is request timed out.

Not sure if the route hops is too long because when ping from locally,it can ping -l 1500. but from remote area, it can;t be ping using -l 1500.

thanks in advanced.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
cindylee27 Sun, 08/19/2007 - 23:52


Another thing is when ping from the Router locally to the printer, it able to get the ping -l 1500 connection successful as well.

I am lost on how to troubleshoot this problem.

Thanks in advanced.

ilya.varlashkin Mon, 08/20/2007 - 00:35

Make traceroute to see complete path. Then do hop-by-hop ping with size 1500 and DF bit set to find at which hop MTU is smaller than 1500. If fixing MTU at that hop isn't possible, you can try applying "ip tcp adjust-mss" on lan interface of end routers, though it won't have effect on UDP traffic.

cindylee27 Mon, 08/20/2007 - 00:59

Thanks ilya for your response.

This is what i got. By the way, how can i do hop-by-hop ping with size 1500? and how can DF bit set helps in this? Thanks again..:)

Tracing route to over a maximum of 30 hops

1 16 ms 6 ms 7 ms

2 <1 ms <1 ms <1 ms

3 2 ms 1 ms 1 ms

4 3 ms 3 ms 1 ms

5 5 ms 4 ms 1 ms

Trace complete.

royalblues Mon, 08/20/2007 - 01:22

You need to log on to the network device and do an extended ping


Protocol [ip]:

Target IP address: <>

Repeat count [5]: 20

Datagram size [100]: 1500

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface:

Type of service [0]:

Set DF bit in IP header? [no]: y >>>>> setting the DF bit

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 20, 100-byte ICMP Echos to, timeout is 2 seconds:

Packet sent with the DF bit set




cindylee27 Mon, 08/20/2007 - 01:31


Protocol [ip]:

Target IP address:

% Bad IP address



Protocol [ip]:

Target IP address:

Repeat count [5]:

Datagram size [100]: 1500

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface:

Type of service [0]:

Set DF bit in IP header? [no]: y

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 5, 1500-byte ICMP Echos to, timeout is 2 seconds:

Packet sent with the DF bit set


Success rate is 100 percent (5/5), round-trip min/avg/max = 4/7/8 ms


This is what i got from the Switch..Is pingable from the remote end and the local switch..but can't ping from the PC connected to the Remote Switch using -l 1500.

How can I troubleshoot from here?

Thanks again..

cindylee27 Mon, 08/20/2007 - 01:46

Hi Narayan,

Can give me some examples?

Meaning there is something to do with the devices that preventing the remote PC to not be able to ping with -l 1500 bytes???

I mean a switch can prevent the 1500 bytes to bypass the devices, n at the end it blocks the connectivity between the printer n remote pc?

Am i understand correctly this way?


b.petronio Mon, 08/20/2007 - 02:03

I there,

I believe, is the printer, and, is the Default Gateway of the PC where u are.

As i could read, u can do a 1500 size ping from that point ( to the printer, right ?

Could u check if u could ping (1500 size) the Deafult Gateway from ur PC ? or anything other address from ur PC ?

If not, u have a cabling/speed/duplex issue beetwen ur PC and the switch/router.

Try to set ur speed/duplex NIC config to 10/Half, and try again.

Hope that helps,

Best Regards,

Bruno Petr?nio

cindylee27 Mon, 08/20/2007 - 04:35

Hi Bruno,

Thanks for your reply..But we cant control the speed to 10/half as the pc must be connected to 100/full as part of the policy..

I can ping from the switch to the printer with -l 1500 but i can;t ping from the pc that connected to the switch, which will gve me timed out if ping with -l 1500. i can do it with only -l 1452.


b.petronio Mon, 08/20/2007 - 04:45


I'm not asking u to change it forever, but in order to troubleshoot.

Did u ping other machines from that PC, with the 1500 packet size?

If im right it wont work.

So i think, that u have a cable/nic/switch port issue.

Check the cables, and speed/duplex settings in both sides.. (PC <--> Switch).

Check the switch port, that connect's to the PC, issue a "show interface xEthernet x/x", and paste it for us.

Best Regards,


cindylee27 Mon, 08/20/2007 - 04:49


I am not in office currently..but can paste for u tomorrow.. but any other ways beside changing the ports??

cindylee27 Mon, 08/20/2007 - 21:04

Hi PEtro,

As below:

FastEthernet0/12 is up, line protocol is up (connected)

Hardware is Fast Ethernet, address is 000c.8551.e615 (bia 000c.8551.e615)

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, media type is 100BaseTX

input flow-control is unsupported output flow-control is unsupported

ARP type: ARPA, ARP Timeout 04:00:00

Last input never, output 00:00:01, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 2000 bits/sec, 3 packets/sec

5 minute output rate 5000 bits/sec, 6 packets/sec

30911733 packets input, 329155349 bytes, 0 no buffer

Received 197855 broadcasts (0 multicast)

0 runts, 0 giants, 0 throttles

4 input errors, 2 CRC, 2 frame, 0 overrun, 0 ignored

0 watchdog, 73532 multicast, 0 pause input

0 input packets with dribble condition detected

100003912 packets output, 2636780919 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 PAUSE output

0 output buffer failures, 0 output buffers swapped out

ilya.varlashkin Mon, 08/20/2007 - 05:45

from your Windows PC do 'ping -l 1500 -f '. Where IP of each hop is IP from the traceroute you just got. If at some hop you stop getting responses to above ping command, you've localised the problem.

cindylee27 Mon, 08/20/2007 - 06:54

Thanks Ilya,

You really give me a path on where to troubleshoot now..:) Now,i will try on what you asked me to do.. Lets say the hops go through devices IP A,B,C,D,E,F..

and it stops at C.. How should I troubleshoot further from there?

Thanks once again..:)

Danilo Dy Mon, 08/20/2007 - 07:36


Have you tried printing that large job by using a PC connected to the same switch where the printer is connected? Printers with low memory cannot print large jobs.

cindylee27 Mon, 08/20/2007 - 19:59

Hi Medan,

Yup,it can be printed if that is the case..

just tat can;t go through remotely ,so suspecting could be the MTU or buffer size of defragmentation or wat..


ilya.varlashkin Tue, 08/21/2007 - 10:59

Guided version: One little step in a time. Get that part sorted first, then will continue from there :-)

Unattended version: you go to that hop C and check it's links to B and to D trying to find out which part of the config results in reduced MTU :-)


This Discussion