On Thu, 5 Feb 2004 [EMAIL PROTECTED] wrote:
> On Thu, 5 Feb 2004, Les Mikesell wrote:
>
> > On Thu, 2004-02-05 at 17:17, [EMAIL PROTECTED] wrote:
> >
> > > If he's doing printing to an LTSP workstation, it does the same thing as
> > > a jetdirect interface. it starts printing the data as soon as the
> > > connection is started.
> >
> > OK, next guess: does it do an IDENT query back to the source? Or
> > a reverse DNS lookup? 3 seconds seems too slow for a working DNS
> > and too fast for a DNS problem, but something must be happening.
>
>
> Nope. No ident. and I agree about the 3 seconds probably not being a
> dns lookup issue.
>
> I suggest running tcpdump, watching port 9100, to see what kind of
> traffic is flowing when he hits the PRINT key.
>
> something like this:
>
> tcpdump -i eth0 port 9100 or 53
>
>
> That should catch any print or dns packets. at least this will show at
> what point the first connection is made between the spooler running on
> the server, and the lp_server running on the workstation. If it spews
> out too much info, then you could run:
>
> tcpdump -i eth0 -s 1520 -w /tmp/tcpdump.out port 9100 or 53
>
> and that will capture the packet stream to a file. That file can then
> be viewed with ethereal using:
>
> ethereal -r /tmp/tcpdump.out
>
> Then, you can browse through the file looking at timestamps and packet
> types. It might show exactly what is happing (or trying to happen).
>
Jim,
sounds like plan. will do. julius
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
