RE: Wired vs wireless - comm trace needed

Hi Jeff

A couple things -

1. In the comm trace printout you might need to select ASCII instead of EBCDIC - if you see a bunch of '@' characters, especially, in the data part - I don't have knowledge of the Zebra encoding, but just maybe

2. There is always a job or jobs with the name of the writer - see what the job logs say, if you've not done already

3. A great packet sniffer used to be called Ethereal - www.ethereal.com will still get you to it, i think. Runs on a PC - like your laptop. It interprets packets really nicely - the i5 comm trace does some interpretation but can be puzzling at times. Ethereal CAN read packets that go to a different NIC but I've not got it to work with the iSeries - the NIC has to support it. Of course, I've not tried REALLY hard yet.

HTH
Vern

At 07:24 AM 6/12/2007, you wrote:

I've tried twice this morning and I just flat out don't see anything
resembling the data on my labels in my captures.

If I do a display filter on the IP address of my laptop, I see those records
in the capture file. If I do a display filter on the IP address of the
Zebra printer, I see nothing in the capture file. The online help wasn't.
I'll have to do more searching online for more help. I've never done this
before, but it doesn't seem THAT difficult.

A 47-label spool file took 467 seconds and 319 seconds, respectively, in 2
separate runs.

--
Jeff Crosby
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.


> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Krebs
> Sent: Monday, June 11, 2007 6:47 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Wired vs wireless - comm trace needed
>
> > It took 220 seconds for printing to complete...contains 182
> "records".
>
> Considering the number packets captured and the size of the
> file, 220 seconds is way too long. That is less than than 1
> packet every second.
>
> Ignore the ARP packets for now and look at the rest. Do you
> see the label data in some of the packets? Does it take the
> entire time to download the label data?
>
> Mike
>
> --
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list To post a message email:
> MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
> list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting,
> please take a moment to review the archives at
> http://archive.midrange.com/midrange-l.
>
>


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.