<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 4, 2010, at 1:47 PM, Anurag Chourasia wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Mike,<div><br></div><div>Both the printer and the machines have the same subnet mask i.e. 255.255.255.0<br><br></div><div>Please note that both the working and non-working machine are on same network.</div><div><br></div>
<div>However, I have seen this problem with two physical printers now. Printer model is Zebra ZM400 and both are using D-Link Network Server.</div></blockquote><div><br></div>I don't have a whole lot of personal experience with D-Link servers, but since it works from one machine and not another I think we can rule out the printers and print servers. Look at the machines and how they connect to the network (cable, card, port on the switch, etc.)</div><div><br><blockquote type="cite"><div>Is there anything else I could try to get to the bottom of this issue?</div></blockquote><div><br></div>Network analyzers are your best bet; you can also look at port logs (if you have a "smart" switch that provides you with this information).</div><div><br></div><div>I'd also try swapping the working and non-working systems - move them as needed and connect the non-working machine to the working machine's cables and visa-versa.</div><div><br></div><div>Verify that both systems have the exact same software installed. If the machines are identical (same make/model/configuration of hardware) they should yield identical results over the same network cable and port on the switch you connect to. </div><div><br></div><div><blockquote type="cite"><div><br></div><div>Regards,</div><div>Anurag</div><div><br></div><div><br><div class="gmail_quote">On Fri, Nov 5, 2010 at 1:55 AM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com">msweet@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><div style="word-wrap:break-word"><div><div class="im"><div>On Nov 4, 2010, at 11:34 AM, Anurag Chourasia wrote:</div>
<blockquote type="cite"><font face="verdana, sans-serif">HI Mike,</font><div><font face="verdana, sans-serif"><br></font></div><div><font face="verdana, sans-serif">We have tried using Socket Protocol again for printing but the problem persists. Out of 100 Label print requests, only a few actually come out of the printer while the others are shown as completed successfully but nothing comes out of the printer.</font></div>
<div><span style="font-size:13px;color:rgb(51, 51, 51);line-height:18px"><font face="verdana, sans-serif"><br></font></span></div><div><span style="font-size:13px;color:rgb(51, 51, 51);line-height:18px"><font face="verdana, sans-serif">I have also captured the logs using tcpdump for this scenario.</font></span></div>
<div><span style="font-size:13px;color:rgb(51, 51, 51);line-height:18px"><font face="verdana, sans-serif"><br>The log in <a href="http://paste.org/pastebin/view/22779" target="_blank">http://paste.org/pastebin/view/22779</a> is when the print command was sent to the printer but nothing came out of the printer (Even though the JOB Was set to successful Status). <br>
<br>The log in <a href="http://paste.org/pastebin/view/22780" target="_blank">http://paste.org/pastebin/view/22780</a> is when the print command was sent to the printer and a label came out of the printer well printed. <br>
<br>The IP of the printer is 10.15.98.14 <br>
<br>The IP of the machine from where the command was sent is 10.0.157.86 <br></font></span></div></blockquote><div><br></div></div>Do the printer and machine have the same netmask defined?</div><div><br></div><div>How about the default router?</div>
<div><br><blockquote type="cite"><div><span style="font-size:13px;color:rgb(51, 51, 51);line-height:18px"><font face="verdana, sans-serif">...<div class="im"><br>I am not sure how to interpret this. From another Linux machine in the network, I am able to print successfully to this same physical printer using socket protocol.<br>
</div></font></span></div></blockquote><div><br></div><div>Is the other machine on the same network segment as the non-working one?</div><div><br></div><div>My suspicion is that you either have a configuration problem or have a bad network card, port, or cable causing the one machine not to work with this printer.</div>
</div><div class="im"><br><div>
<span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Monaco;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Monaco;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="word-wrap:break-word">
<div>________________________________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair</div><div><br></div></div></span><br></span><br>
</div>
<br></div></div><br>_______________________________________________<br>
cups mailing list<br>
<a href="mailto:cups@easysw.com">cups@easysw.com</a><br>
<a href="http://lists.easysw.com/mailman/listinfo/cups" target="_blank">http://lists.easysw.com/mailman/listinfo/cups</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>cups mailing list<br><a href="mailto:cups@easysw.com">cups@easysw.com</a><br>http://lists.easysw..com/mailman/listinfo/cups<br></blockquote><div><div><br></div></div></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>________________________________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair</div><div><br></div></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br></body></html>